Ableton Forum

Inside a max midi effect I see the reported midi channel of a xnotein (or for that matter any midi object) is always channel 1. This is true even if the parent Live track is set to only listen to midi incoming on channel 2.

I was hoping to use a single live track to monitor midi on all channels from a hardware device and split the processing chain based on midi channel of message.

Is this behaviour a bug or am I missing something here?

It's an intentional limitation by design, but you may call it a "design bug".

Yeah a really annoying limitation together with the fact that MFL can't access its own midi ports makes it hard to centralize controls for multiple devices with one MFL device.I'm planning to use send/recieve + a track for each channel piped though virtual midi ports to overcome this, but results in many more tracks, I also use Bidule to receive and distribute multi channel data.

http://forum.ableton.com/viewtopic.php?f=35&t=128795 is a workaround for this.

Thanks for the answers... This is a bit of a bitch when added to Audio FX not being able to receive Midi either.
ho hum.

Dionysiac wrote:Thanks for the answers... This is a bit of a bitch when added to Audio FX not being able to receive Midi either.
ho hum.

what exactly do you want to do?
I may not understand.

do you want to use a midi channel with, inside, an instrument and make the midi flow to go out another midi channel? it is possible with send/receive as I wrote in the workaround.

I'm using it with the protodeck controller.
I want to use midi instrument BUT catching the midi flow that goes into these instruments in order to make it goes out into the protodeck controller hardware.

julienb wrote: what exactly do you want to do?
I may not understand.

I was trying to create a custom object to accept midi messages from 4 layers of a Tenori-On in score mode to use as gate triggers for a multiband dynamic gate effect. I have it working already using 4 midi channels that fire a hihat and sidechain into the gate device. This seems to be a bit clunky given that we have M4L now.

Ideally I would be able to build a M4L midi controlled gate audio FX device that listened to a port/channel combo and gated on midi note. However one can not access midi data inside an audio device so thats a no go.

Next solution is to have a pair of devices; a midi satellite that grabs the midi and then uses internal OSC to send trigger messages to the audio gate devices. (internal OSC because the send/recieve is too slow. I am told OSC will be faster). However because of the limitation of only one channel per track I am back at using 4 satellite tracks and at this point it becomes a big fat waste of time and I give up and carry on adding 4 tracks of hihat to every set I want to use this technique in.

Thanks for the input but I will have to shelf this particular device until the M4L capabilities change.

adding a midiin in a Max audio fx isn't forbidden.

julienb wrote:adding a midiin in a Max audio fx isn't forbidden.

But how would you route midi into the audio fx?

max audio effect device, max instru device & max midi effect device doesn't behave equally.
indeed, you have to workaround to make it ok.
I don't have a lot of time now...
I'm sure you can find the answer in the manner I'm grabbing midi note from each tracks and reroute all of them in particular midi channel inside the patch in the first track.
check it here: http://www.julienbayle.net/diy/protodeck/#m4L

mail me if problem.

Thanks, but I was hoping for a straight solution..

broc wrote:Thanks, but I was hoping for a straight solution..

I guess it cannot be done like that

BUT if you use send/receive, indeed, you can route data flow as you want.
it could add cpu consumption but, it is another workaround so...


I'm sure we miss one general m4l device instead of the 3 already provided.
a kind of superdevice we could connect in/out, audio/midi/other.
there are several post about that.
for instance, my interface patch isn't a midi effect max device, a audio effect max device or an instrument.. it is "only" a big interface.

in my patch, you can check that.
the superdevice would equal to:
- my first track + the interface patch
- all the workarounded track for midi re-routing etc

I'll save tracks and cpu consumption...

julienb wrote:I'm sure we miss one general m4l device instead of the 3 already provided.
a kind of superdevice we could connect in/out, audio/midi/other.

Unfortunately the device types are imposed from Live. So we need some redesign ala Reaper..

broc wrote:

julienb wrote:I'm sure we miss one general m4l device instead of the 3 already provided.
a kind of superdevice we could connect in/out, audio/midi/other.

Unfortunately the device types are imposed from Live. So we need some redesign ala Reaper..

obviously.
but workaround are fine too and works.
I guess we can deal with til this hypothetical redesign...