What’s up with Monomodular?!
Hello to all of you out there in grid-land, and anyone who reads this blog. I wanted to make a quick post to let you know where things are with Live9 integration, and Monomodular as a whole.
First of all, I applaud the patience of those users who continue to use Monomodular in its current state in Live9….I can’t say that even I am among your ranks. Fact is, I haven’t used Live9 at all for creative purposes yet, and I sure as hell haven’t moved my Monomodular sessions over to it. Mostly, thus far, I’ve only had Live9 open to test Python scripts that are being ported over from Live8. Any testing of m4l has been very cursory, just to see if things “appear to work”. Furthermore, I’m afraid I’ve probably broken most of the links in SVN to Monomodular’s b994 content for Live8….sorry guys, but progress sometimes requires sacrifice, and I had to do some restructuring.
The good news: I’ve made a lot of progress. Most of the Python code is fairly stable now in Live9, but I know there are still plenty of bugs in there. It’s been my ambition to reduce the redundancy of the internal components and subclass everything following proper Pythonic conventions so that in the future it won’t be such a headache to change and maintain things.
The bad news: I have a lot less spare time than I used to, and Life has been kicking me in the ass for a little while…I’m still not sure when this will be done. But I work on it every day, so the prospects for completion sometime this month are good.
I just wanted to reiterate that I really appreciate all the help I get from you in the way of questions and bug reports. This has been a much bigger task than I anticipated (although, really, did I think it was going to be an easy thing to sift through and rewrite three years of work? Yes, apparently I did…silly boy).
For those of you who want to try things out while I’m still finishing b995, here’s what I can tell you:
Make sure to download the most current version of SVN repository, here:
http://code.google.com/p/monomodular/source/checkout
Make sure to only use b995 patches with the Live9 Python scripts.
Make sure to read the wiki, and put things where they go manually. Roughly the same rules apply for Live9/b995 as they did for Live8/b994….here’s some advice:
https://aumhaa.com/wiki/index.php?title=Manual_Installation
Make sure that when you download a new version of the repository that you replace ALL the relevant files, especially the Python files. The Live9 scripts heavily depend on one another, and upon the _Mono_Framework folder. These files change regularly, and it’s important (especially during the development process) that the most current versions be used so that they all get along with one another.
If you’re using OSX and want to try the installer, I’ve built one that works on my system, but you’ll have to drop me some email in order to get it: I really need get some feedback about it, and that’s the only sure way I can do it.
Make sure to send me bug reports….I am not currently using any of this stuff beyond programming it, so if I don’t hear about a problem from you it’s definitely not going to get fixed. That will hopefully change in the near future after I get the Python stuff finished (along with the Livid backlog I’m working on), but in the meantime it really helps when you can send me details and a log.txt file so I can track it down.
As always, thanks for the love….I don’t do this for the money, so its really great to hear from you and know that you’re using my work even when I don’t have the time to. It makes it much more satisfying, and gives me hope that I, too, will soon be blinking again!
a
P.S. I’ve made statements to several of you lately via comments about specific bugs/problems that I haven’t checked on yet….don’t despair, the fact that they are in comments here gives me a reference to them, and I’m going to start working on that tonight.
Uncategorized
Awesome post, thanks for the update!
James
somehow for me it still crashes after i ad the second script.
(monomodular + launchmod)
35577 ms. RemoteScriptError: Traceback (most recent call last):
35578 ms. RemoteScriptError: File “”, line 1, in
35578 ms. RemoteScriptError: File ”
35578 ms. RemoteScriptError: C:\ProgramData\Ableton\Live 9.2 Suite\Resources\MIDI Remote Scripts\Monomodular_b995_9\__init__.py
35578 ms. RemoteScriptError: “, line
35578 ms. RemoteScriptError: 5
35579 ms. RemoteScriptError:
35579 ms. RemoteScriptError:
35579 ms. RemoteScriptError:
35579 ms. RemoteScriptError:
35579 ms. RemoteScriptError: ^
35579 ms. RemoteScriptError: SyntaxError
35580 ms. RemoteScriptError: :
35580 ms. RemoteScriptError: invalid syntax
35580 ms. RemoteScriptError:
35580 ms. Exception: Traceback (most recent call last): File “”, line 1, in File “C:\ProgramData\Ableton\Live 9.2 Suite\Resources\MIDI Remote Scripts\Monomodular_b995_9\__init__.py”, line 5 ^ SyntaxError: invalid syntax
this is what the logfile says
hmmm… somehow this was a mess from my side, i went to the SVN repository and there i couldnt figure out how to download the scripts other then click on each and download them, but somehow they got modified doing this, i went now to the read only link, did the same there and voila… it works, sorry for the hussle
robert
And me again…
I found a program to download the whole SVN rep.
I tested some of the m4l patches and they seemed to work.
But modlink crashed live.
There is an unfrozen file in the Folder but this is b994, anything I am
Doing wrong? Windows 7 here btw.
Thank you!
Robert
hey robert,
I was having the crashing problem also. I had to load modlink in live 8, hit the edit button, unfreeze the device, and resave it. Then i could use it in live 9. I’m on win 7 also, if we keep giving amounra as much info as we can find about problems we’re having, maybe we can get this puppy running as smooth as it was in live 8.
What’s up What’s up !What’s up !What’s up !!! thanxs for your work !! mostly the mods, run fine, how can i see the error reports for send to you???
i have a petiton for port in monomodular is this:
http://monome.org/docs/app:raptor
but the 1.02 version, the raptorX don´t have quantization… 🙁
i know u are very busy but only is a suggestion/petition..
thnxsss!!!!
Hey javier,
Thanks for the love!
I’ve got a bunch of stuff I want to port over to mod-land when I get all this Live9 stuff finished. I’ll definitely take a look at that, most of the newer patches are pretty easy for me to port. That one looks pretty interesting. Does it work with modlink?
Re: error reports. There’s two places you can look. For Python errors, you want to send me your log.txt file (https://aumhaa.com/wiki/index.php?title=Log.txt ). For Max errors, you can look in the Max window (ctrl-click or right-click on the mod patch’s window and select the bottom option, “Open Max Window”).
I had a little breakthrough today. I haven’t really been able to use modlink with external apps since i started using live 9, some apps would kinda work, but most wouldn’t work at all. The fix for polygome, and plinko you recently put up, work perfectly.
So I decided to open up the new polygome, and the old polygome, and put them side by side, and see what was different. In the p gome subpatch, I noticed there were 3 boxes added after an r–in, and before a zl rot-1. So i copied those 3 boxes, opened up modlink, and looked for an r–in, and a zl rot-1. When I found them I pasted the boxes, hooked them up the same way, and saved the patch. Now every monome app I throw at modlink works perfectly!
I’m not going to pretend I have any idea why it works, but it does, thanks to your work!
I think you’re talking about the addition I made that filters out velocities other than 0 or 1. I did this for Push (because it can send a grid press at any value between 0 and 127, but the patches only respond to 0 or 1).
It’s weird that this would have any effect on a system not using Push, but I’m glad you told me about this. I spent some time messing with modlink last week (around the same time that I posted updates to Polygome and Plinko) and was having my own problems. For one thing, the serialosc standard appears to have changed yet AGAIN, which means I need to figure out what’s changed and then implement it. Anyway, I’ll need to add that bit you’re referring to in most of the current patches before they can be used with AumPush.
Hello,
I have been trying to get Monomodular to work and finally got the installer to work (b993). Problem is, when I select LaunchMod as the Control Surface script, nothing happens…all the lights go off on the launchpad and if I press any buttons on it, Automap tells me that there is no software to connects to and “please run Software Setup”
I would try this with b994 but the installer will not work for me (it does not recognize the Installation Package when I drag/drop it in the appropriate place).
I am using OSX.7.5, Live Suite 9 (not yet authorized), and Max 6.1. I am sure youre busy. Thank you for any and all help.
You’ll have to use the b995 versions to work with Live9. I’ve added the OSX installer for b995 at the root of the GitHub distribution, I’d download the most current version of the repository and give it a try. If it doesn’t work for on your system for whatever reason, you’ll probably have to put things where they go manually. There’s info about where each file goes here:
https://aumhaa.com/wiki/index.php?title=Manual_Installation
And you can download the current version here:
https://github.com/aumhaa/monomodular/archive/master.zip
If that doesn’t get you up and going, hit me again and we’ll figure out the details together.