Max

A group of Jamoma-developers presented a paper suggesting an extension to OSC at this year’s NIME in Genova two weeks ago: Reference: Place, T., T. Lossius, A. R. Jensenius, N. Peters and P. Baltazar (2008): Proceedings of the 2008 International Conference on New Interfaces for Musical Expression, 5-7 June 2008, Genova. Downloads: Full paper Poster Abstract: An approach for creating structured Open Sound Control (OSC) messages by separating the addressing of node values and node properties is suggested....

One of my reasons for developing motiongrams was to have a solution for visualising movement in a way that would be compatible to spectrograms. That way it would be possible to study how movement is evolving over time, in relation to how the audio is changing over time. In my current implementation of motiongrams in Max/MSP/Jitter (and partially in EyesWeb), there has been no way to synchronise with a spectrogram. The problem was that the built-in spectrogram in Max/MSP was running much faster than the motiongram, and they was therefore out of sync from the start....

Some pictures from our Jamoma workshop after NIME: {width=“400” height=“237”} Pascal showing the ramping and mapping magic in Jamoma. {width=“400” height=“252”} Tim showing that Jamoma is soon to be working in Max 5.

Richard Widerberg held a workshop today on using mobile python on Nokia phones running Symbian OS S60. He has gathered some links to everything that is needed to get a connection up and running with PD. Now I got a simple script up and running and communicating with Max/MSP through the serial object. It works, but it feels a bit limiting to only have one-dimensional control joystick up/down + number keys for interaction....

Cycling ‘74 has released Max 5! I have been beta-testing the software for some time now, and can highly recommend the update. There has been a lot of discussion about the new “rounded corners”, but Max 5 is so much more about improvements and workflow. What I like the most about Max 5 is the presentation mode, which allows for separating the “code” from the user interface. This greatly enhances creating more complex patches with a neat little interface on top, since you can easily select which objects to include in the presentation, and then rearrange them as you like....

We had a programming session this morning, and Paolo Coletta implemented a block for creating motiongrams in EyesWeb. It will be available in the new EyesWeb XMI release which will happen in the end of this week. Great!

I am participating in the EyesWeb Week in Genoa this week. This morning Nicola Bernardini held a lecture about Free Software. I have heard him talk on this topic several times before, but as I have now some more experience on participating in a Free Software project (i.e. Jamoma), I got more out of his ideas. Some main points from the talk: Use Free Software! Freeware and shareware may have nothing to do with Free Software....

I have had problems with SubEthaEdit making Max/MSP .mxo externals show up as folders instead of packages. I type the solution here so that I won’t get forget it anymore (thanks to jasch for figuring this out): Right click on SubEthaEdit and select “show package contents” Open the Info.plist file in a text editor Remove the line with mxo Save and restart

The newly refurbished OSC forum web site has sparked off some discussions on the OSC_dev mailing list. One interesting note was a reply from Andy W. Schmeder on how OSC should be spelled out correctly: The short answer is, use “Open Sound Control”. The other form one may encounter is “OpenSound Control”, but we don’t use that anymore. Any additional forms you may encounter are probably unintentional. I have been using various versions over the years (also including OpenSoundControl), I guess this is then an official answer since Andy is working at CNMAT....

I am updating the GDIF messaging in the jmod.mouse module in Jamoma. Trond suggested to use the OpenGL convention for ranges and coordinate systems, which should give something like this: {width=“414” height=“270”} This means that values on the vertical axis would fall between [-1 1], while values on the horizontal axis would be dependent on the size of the screen. For my screen (1280x800) this gives a range of [-1.6 1....