Archive for April, 2013

h1

What’s up with Monomodular?!

April 22, 2013

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:

http://www.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.

 

 

 

h1

Old News

April 9, 2013

The AumPC40 script has been giving me grief for a week now, but I’m happy to report I’ve finally got it licked.  There’s a new script in Monomodular SVN for the APC40….I’ve also updated all of the _Mono_Framework files.   I can’t guarantee that changes to the Framework haven’t broken earlier scripts I’ve ported, so you may want to hold off updating if you already had Monomodular working in Live9 and don’t need the APC40 script.

AumPC20 script will follow shortly….I have to catch up with a few other things first, though.

I’ve already done most of the work for the AumPad script, so it looks like Code is the last thing to update.   Base will get some Monomodular love pretty soon, I think, now that I have a beta version finished for Live9.   Also, it sounds like I should be getting a Push sometime this week, so I can finally get on with tearing that apart and maybe doing some cool things with its codebase (which I’ve largely been unwilling to even look at until I got the hardware in front of me…sorry, but free time is at a deficit these days).

Lemme know what you find….I’m certain there’s still some broken stuff in there.

 

h1

If you can’t say anything nice, then add some stuff to svn.

April 3, 2013

I’ve been hard at work since my last blog post trying to get Monomodular working in Live 9.

The good news:  some stuff is working.  I was able to get AumTroll and MonOhm working together in my own setup, although I haven’t done extensive testing.  I’ve also gotten the LaunchMod script working (and boy, was that a pain in the arse!).

The bad news:  Live 9 sucks.  Well, not necessarily from the end-user’s view, but from the viewpoint of a programmer who was already having to hack into the backend of Ableton’s code, things have become considerably more difficult for those of us who are not working with the official Cucumber debugger.  New methods in the _Framework have essentially broken any error reporting that doesn’t happen in the very top level of code, which means now things just break and there’s no way to find out what the cause was other than adding explicit lines of debug code myself, and even that is only moderately effective.  In addition, Live no longer recompiles and reloads the scripts each time you add or remove  them from preferences, so its now necessary to restart Live every single time I change a line of code in one of my scripts.  Bottom line:  the whole process is much more tedious and takes a good deal longer.

Oh, and the current decompiles of the included Live 9 scripts available are fairly unusable for more than just educational purposes.  Just saying, that’s all.  Presumably the method being used is decompyle2, and although it does a really good job, assertions are not being rendered properly and will fail to compile correctly in Live 9’s Python interpreter.  I wish I could say I’ve done better myself, but I am using the same methods and the only solution is to go through and carefully hand marshall all the incompatible lines with correspond valid syntax.  It’s painful.

I’ve added the currently working scripts to the SVN repository for those of you that want to try things out.  Let me know what you discover, there are sure to be lots of bugs with all this stuff.  I’m slowly but surely getting through most of the old scripts.

It is now necessary to have the “_Mono_Framework” folder installed for the scripts to work.  This is a generalization of the most useful and prevalent scripts I’ve written, and will be the model going forward for all the stuff I’m working on.  When updating to new versions, it is extremely important to make sure that you’re using the most recent version of these scripts, and I haven’t come to any conclusions about how I’m going to marshall that process, so for the time being just replace the “_Mono_Framework” folder with the current version every time you download a new revision and you should be fine.

I’m currently trying to get the AumPC scripts done, but I’ve run into a very frustrating problem I haven’t been able to solve yet so I’m not sure when it will be finished.

It seems I might have gotten left out of the loop in regards of getting an Ableton Push in a timely manner.  Oh well, their loss I guess.  I’m not going to be bothered to write cool stuff for it if they can’t send me the hardware….hell, I’m even paying for the damned thing!  Anyway, some of you had been asking, so there’s your answer:  it’s still “Vaporware” as far as I’m concerned 😉

Oh, and for those of you concerned about my health (mostly just me, but still…), I apparently might be getting better.  But quite honestly, all these meds are making me sleepy and cranky….I’ll sure be glad when things are back to normal!