Some of you may have heard that major changes are imminent in the Max world, and there is a lot of speculation about what those changes might be. On the eve of our first public exposition of the new version of Max at the AES convention in New York, I thought it would be appropriate to offer some details on the product.
Last week I arrived home from a 'vacation' in France. In my case though, the term 'vacation' means that I was programming and debugging objects for Max/MSP/Jitter. The occasion for this trip to France were two workshops focusing on Jamoma that were organized by Pascal Baltazar, GMEA, and Incidents Mémorables. The workshops [described in this article] were held in Albi and Paris, respectively.
This is perhaps an unusual article for Cycling '74 to put on their web site, because it has to do with all the languages that Max/MSP isn't. I have to confess that I'm not really a very good Max-user. I know only a handful of objects, and I am of the text-based generation that is still a little, um, "graphical-user-interface-challenged". I basically use Max/MSP only as a window onto computer music languages that I am adept at using. More and more, though, I am also using Max as base platform for connecting these languages to each other. One of the really great decisions that the Cycling '74 design team made was to make the development and integration of external objects relatively easy. This has been a real boost for the classes that I teach at Columbia University, and it has also allowed me much more creative freedom in my compositional work.
One of the beauties of Max is its simplicity: the ability to quickly create a patch that does something artistically interesting. Part of this has to do with its visual programming style - patchcords allow us to see the relationship between graphic objects. However, unless you limit yourself to creating only straightforward patches, your patch can become a spaghetti-like series of connections that confound attempts at debugging. Please note: This article was written for Max 4.6 originally
Matthew Lewis: Education through synesthetic study and play.
In this tutorial, Nick Rothwell will lead us through the process of setting up the powerful Eclipse IDE for creating MXJ objects for Max.
This is a quick rundown of how the MXJ class loader works, and the implications for class variables (statics).
you can send any Max mxj object the viewsource message (Even if you don't have the source, the viewsource message will decompile it for you if you have the Java class file!) to check on