I use a Faderfox PC12 to control my OT. The pot I have set up to change amp volume (cc 25) to audio track 3 is somehow sending a signal to solo that track and I can’t for the life of me figure out how or why. It only happens when that controller value goes above 0 two consecutive times after the sequencer has been started. If I go into the mix view and unsolo the rack it won’t happen again unless I stop and restart the sequencer. The PC12 isn’t capable of macro control so I don’t know why the OT acts like a cc 50 control change is coming in from that pot (and I confirmed with a MIDI monitor that the pot is only sending 25.) It only happens on that one track - a Static machine that is configured exactly like two other tracks which don’t have this behavior. This only happens if I adjust track 3 volume from the PC12, and doesn’t happen if I do it directly on the OT.
actually the PC12 has hidden macro control if one can call it like that, It understands certain commands meant to setup the device, as written in the manual.
That aside, CC25 is not part of NRPN message specs, nor RPN msgs, so that it can not be.
That it doesnt happen on OT directly tells it clearly is a midi misinterpretation or unexpected misrouting as of your setup. Another way of messing around is having PC12 send properly but receiving on OT on Autochannel (ch?) & dedicated Midi channel (likely 3) to control that track, in that case it is clear what shall happen but who knows if that declaration is true under any circumstance.
Of course you eleminated the possiblity to let OT send Midi to itself via PC12 to avoid clash scenarios before asking elektronauts for a better guess.
and for fun of math a flip can be explained also by…
00011001 (25)
00110010 (50)
see the pattern, a bitshift would be enough. Then comes the question how, if that is even the source of problem, could a bitshift happen. (in example rotten cable, broken quartz, noisy electric environment causing interference, weak power supply, rerouting into itself and many more…, you could confirm a bitshift problem when CC100 is also affected because that is 01100100, if that would happen on 4th round the gun smokes).
You can also, if you have an extra midi interface, messure what comes out of OT midi thru to confirm what is passing into it. MIDI Thru data is meant to leave the OT un-altered aftr receiving. If that would contain the cc50 but pc12 never send it but a cc25 then you could confirm with high likelihood a byte misalignment bug.
Interesting info wrt the potential bitshift. I took the OT out of studio mode and the problem stopped. Even after switching it back to studio mode, I can’t re-create the issue. But if it happens again I will monitor the thru output of the OT.
Thanks!