Since I don't have a working Ohm, all I could do was trace the obvious problems and fix them. Here is a link to the MonOhmPad script that should work with Live 8.22. It will load, but I can't test it further for a while. Please provide me with feedback and copies of your log. Good Luck!
http://dl.dropbox.com/u/6044993/MonOhmPad_b972.zip
31.3.11
New Toys! ....er, nevermind.
New versions of Live and MaxMSP have arrived, and I'm happy to say that it looks very promising. I see some easy solutions to some problems I've been having for a while (especially initialization ordering). You can look forward to some updates when I have time to sit down and have a look-see. I've been trying to bend my time towards making some music lately, which means that I'm discovering bugs, flaws, and ergonomics issues with all of my patches. Bad in the short term, but good in the long term as I have a chance to fix things. Cheers :)
edit:: so much for that. Ableton has changed the remote scripts. Everything appears to be broken (Hanz's scripts as well, as far as I can tell). I would fix my Livid scripts, but....
My Ohm64 has picked today, of all days, to completely take a dump.
Heavy sigh.....
I can't even switch back to the APC, because my scripts are broken for it, as well. In any case, it looks like I'll be fixing the APC scripts first, since I actually have one that works....
Sometimes progress is painful :(
edit:: so much for that. Ableton has changed the remote scripts. Everything appears to be broken (Hanz's scripts as well, as far as I can tell). I would fix my Livid scripts, but....
My Ohm64 has picked today, of all days, to completely take a dump.
Heavy sigh.....
I can't even switch back to the APC, because my scripts are broken for it, as well. In any case, it looks like I'll be fixing the APC scripts first, since I actually have one that works....
Sometimes progress is painful :(
15.3.11
Quiet....I'm thinking.
I've done very little programming for a while. My head has departed from the: "what can I do with the controllers that exist," to the : "how can I make the control surface that I really want". I'm very happy with the software tools I've created, but I don't wish to write anything further until I've decided exactly what I need to incorporate into a final version of Monomodular to support what I have in mind for a "all-inclusive" grid controller.
What does that mean, exactly? Well, let's just say this: it hasn't been done yet. When I've got a working prototype, I'll post more details.
In the meantime, I'll be trying to navigate back to older versions of Monomodular to add some stability to them , as well as adding a few new features and fixes to the Ohm64 scripts.
Coincidentally, as I'm writing this I've just received a box in the mail from Mouser...now the fun begins :)
What does that mean, exactly? Well, let's just say this: it hasn't been done yet. When I've got a working prototype, I'll post more details.
In the meantime, I'll be trying to navigate back to older versions of Monomodular to add some stability to them , as well as adding a few new features and fixes to the Ohm64 scripts.
Coincidentally, as I'm writing this I've just received a box in the mail from Mouser...now the fun begins :)
8.2.11
Construction Time Again
Just a quick note....
I've mostly been dealing with 'Life' lately (no...I mean 'REAL Life', not the generative Monomodular patch I've been promising to release for over a year and haven't gotten around to....ironic)....mostly running live sound a lot. Last week I experienced the ultimate in dichotomy: first, I ran sound for Bassnectar (probably the loudest show I've ever done), and the following day I ran sound for the Bee Eaters: four large diaphragm condenser mics, all several feet from the performers, mixed so that its only loud enough to sound like you are standing right next to the musicians anywhere in the room. It might have been nicer if the Bee Eaters show had been BEFORE Bassnectar. And of course, I've been reassembling a 78 VW Bus after catching it on fire two months ago (it will be nice when I'm "mobile" again).
Monomodular has taken a back seat lately, but I'm still working. Debugging is much more difficult now that I'm compartmentalizing things....I hit a snag last week and just finally figured it out. I got the current version up and running last night, though, so progress is being made. I have no idea how long the rest will take, as this is a very major rebuild of the whole framework.
In the meantime, if you want to try out the current beta version of the material, there's a link at the bottom of this post. I had held off making this public as long as possible with the hopes of releasing a full package for all the supported controllers, but I simply haven't been able to finish everything as soon as I'd hoped. I got a little too ambitious with this new version, but all in all, it will allow me to integrate more types of hardware controllers much more easily into version 1.0, as well as allowing expansion of the feature set of Monomodular considerably in the future.
If you have any issues/questions about the current beta package, please drop a comment here, or feel free to contact me directly.
Cheers :)
http://dl.dropbox.com/u/6044993/Monomod%20b96b_release.zip
Please note that this beta version is only compatible with the Livid Ohm64....the other controllers haven't been reintegrated yet.
I've mostly been dealing with 'Life' lately (no...I mean 'REAL Life', not the generative Monomodular patch I've been promising to release for over a year and haven't gotten around to....ironic)....mostly running live sound a lot. Last week I experienced the ultimate in dichotomy: first, I ran sound for Bassnectar (probably the loudest show I've ever done), and the following day I ran sound for the Bee Eaters: four large diaphragm condenser mics, all several feet from the performers, mixed so that its only loud enough to sound like you are standing right next to the musicians anywhere in the room. It might have been nicer if the Bee Eaters show had been BEFORE Bassnectar. And of course, I've been reassembling a 78 VW Bus after catching it on fire two months ago (it will be nice when I'm "mobile" again).
Monomodular has taken a back seat lately, but I'm still working. Debugging is much more difficult now that I'm compartmentalizing things....I hit a snag last week and just finally figured it out. I got the current version up and running last night, though, so progress is being made. I have no idea how long the rest will take, as this is a very major rebuild of the whole framework.
In the meantime, if you want to try out the current beta version of the material, there's a link at the bottom of this post. I had held off making this public as long as possible with the hopes of releasing a full package for all the supported controllers, but I simply haven't been able to finish everything as soon as I'd hoped. I got a little too ambitious with this new version, but all in all, it will allow me to integrate more types of hardware controllers much more easily into version 1.0, as well as allowing expansion of the feature set of Monomodular considerably in the future.
If you have any issues/questions about the current beta package, please drop a comment here, or feel free to contact me directly.
Cheers :)
http://dl.dropbox.com/u/6044993/Monomod%20b96b_release.zip
Please note that this beta version is only compatible with the Livid Ohm64....the other controllers haven't been reintegrated yet.
19.1.11
A little stumped....
Its funny that I've been able to do all this hacking to other peoples code, and now that I'm working with code that I wrote my self, I'm having difficulties.
The integration for the iPad version of the MonOhmPad script is nearly done....I have some details to work out (mostly displaying correct parameter names/values when they change assignments), but its working swimmingly. That means I'm using an iPad as a control surface to communicate directly with Live's Python scripts just as though it were an actual Ohm64. (I needed to write that, it kinda felt good ;) ).
So, now I'm working on completely rebuilding the Monomod framework so that it is configurable in a more general manner. I've used the _Framework as a guide, and I guess I'm finally getting the idea of what object oriented programming really is. But I've hit a bit of a snag....there's so many different ways to go !
I hope to present a completed version by the end of the weekend (simply because I have other things I'd rather be doing than staring at a computer screen for hours on end). I'm taking my time with it: the idea is to create the framework I'd originally intended on, which will make it a great deal easier to add new control surface support as I/others have time. I had hoped to make it understandable to the general user, but I guess I kind of missed that boat when I used the _Framework scripts as a model. Anyway, the final version of Monomod will contain a single js contained in a very barebones Max patch. Eventually, I plan to code a pure Python version of Monomoduar....wouldn't that be nice :)
The integration for the iPad version of the MonOhmPad script is nearly done....I have some details to work out (mostly displaying correct parameter names/values when they change assignments), but its working swimmingly. That means I'm using an iPad as a control surface to communicate directly with Live's Python scripts just as though it were an actual Ohm64. (I needed to write that, it kinda felt good ;) ).
So, now I'm working on completely rebuilding the Monomod framework so that it is configurable in a more general manner. I've used the _Framework as a guide, and I guess I'm finally getting the idea of what object oriented programming really is. But I've hit a bit of a snag....there's so many different ways to go !
I hope to present a completed version by the end of the weekend (simply because I have other things I'd rather be doing than staring at a computer screen for hours on end). I'm taking my time with it: the idea is to create the framework I'd originally intended on, which will make it a great deal easier to add new control surface support as I/others have time. I had hoped to make it understandable to the general user, but I guess I kind of missed that boat when I used the _Framework scripts as a model. Anyway, the final version of Monomod will contain a single js contained in a very barebones Max patch. Eventually, I plan to code a pure Python version of Monomoduar....wouldn't that be nice :)
17.1.11
Nitty Gritty
I've been plugging along all weekend (pun-intentional), splitting time between fixing the VW (what a mess! I wish I could script its problems away....) and writing code to integrate the m4l stuff with the new version of the Ohm64 script. I've made good progress.
The final release will probably take a little longer than I originally planned (imagine that? hehe). I've rewritten the entire framework of the m4l stuff based on what I've learned from the _Framework scripts in Python. Its very satisfying to be able to port entire sections of my older scripts in a very quick, easy manner and have things just work. On the other hand, I've been taking my time so that the new javascript framework/objects are as reusable and programmable as possible. I have it in mind to make some new layouts for the iPad in the future, and I'd also like the framework to be accessible to others that may want to use it.
I haven't been able to achieve everything I'd hoped with the direct use of the Python scripts and m4l. I (grudgingly) was forced to create a nameserver in javascript, instead of doing it in Python. The reasons for this are various, but mainly I do not want to replace framework elements wholesale....if I cannot provide an override for a Class, or come up with a workaround in the main Module, I'll do it in m4l. It seems like this is the best option for compatibility. I will be investigating the Serato scripts to see if I can find better solutions than what I've currently worked out.
Finally, I plan on making a few key changes to the Ohm64 base script before release. It's come to my attention that grid navigation is less than desirable with the script. I have to agree, and its been bugging me for a while. I'm going to add an extra shift mode that utilizes one of the top left keys to make the bottom left buttons become navigation keys WITHOUT zooming the grid out. This way you will be able to move track/scene at a time while still looking at the grid (Launchpad style) as well as have a visual indication (via button lighting on the bottom) of which directions are available to navigate. Hopefully this extra mode doesn't make things too confusing for those of you that might already be a little fuzzy.
The Monomod script is currently working in its new incarnation, but it might be this weekend before I get it into everyone's hands (or longer, I guess, but I'm being optimistic). I've stopped playing with the Ohm64, and am now working solely on integrating TouchOSC with the Python scripting so that you can either use the iPad as a replacement for the Ohm64, or use it for additional input/controls via the same script (the first release will probably not include many extras, but you will be able to use the 256 Monome multicolor grid at the same time as the Ohm64, and hopefully I'll have time to port some simple LCD feedback to the same patch so that the iPad displays the same sort of thing that the LCD patch in m4l does).
Just wanted to post a short update, I'll be in touch. Cheers.
a
The final release will probably take a little longer than I originally planned (imagine that? hehe). I've rewritten the entire framework of the m4l stuff based on what I've learned from the _Framework scripts in Python. Its very satisfying to be able to port entire sections of my older scripts in a very quick, easy manner and have things just work. On the other hand, I've been taking my time so that the new javascript framework/objects are as reusable and programmable as possible. I have it in mind to make some new layouts for the iPad in the future, and I'd also like the framework to be accessible to others that may want to use it.
I haven't been able to achieve everything I'd hoped with the direct use of the Python scripts and m4l. I (grudgingly) was forced to create a nameserver in javascript, instead of doing it in Python. The reasons for this are various, but mainly I do not want to replace framework elements wholesale....if I cannot provide an override for a Class, or come up with a workaround in the main Module, I'll do it in m4l. It seems like this is the best option for compatibility. I will be investigating the Serato scripts to see if I can find better solutions than what I've currently worked out.
Finally, I plan on making a few key changes to the Ohm64 base script before release. It's come to my attention that grid navigation is less than desirable with the script. I have to agree, and its been bugging me for a while. I'm going to add an extra shift mode that utilizes one of the top left keys to make the bottom left buttons become navigation keys WITHOUT zooming the grid out. This way you will be able to move track/scene at a time while still looking at the grid (Launchpad style) as well as have a visual indication (via button lighting on the bottom) of which directions are available to navigate. Hopefully this extra mode doesn't make things too confusing for those of you that might already be a little fuzzy.
The Monomod script is currently working in its new incarnation, but it might be this weekend before I get it into everyone's hands (or longer, I guess, but I'm being optimistic). I've stopped playing with the Ohm64, and am now working solely on integrating TouchOSC with the Python scripting so that you can either use the iPad as a replacement for the Ohm64, or use it for additional input/controls via the same script (the first release will probably not include many extras, but you will be able to use the 256 Monome multicolor grid at the same time as the Ohm64, and hopefully I'll have time to port some simple LCD feedback to the same patch so that the iPad displays the same sort of thing that the LCD patch in m4l does).
Just wanted to post a short update, I'll be in touch. Cheers.
a
11.1.11
Its out.
Beta testers have it. Hopefully all goes well and I can have it out to the public in a week. Stay tuned....
Subscribe to:
Posts (Atom)