Add new comment

however,

that's the reason why CC#10 it appearing in the screenshot above and not the custom cc#3: it is being captured by the dialog in real-time, due to so called "MIDI Learn" feature; as long you don't hit the "OK" or "Reset" buttons your previous assignment won't get dismissed.

and, what kind of automation are you trying to achieve on buses with all this? it seems to me, that you're about to get the trouble in having a nasty positive feedback loop and hosing the MIDI track in question (eg. MIDI track vol/pan -> CCauto out -> Control in -> MIDI track vol/pan)...

now, qtractor >= 0.9.39.12git.16452b is set to mitigate the effect but only applies to standard MIDI track volume and panning controllers and most probable cause for the OP (non-selectable clip issue).

hth.