mike@TrackTeam Audio wrote:
As far as Max MSP literature goes, ive heard the Winkler book is a bit outdated, but if your looking for something to supplement Max's own documentation, download this PDF, lots of goodies in there...
http://www.cycling74.com/forums/index.p ... 10aa3508d5
Note that when passing around URLs to Cycling's forums, you don't need to include the "S=XXX..." (or the rid=0 part) -- this is the session id and unnecessary, and in fact, can thwart you when trying to download a file. The proper URL would be:
http://www.cycling74.com/forums/index.p ... le&id=1007
BTW, as far as the comparisons between Max and Reaktor go, while there is quite a bit of overlap between these two patching environments, really they have very different focuses and philosophies.
I've been a Reaktor user since v.3, and a Max/MSP user since v.4. What I have found is that Reaktor has a very strong inclination towards synthesis and sampling, with some strong, but limited sequencing options. There is an unbelievable number of ready-made ensembles and instruments, so much so that unless you really want to, you don't have to make anything "from scratch".
With Max, the focus is not so much on synthesis and sampling, although it's certainly capable of both. Max, for a lot of people, functions as a "glue" between different systems. I have a friend, for example, that has been working on a patch to control his CyberLights (using a DMX protocol object) and do live video processing/fx as well -- so he's basically using Max for the visual component of his A/V PA (I think he's using Renoise for the audio).
One of the old Max mottos used to be "control anything with anything" and that's as apt a description as any. Go to
http://www.maxobjects.com and you'll find Python objects, objects for use with MsPinky control vinyl for building your own digital DJ solution, externals that allow you interact with a unix or DOS shell, OSC implementations, etc.
On the other hand, what you won't find is a centralized repository of ready-made Max instruments, etc. This is due to the cultural differences between Max and Reaktor. While Reaktor encourages capitalizing on other people's existing work, Max sort of has a culture of "build everything from scratch". You'll see this when asking questions on the Cycling forums. People are less apt to flat out give you a patch that does what you describe than give you bits and pieces and suggest you look in a certain direction.
I'd also say that until v.5, Reaktor had a big leg up in the usability dept, although that playing field seems much more leveled at this point. Also, beyond the shadow of a doubt, Max's documentation is very very good, some of the best I've encountered in any audio application, heck any software application PERIOD.
Now, in the interest of full disclosure, I work for Cycling 74. However, I speak these words as a user, and not in any official capacity. These are my honest opinions and I'm not saying any of these things about Max to encourage a sale. I love Reaktor, have for years, and to tell you the truth, if I'm going to build a synth/sampler, I'll reach for Reaktor before I reach for Max. On the other hand, Max is much stronger IMO for building sequencers, although Reaktor allows for a bit more direct approach to this task.
) and you get Jitter on top!