I'm not sure how this would lend itself to the scenario where the session (instruments and routing) are handled by Carla rather than Qtractor. Traditionally, I've loaded my Qtractor project first in order to create the ports. Then I load the corresponding .carxp file in Carla in order to load the instruments and connect everything.Based on what we're saying here, I now understand why those controllers being sent by Qtractor had no effect.
If I swap the work flow and load Carla first, I have instruments loaded and ports established but they're not routed (which makes sense since Qtractor is not open). Loading the Qtractor project results in the audio routes being established but not the MIDI.
So basically, it would appear as if the method by which these controllers are sent is really centered around the assumption that Qtractor is being used in a stand-alone fashion?
I'm not sure how this would lend itself to the scenario where the session (instruments and routing) are handled by Carla rather than Qtractor. Traditionally, I've loaded my Qtractor project first in order to create the ports. Then I load the corresponding .carxp file in Carla in order to load the instruments and connect everything.Based on what we're saying here, I now understand why those controllers being sent by Qtractor had no effect.
If I swap the work flow and load Carla first, I have instruments loaded and ports established but they're not routed (which makes sense since Qtractor is not open). Loading the Qtractor project results in the audio routes being established but not the MIDI.
So basically, it would appear as if the method by which these controllers are sent is really centered around the assumption that Qtractor is being used in a stand-alone fashion?