I'm doing that with all my tracks to monitor midi note on on my controller.
I created the same number of midi track, each one sending midi message to my interface (patch) track.
midiselecting things in m4L works fine.
but it isn't exactly the problem here (I may probably not explain it as well)
I have a controller, I have my interface patch, I have Live.
between controller and patch, I need to have 16 channel midi message feature!!
between patch and live, I only use API. excepted for the midi note on message monitoring I explained before.
I'd be really disappointed if I couldn't send/receive midi message from channels 1-16 in one track...!
I guess it is because I don't know how to do that, and not because of a limitation in this case...
indeed, in the track where the interface m4L patch sits, there is the option "MIDI FROM" and under that the midi channel and I can choose channel 1, 2 ....... 16 or ALL.
btw, I tested it: it doesn't work.
when I send midi message on channel N, if N is selected as a MIDI FROM track, the message is sent to the patch inside the track.......................... but the patch ALWAYS receives as if
the message came from midi channel 1
I'll have to think about my patch VERY differently !!!!!
or ... I tweak my python script as an old school guy... and I won't but m4L
the second option would be very bad for me (not for abes...
PLEASE ABES, HELP US with our poor midi protocol !!