Add new comment

The MIDI track channel volume and panel events are sent to regular output bus, to which the MIDI track is assigned, not the dedicated control bus. If you setup a dedicated output control bus you'll miss those events. If you really want, you can turn the dedicated control outputs off and connect the MIDI Master Out bus to the BCF2000. However now that's where all events go, as it's not dedicated to control events anymore.

Re. qtractorMainForm::midiControlEvent() is where inbound controller events are dispatched (ie. received) and in fact is the single place to look on the JLCooper-like stuff. Take care that, for having proper feedback, you must not replicate the incoming events to output. You would need to send the corresponding MIDI CC events when and only when a session view element (eg. mixer widget slider) or the model data changes--refer to the MVC pattern ;) All that to say that things are not that straight-forward at this time. A direct and naive approach could turn into an endless feedback loop and crash-landing imminent. There are many parts involved and refactoring is always one of such needs. Anyway, all that will be taken care while in proper MIDI controller map implementation so I'll ask for your patience ;)

Cheers