Ableton Forum

Hi everyone! I'm trying to write simple M4L device with few MIDI CC's which i can control and automate. The problem is that i want to route these CC's onto different MIDI-channels at once. Is that possible? Who can give me a piece of code? Thanks a lot and have a nice day!

thats not possible, in Live all is merged to midi channel 1.

Even with MPE we can’t address midi to specific channels. It’s a shame.
Please send feature requests.

That said there is a workaround, which is to use the M4L control surface. It’s a pain to use and somehow proves it’s a weird limitation.

Yes, think that an feature request since decades. Like VST3 program Change / Parameteres etc.

If you want to do that you need a workaroud like:

dedicated device on separate track and a master

and send the data from the master to the devices via

send / receive (timing not the best!)
mapping a control
via 14Bit CCs (msb for channel)

Look into udpsend/udpreceive. I've written a few M4L sequencing patches that all operate on the basis of having everything in one patch controlling different stuff across 2 or 3 midi tracks, utilising a fairly straightforward udpsend/receive system. Not sure if that's maybe what you're looking for..?

christianlukegates wrote: ↑

Tue Mar 26, 2024 10:48 am

Look into udpsend/udpreceive. I've written a few M4L sequencing patches that all operate on the basis of having everything in one patch controlling different stuff across 2 or 3 midi tracks, utilising a fairly straightforward udpsend/receive system. Not sure if that's maybe what you're looking for..?

In my experience, any kind of send/receive will add an unpredictable latency, which is sometimes critical.
The best trick I've found is to use a CC before each note as a flag to specify the voice number. It works well as the CCs are treated "before" notes in Max, and as it's only MIDI it stays in the high priority thread of Live.

idk, my patches are all types of sequencer that hinge on super tight timing and while I had that same concern prior to building them, in use they are solid. Most of the patches are written largely in RNBO tho so that may have some bearing on timing, event scheduling or whatever