Page 5 of 6

Re: Monomod Thread (b932, Monotes)

Posted: Wed Jun 22, 2011 9:40 pm
by hgt
amounra93 wrote:Ohm64 Support is complete. I've been testing the current build for the last week or two, and everything seems to be working except some of the pattr stuff in a few client patches. Hopefully I'll be able to get this cleared up pretty quickly.

I'm currently reintegrating the TouchOSC template into the new depends on how long it takes me to do this, but its been pretty straightforward so far. It is completely different than the old version of the TouchOSC template. I think it would break things if you delete any of the stock pages in the TouchOSC arrangement, as the script will send controls data back to TouchOSC and it won't know what to do with them. BUT, I hadn't thought of that eventuality, and I haven't gotten that far on the script, so I'll try to add some kind of customization features in the MAP file so that you can turn pages off if you don't need them.

When the TouchOSC stuff is done, I'll release that portion of the suite.

Block support is planned, but I haven't decided exactly how to do it yet: I don't have a Block, so that makes it difficult to come up with a control script for the surface when its not in Monomod mode. I will probably just use Livid's stock script and add the Monomod stuff (with the mode toggle assigned to the Livid button). There will be the addition of flashing states to the stock script, at the very least.

I'm waiting on some things to pan out before I can release all of the current version...its out of my hands. I apologize for the delay, but it shouldn't be too much longer, and you can look forward to a much faster, easier, more complete monomodular when I publish the new stuff (along with some new original clients, and greatly improved documentation for those of you wanting to create your own clients) :)

I plan to support the new following controllers with the new version:

iPad w/TouchOSC

Keep an eye on the blog...I've been putting off making any announcements until I decide exactly what I want to release and when. Although I know it may look like I haven't been doing anything for a while, in fact the opposite is true....I've completely rewritten everything from the bottom up.

Send (or resend, if you already have sent me in the past) your system specs, email, etc if you would like to test this stuff before release.

thanx a lot for your fast answer.
its nice to hear that there is block support planned and using the livid stock script + monomod sounds like a perfect solution. would the monomod host work with the livid monome bridge?
i think keeping it simple suits most people best.
i don't like to switch between modes on a controller a lot. thats why i got rid of the launchpad and why i don't use touchable on the ipad anymore. its to many controls squeezed into a single surface. that will allways result in an unsatisfying compromise. i rather use a dedicated controller on one function only. e.g. , real(not simulated) faders for mixing, griid for cliplaunch, pads/keys (and some ipad sequencer apps) on note input, konkreet performer and some (real)knobs for device control, plus a gridcontroller for monome emulation(your host+8 clients concept is really how i allways wanted the monome to work!)...
maybe a very personal approach but i get distracted very easy if there is too many modes, menues, shift fuctions and stuff on a controller.
thank you very much for the great device! is there a donation button :wink:,

Re: Monomod Thread (b99)

Posted: Thu Jul 21, 2011 1:13 am
by amounra93
Just got back from vacation, and trying to get things together to publish this weekend. Here's the details: ... lence.html



p.s. in response to question about the Livid monome bridge: Monomodular replaces the need for it. Sorry for the late response, I didn't see that post until just now ;)

Re: Monomod Thread (b99)

Posted: Mon Aug 08, 2011 9:51 am
by amounra93
b99 release....follow the bread crumbs.

Public release currently supports iPad (TouchOSC), Livid Ohm64 RGB and Monochrome, and Launchpad.
OSX only for now, but there's only a few missing files to make it work (zeroconf for Windows...).

Read the docs suck, I know, but if I spent the time necessary to document everything I wouldn't be able to release it for another 30 days or so. Cart, then horse ;)

I know some of you want a Block script...its in the works. Block is in the mail...should have it next week sometime.

Livid's Code, APC40, and iPod will be out shortly after I've gotten some feedback about the current scripts.

I'll be doing some video tutorials throughout the week as I have time, check back.

