Yes, indeed that’s helpful. I think I’ll bookmark this thread… and MidiOx is (still) my faithful friend for decades now.
This feature looks weird but it’s actually quite useful!
There is however a question on the direct connect feature I don’t understand yet.
I want to control the crossfader with a midi footpedal. The midi implementation chart says: crossfader = CC #48. It doesn’t state a channel. So I programmed my pedal to send this CC on the autochannel. I was in midi mode and had a midi track active, I saw in Midi Ox that the message was thru’d but had it’s channel changed to the channel of the active track. So this re-routing is applied to CC’s as well, not only PC’s, as stated above quote. (As was mentioned before…)
But the crossfader did’t react. I checked and had direct connect on. (then read this thread to confirm what was happening). I don’t understand this, because in the manual, appendix C.2 (CC mappings) there’s no hint that this shouldn’t work. So I unchecked direct connect and now the crossfader reacts to my footpedal.
In the manual, appendix C.3(autochannel CC mappings with direct connect OFF) CC#48 is unused. But it’s the only way to map to the crossfader! I’m puzzled…
EDIT:
C.3 MIDI MODE CTRL CHANGE MAPPINGSWhile in MIDI mode and CC DIRECT CONNECT is deactivated, the auto channel responds to the following CC messages.
Which explains why crossfader control over midi doesn’t work in midi mode, only in audio mode (yet one more WTF moment explained).
But I still don’t understand why it doesn’t work with direct connect ON…