Can anybody confirm how MC is supposed to send MIDI CC?
I was under the impression that T1 sends on midi-channel 1, T2 sends on midi-channel 2, etc… (which is obviously configurable, of course). I replicated a quick m4live-device (attached) with “midiselect” to unpack and have look at incoming MIDI-data. But no matter whether note-data or MIDI-CC, it’s always channel 1 that is banging. Probably I’m just an idiot, but can anyone offer some ideas? Shouldn’t it be MIDI-channel 2 that is banging when I hit a pad or CC on T2?
I remember that Ableton - no matter what you select in the MIDI IN Channel box - always uses Channel 1 after it has been passed through to the devices.
If you select channel 2 as input it will only pass through that channel, but then in the track it is channel 1. You can use the M4L midi monitor to verify that… Not at my computer atm.
Thank you! I believe this is what I am trying to do right now and what is indeed happening. I’d love to control my device from the MC-hardware and vice versa, the limitation seems to be with Ableton and/or my understanding of how MIDI is routed within. There are external libs for M4L like imp.midi but I am actually running into other issues (timing) with MC right now.
Thx, seen that! It’s great! Yet building my own controller at the moment, really a cool learning experience, Max for Live is a fantastic MIDI-data-and-numbers-manipulator.
