I'm hooking up a Jitter patch for the first time in M4L, and I'm wondering where to put my actual patch. Ideally I could have one Jitter patch and be able to route different MIDI and Audio tracks to it to manipulate the patch in various ways. How to route this stuff I'm not sure, and I've experienced certain problems when it comes to putting the patch in my MIDI track or Audio track that I want to manipulate. How have folks been doing this? Any suggestions?

I'm hooking up a Jitter patch for the first time in M4L, and I'm wondering where to put my actual patch.  Ideally I could have one Jitter patch and be able to route different MIDI and Audio tracks to it to manipulate the patch in various ways.  How to route this stuff I'm not sure, and I've experienced certain problems when it comes to putting the patch in my MIDI track or Audio track that I want to manipulate.  How have folks been doing this?  Any suggestions?

routing-midi-and-audio-to-jitter-in-m4l

M4L devices can receive either MIDI or Audio, not both at the same time.

This restriction is imposed by Live's track types.

A possible work around would be to put the device on an Audio track and feed MIDI into it from another device via Max send/receive objects. But unfortunately this introduces some (unpredictable) latency. So it's not suitable for time-critical data.

M4L devices can receive either MIDI or Audio, not both at the same time.
This restriction is imposed by Live's track types.

A possible work around would be to put the device on an Audio track and feed MIDI into it from another device via Max send/receive objects. But unfortunately this introduces some (unpredictable) latency. So it's not suitable for time-critical data.


When I wanted to send velocity data from Ms Pinky from one device to another as quickly as possible I used live.remote~ to control a parameter in the other one.

routing MIDI and Audio to Jitter in M4L