Week 10 - Class 1
By popular request, we are going to talk about interfacing with other software/processes.
Max with Max
First, it is useful to talk about ways to get Max patches to work with each other. To do this, you can use:
- send/receive (s and r): sending Max messages back and forth.
- send~/receive~: sending MSP audio streams back and forth.
- udpsend/udpreceive: sending data over a network to another computer's Max patch.
- [mxj net.tcp.send] and [mxj net.tcp.receive]: network discussion using tcp
- [mxj net.udp.send] and [mxj net.udp.receive]: network discussion using udp
- [mxj net.maxhole]: the simplest network communication
- jit.net.send and jit.net.receive: sending jitter matrices over a network
But we may want to move beyond Max! For this, you have a few options:
- To interact with MIDI, you can use the Max virtual ports.
- To interact with Rewire software, you can use the ad_rewire audio driver or rewire~ object.
- You can also use hardware options (which often will work best...)
Let's look at Rewire. To act as a Rewire client (meaning that something else interacts with the audio outputs...), you change the Audio Status driver type to ad_rewire:
When you do this, the audio output of Max appears as a new device within (in this case) Ableton Live. If you want more details, you can check out the documentation page:
Finding other ways to interact can take many paths. You can find more in another documentation pay:
Perhaps the most interesting way to interact with another software package is to look at the tight integration between Max and Ableton Live via the Max for Live product. We will look at this in class:
Week 10 - Class 2
Sorry, but illness prevails. I'm not going to be able to do this one...
Return to the class index.
Last update: 03/09/2015