Is there someone that can explain to me why, when using the m4l patch joined, the midi channel stay on 1, even if the controller is on channel 4 (but in the same time, the box for ctrl change works ok, even for a controller on channel 4).
I don't get it…
help monitoring midi from lemur in m4l
Re: help monitoring midi from lemur in m4l
I haven't downloaded your M4l patch but perhaps you would be interested to know that Ableton Live does some tricky stuff with midi channels. While working on some M4ls of my own it became clear to me that Live takes all incoming midi channels and processes them in the midi tracks as midi channel 1.
For example if you have a controller that sends CC values on channel 4 and you have a a midi track in Ableton Live this happens:
Controller CC on ch4 -> Ableton Live midi ports (ch4) -> midi track input (ch4) -> internal transformation to ch1 -> any plug ins, m4l patches inside the midi track are receiving now midi messages on ch1 (even though its input may have been set to receive on ch4)
I dont know if the above clarify the issue - make it clear for you. Lets say you have a plug in or M4l patch and there is a setting to receive CC on a specific channel. WHATEVER you do, inside Ableton Live it will only work if it receives on ch1.
For example if you have a controller that sends CC values on channel 4 and you have a a midi track in Ableton Live this happens:
Controller CC on ch4 -> Ableton Live midi ports (ch4) -> midi track input (ch4) -> internal transformation to ch1 -> any plug ins, m4l patches inside the midi track are receiving now midi messages on ch1 (even though its input may have been set to receive on ch4)
I dont know if the above clarify the issue - make it clear for you. Lets say you have a plug in or M4l patch and there is a setting to receive CC on a specific channel. WHATEVER you do, inside Ableton Live it will only work if it receives on ch1.
Last edited by Softcore on 08 Mar 2013 09:53, edited 1 time in total.
Re: help monitoring midi from lemur in m4l
Oh thanks, that's the answer.
I was trying to filter a specific midi ctrl (ch4, ctrl10) using a m4l patch that was on a midi track set to channel 1 as input.
If I put my m4l filter on a midi track set to ch4 as input, it works ok.
So as you said, Live is quite tricky. We can forget about the midi channel output of the ctrlin in m4l. This has to be done by setting the correct channel input on the track.
Thanks again, I was slightly becoming mad with this
I was trying to filter a specific midi ctrl (ch4, ctrl10) using a m4l patch that was on a midi track set to channel 1 as input.
If I put my m4l filter on a midi track set to ch4 as input, it works ok.
So as you said, Live is quite tricky. We can forget about the midi channel output of the ctrlin in m4l. This has to be done by setting the correct channel input on the track.
Thanks again, I was slightly becoming mad with this
Re: help monitoring midi from lemur in m4l
Exactly!frz wrote: We can forget about the midi channel output of the ctrlin in m4l. This has to be done by setting the correct channel input on the track.
Re: help monitoring midi from lemur in m4l
Ahhh - so that's it.
Got very close to discovering this for ourselves here at the lab the other night, setting up a Live Set to accomodate NI Maschine.
We managed to figure out there was some shenanigans afoot with MIDI chans and got it working but didn't go on to nail the problem down with such specificity.
Good work, chap.
[edit]
Not that Maschine doesn't have quirks of its own in this dept.
Got very close to discovering this for ourselves here at the lab the other night, setting up a Live Set to accomodate NI Maschine.
We managed to figure out there was some shenanigans afoot with MIDI chans and got it working but didn't go on to nail the problem down with such specificity.
Good work, chap.
[edit]
Not that Maschine doesn't have quirks of its own in this dept.