Closure()

I’m getting very close with this b993 thing….I worked out the bug with the DeviceControlComponent earlier this evening….a simple problem with a complicated fix that was simply implemented by a closure in the right place.  I love closures 🙂

I’ve gotten a little feedback from users of a test release of b993, and no one has had anything bad to say.  All that’s left to do is tidy up the packaging, add a mute indicator for the new ModMute functionality, and add the MonoLinkClient support to the half of the Python scripts that it hasn’t been already ammended.  You’ll like it, I think. More details about this with the release, and I need to hand it off to a couple of beta testers, but here’s a teaser, if you haven’t already seen it, from about a week ago (when I’d just confirmed it was possible):

What does that mean?  Well, I’ve assembled a new Monoclient script that lives in Monomodular, and it’s capable of sending and receiving  directly from Live via _osc._udp (this isn’t really news, LiveOSC has been doing it forever); it also publishes all its connection information via ZeroConf/Bonjour, so any of the new monome patches supporting serialosc will be VERY easy to connect to.  This means that your grid-based, Monomodular compliant device will now be a ‘ringer’ for a real monome, sharing its connection protocol without needing any intermediary apps.  Just load the scripts in Live, and all the connection configuration can be handled by pressing ‘Alt’ and entering the information from the grid.  If it’s a serialosc app your trying to connect to, you don’t even need to do that:  you just hit the ‘connect’ button on the monome app, and your device will be automagically connected.  YOU DON’T NEED M4L.  It’s not going to be as fast as the m4l monolink, but I’ve been using it over the last several days, and its plenty fast for most things.  The proof will be in the pudding, though, I guess.

Oh, and I’m now taking suggestions to add to the default user configuration file for handling automatic (preset) connections.  What does that mean?  Well, basically, I want to know what the most popular monome apps are among users, and I’ll put their connection information into the script so you don’t have to do it later.  Right now, I have Polygome, Molar, and 7up in the registry, but I need twelve more.  They can be serialosc or monomeserial, as the new script does both types of connections.  You can always input the port data directly by way of the Mod grid, but the User Configuration file will allow you to store 16 preset addresses (as well as their prefixes and communication protocols) so you can get to them quickly, just like you would with normal Mods in m4l.

At this point it looks like b993 is going to be the testing ground for a whole lot of new things.

a

~ by amounra on March 6, 2012.

11 Responses to “Closure()”

  1. Fantabulous. All I have to say.

  2. can we have support for party van?please

  3. Hi Man, really great work!! I trying to make all work but I can’t figure out were I go wrong, could you help me out? I’m running ableton live 8.2.6 and Max 6. I’v downloaded the b993 content and use the OSX installer. I choose blockmod and monomodular in the midi device setting in ableton preferences. I also downloaded polygome from monome website, the serialosc version. I did all the steps you show in the latest video but when I open up polygome it says “not connected” in the lower left corner and it doesn’t recognize monomodular from the list option. I really need your help ’cause I love this stuff!!

    • Hey Paolo,

      Sounds like you found the easter egg 😉 I haven’t announced it yet because I’m still trying to get the docs finished. In the meantime, here’s a better description of the component:

      http://www.aumhaa.com/wiki/index.php?title=MonoLinkComponent

      Also, none of this has been tested with Max6, and when I’ve accidentally started my own sessions after mistakenly forgetting to switch to Max 5.19 nothing worked as it should. The new MonoLinkComponent stuff should probably work, but I don’t know about the regular m4l stuff.

      You may need to try switching channels once in MonoLinkComponent mode in order to get Bonjour started…keep in mind, this is all still VERY beta….let me know how you make out.

      a

      • Sorry guy, I was so excited to get hands on it I didn’t realize you were still working on it! I had troubles with the previous release (b992): I couldn’t even download it, never knew why. So now I?m craving for this release. Just a question, If I changed channel in block editor, ableton live and monomodular stop recognizing block. I guess I have to change something also in ableton or monomodular but I can’t figure out what. Sorry If my programming knowledge isn’t so wide and thanks again

      • I definitely know that some things don’t work correctly when trying to run Monomodular with Max6. Connections to clients don’t initialize correctly for me….that’s about as far as I’ve gotten in testing it.

        The new MonoLink capabilities should work fine with any version of Max, since they don’t have anything to do with it. However, I don’t know if Polygome will work correctly with Max 6 (I haven’t tried it).

        If you want to change the channel for the Block in the scripts, you can do so in the main BlockMod.py file. Just change the part at the top that says:

        CHANNEL = 0

        To whatever channel you want to use (0 = channel one, 1 = channel two, etc).

  4. @paolo

    So you’re using the Livid Block, nice. If you are having problems, make sure to use Max 5 just to be sure. Or, you could use the polygome mod that is included with the monomodular suite, it works basically the same, however, you’ll have to have m4l for that. If you don’t have m4l, you can still use the polygome but maybe with the max 5.1.9 runtime. When you pull up the blockmod, are you able to get any other feedback?

    • Do you think some problems may rise because I’m running max6 instead of 5? I’m trying these days to make all work but I’m quite new to midi controllerism. I was using touchosc on my iphone till the last year, when I bought this fabolous controller from livid. I’m sailing through forums, youtube tutorial and blog. Hope I’ll get on the right way as soon as possible! What you mean with “feedback” when I pulled up monomod? I can switch from monomod and monolink if that helps 🙂

      • By feedback I just mean that you are getting led responses when you press buttons, etc. The MonoLink client as mentioned above doesn’t rely on max4live, but other devices will. For the time being you are probably best off sticking with max5/max5 runtime for your max4live stuff (if you are using the monomodular mods packaged). However, if you are just wanting to use monomod with MonoLink mode so that you can run pure monome apps, then try Max 5 just to see if it connects properly. Apparently Ableton and Cycling 74 are working on a version update for m4l.

Leave a Reply