Those of you with Launchpads, I'd love some feedback...I haven't used the new script much. It allows you to use Monomodular in "User3" (by pressing User1+User2), so you can still use it with whatever else you had going on. By popular demand ;) However, I did change the button lighting calls from m4l and I just realized I didn't document it in the script, so contact me if that fubars you somehow, and I'll add the docs to the next release.

SVN hasn't been updated yet, I'll get to that tomorrow (which makes me wonder why I'm even using SVN...).

Happy blinking.


Re: Monomodular Thread (b99: Ohm64, Block, iPad, Launchpad)

Posted: Fri Aug 12, 2011 8:37 am
by amounra93
I've released a preliminary script for the Block that emulates the Launchpad, provides flashing LED feedback, two user modes, and a Monomodular layer. The only documentation currently available is an entry on my blog, but the Launchpad emulation is pretty simple. I don't have much time to spend testing it right now, so I'd love some feedback. Cheers :)


Re: Monomodular Thread (b99: Ohm64, Block, iPad, Launchpad)

Posted: Sat Sep 10, 2011 10:45 pm
by hgt
hi there amounra93,

real great work! would your monomod suite work on a kaosspad3(kaonome: as well?
keep it up,

Re: Monomodular Thread (b99: Ohm64, Block, iPad, Launchpad)

Posted: Mon Sep 12, 2011 9:26 am
by amounra93
Sorry, that might not be so easy to do....while Monomodular offers a m4l plugin to connect directly to native monome plugins, you'd need the opposite. The kind of integration you'd need to do what your talking about would require a control script that communicates directly with a monome (since the kaoss pad, in this instance, is emulating one)....that would mean kaosspad -> kaonome -> m4l/Monomodbridge(doesn't exist) -> Monomodular....not necessarily cpu efficient or desirable, but possible.

The only efficient way to do this would be to build a python script for the Kaoss Pad. You could, of course, build your own bridge to Monomodular...the framework is already fairly robust (I've universalized the Monomodular Python client framework...each compatible controller currently uses a nearly identical script in the unreleased versions). It would require some m4l and python programming skills on your part. Its not something I have any intention to do, sorry. I've gotten very little feedback for much of the stuff I've already built, so I've kind of shied away from implementing support for further control surfaces that I don't use myself (but I do appreciate the support I get ;) ).

I DO plan on direct monome and arc integration at some point, but I don't have any hardware to test on...if and when someone donates a monome for the project, I'll spend some time writing the scripts (it won't actually take that long....the last time I did a raw port, it was for the Launchpad, and it took me about 4 hours to finish with the old framework....and things have improved since then). Anyway, thanks for the interest and encouragement.

I'm currently spending time on finishing versions of native Block and Code scripts (new one for the Block, not the previous quickly released Launchpad emulation), and then I plan to revisit the APC40 before the next release cycle.


Re: Monomodular Thread (b992)

Posted: Sat Oct 29, 2011 1:55 am
by amounra93
Hey guys....Monomodular is up to b992.

Added support for APC20 and 40, Livid Code, there's a new native Livid Block script, and lots of changes and improvements. 2 new Mods that didn't exist before, and new routing possibilities on OSX. Also made an osa installer to simplify things a little (only works on OSX though).

No documentation as of yet....I'm putting it out there for those who are already using it to test out for me, and meanwhile I'm finishing up odds and ends and getting docs and videos ready. If you try it and something isn't working, please let me know so I can fix it. There's so much content now its really hard for me to keep up with everything and make unified releases, so every little bit helps.


Re: Monomodular Thread (b992 release...lots of new stuff)

Posted: Wed Nov 02, 2011 5:08 pm
by douglasciences
i cant seem to find the monomod b992 patch in live, i see all the other b992 items, is it a part of the help file?

Re: Monomodular Thread (b992 release...lots of new stuff)

Posted: Wed Nov 02, 2011 8:23 pm
by amounra93
Most commonly asked question about Monomodular these days. Monomodular now exists solely in in Python. Go to Live's MIDI Preferences, and you can select it as a control surface (with 'None' assigned to inputs and outputs). You'll also want to install whatever version of control surface you're using (LaunchMod, AumPad, etc.) with the appropriate inputs/outputs. The old way of doing things (a m4l plug for the host) is no longer necessary.

I'm working on getting documentation for this stuff built into all the components so that this sort of confusion can be minimised, but that will probably be a b993 addition.


Re: Monomodular Thread (b992: New m4l based installers)

Posted: Tue Jan 03, 2012 7:05 pm
by amounra93
Hey guys, just a short note to let anyone looking here know that there's a new blogsite:

and a new Wiki:

And Monomodular is now distributed through a new m4l patch I built that does all the downloading and installation directly from within Live.

There's quite a bit of new content included as well.

Cheers :)


Re: Monomodular Thread (New m4l based Installers)

Posted: Sat Jan 07, 2012 11:44 pm
by amounra93
Installers updated to add version tagging, and fixed a few bugs on both platforms. I really need some Win7 feedback on these, as I don't have a dev machine with win7 installed....


Re: Monomodular Thread (New m4l based Installers)

Posted: Wed Jan 18, 2012 8:11 pm
by mduncs
hey, i'm on Win7. I installed Subversion and i've restarted live but the monomod installer still sends me to the subversion site to download it every time i click the button. how do i install this?

Re: Monomodular Thread (New m4l based Installers)

Posted: Thu Jan 19, 2012 7:11 pm
by amounra93
Hmmm...that's a new one. I did update the installer for Windows yesterday without saying anything .... I haven't observed that issue yet though (and I've spent a bit of time adjusting the installer lately on a copy of Win7 to get the bugs worked out of it on that platform).

If you still haven't gotten it working, you can always download the SVN files directly to you computer using MSDOS commands now that you have the subversion tool installed. I'll be releasing a new version (b993) very shortly with many changes, and I'll post a link to those file individually on my Website....but I don't have the current versions of b992 available anywhere except SVN at the moment.

Email me directly if your still having problems and I can get you sorted. I'd also like to get to the source of the trouble since things aren't working for you.

BTW I'm guessing that a computer restart probably cured this?


Re: Monomodular Thread (New m4l based Installers)

Posted: Thu Jan 19, 2012 10:13 pm
by mduncs
installing the 32bit version of sliksvn fixed the problem with downloading, i now have a monomodular_svn folder with all the goodies inside, but the installer isn't able to find the three file paths on its own and doesn't seem to respond to the ones i am selecting:

C:\Program Files (x86)\Ableton\Live 8.2.7
C:\Program Files (x86)\Cycling '74\Max 5.0
also tried
for the last one

Re: Monomodular Thread (New m4l based Installers)

Posted: Fri Jan 20, 2012 9:25 pm
by amounra93
You might try downloading the installer again....I updated it yesterday after testing more extensively on win7. It autodetects the paths half the time, but usually if its the first m4l device I drop in a new project, it doesn't find the paths automatically. I think this is because Live is accessing the log.txt file (which is how the installer detects the correct paths) at the same time the installer is trying to access it. There may have been a few bugs in the last one that prevented correct path detection.

If you drop the installer onto a new track and it doesn't automatigically find the right paths, delete it and try it again a couple of times. I'm working on a new routine for the b993 installer that will fix this behaviour (which only happens on windows7, to my knowledge).

The correct paths are detailed on the wiki, and it appears that you've selected the right paths...I'm not sure why it won't install for you. You can, of course, place the files manually where they are supposed to go, the installer is just (usually) a short-cut for this process. I have a debug version of the installer I can send you, I'd be pleased to find out what's going on here (win7 has been a drag so far to get working for this). And thanks again for the feedback.

Just drop me some mail:

Here's the wiki page for manual installation: ... stallation