it’s ok, everyone…I think I’ve caused enough pain for one night! Everyone’s info has been really helpful, I’m sure I’ll get to the the bottom of it or find another way to achieve the same thing. Maybe it’s time to close this can of worms…! I agree, time to make some music instead 
3 Likes
Checked the astrology, today is not a good day for OT PC trouble shooting… 
Sh*t we messed this thread up good… CC direct connect on/off autochannel/midi channel behavior only applies to CC’s! Says right in the manual…
I shoulda stayed out of this one today, haha!
Have fun people’s, till next time!
3 Likes
This info might be useful, from da manual:
For the second quote I don’t believe it has to be the active track if it’s the midi channel, the manual says this in other sections too but I believe active track only matters for autochannel, and midi track channels always pass through (unless an audio track and a MIDI track share the same MIDI channel, the MIDI track will block the audio track from sending out data while the audio track will block the MIDI track from receiving data.)
Also it seems from what I’m reading in the thread (can’t test) that program changes are included with notes to be passed through…
2 Likes
Yes these things sound correct and it’s reflected in what I’m seeing in my project. Because I couldn’t find a way around the problem, I’ve started using Note On Messages to trigger the buttons on my Lemur instead which as it turns out is actually a more useful way of working as I can use Plays Free and have multiple button presses on a single track pattern if I wish. As is always the case this has thrown up another set of problems which I’m currently trying to figure out however I’ve made some progress at least so thank you for all the help and info you provided, hugely appreciated.
2 Likes
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…
Nope. It is the lowest audio channel, NOT shared with a midi track.
Channel 1 by default, default audio channels being 1-8.
Channel 2 if you use a midi track on channel 1. Channel 3 if you use a midi track on channel 2.
Etc…
Without audio channels set, I’m not sure it sends data.
Ok, so that was what you were talking about earlier. I didn’t get that. Thanks. I indeed have switched off all incoming channels, I don’t want any, there’s way too much midi going on with overlapping CC commands between devices.
I tried and it works as you described. That’s quite a drag. I have all 16 channels populated with midi devices, and patch them in if necessary so I never know what the lowest audio channel will be, and we must indeed SEND to that channel and I am not very happy with the idea that I need to re-program the pedalboard each time I change songs/projects when assignments have changed. I thought the autochannel would take care of that, but nope…
You mean “it receives data”… it does, but only in audio mode
I meant crossfader sending data. What channel is used in that case? 1?
Ok figured it out, the lowest audio channel must not be equal to the auto-channel.
So the deal for commanding the crossfader (or to receive whatever other CC is in the C.2 appendix list) over midi is:
-have at least one midi channel assigned to an audio channel
-must not be shared with a midi channel
-must not be shared with the autochannel
-doesn’t matter if direct connect is on or off
The crossfader sends on the lowest audiochannel as well, I just checked. If no midi channel assigned to an audio channel it will not send data. EDIT: But the encoders will always send on the active channel. So the crossfader behaves differently from the other OT controls.
1 Like
not if the active track channel is set to off and if a midi track has same channel, AFAIK.
3 Likes
Crossfader is an audio side cc, must have “audio cc in” checked to recieve, audio cc out either “int+ext” or “ext” to send, and have an audio trig channel or autochannel set… I think it will receive on any channel set on the audio channels or autochannel if one is set, will send on lowest channel…
Not going to type out every specific other detail of audio side/midi side/autochannel/CCdc conflicts which sure one could do but I don’t see why we need to over and over, just pointing out the above and leaving it there… 
Somebody else can fill that in if they want… 
4 Likes
I don’t even use the autochannel, just midi channels…
I’ve had my OT working perfectly fine with all manner of midi going back and forth without issue, works great and I feel I understand it. Yet when I read this thread it becomes so confusing… Haha…
4 Likes
Scenes behave the same.
This happens on other threads too. I feel like I understand very well a concept and then when it is discussed for clarity that’s when it becomes confusing…
First Rule about OT behaviors: You don’t talk about OT behaviors…
1 Like
No that’s what I started with. Autochannel doesn’t work that way… I thought it would, but no.
Remember autochannel controls the active track…
With an autochannel set and an audio track selected, does it recieve crossfader CC 48 then? My OTs napping in storage again or I’d test…
If you want to control it while on the midi side you can not use the autochannel you have to use a set audio channel.
(maybe the exception is with CCdc unchecked it will still work as there is no CC48 on the midi mode CC mapping (which applies when CCdc is unchecked) so it sends it to audio side )
Yes that’s what I reported. Autochannel does only work when in audiomode. Sending on a defined channel except the autochannel works in both modes. I think that’s a confusing architecture.