This seems like an obvious race condition here since both Carla and Qtractor are persisting state.
Opening Qtractor first could never result in everything being routed since the instruments (along with their midi and audio ports) don't yet exist. They won't exist until the appropriate .carxp session file is loaded in Carla. As such, loading the project in Qtractor only results in the internal audio routing being established.
On the other side of the equation, loading the Carla session first wouldn't work either since all the ports maintained by Qtractor don't exist yet.
So basically, it's a chicken/egg scenario.
Can this "send initial controllers" thing be broken out in some way as to allow the end user to drive it as needed? Anything would suffice, a button, a pull down menu option, anything.
This seems like an obvious race condition here since both Carla and Qtractor are persisting state.
Opening Qtractor first could never result in everything being routed since the instruments (along with their midi and audio ports) don't yet exist. They won't exist until the appropriate .carxp session file is loaded in Carla. As such, loading the project in Qtractor only results in the internal audio routing being established.
On the other side of the equation, loading the Carla session first wouldn't work either since all the ports maintained by Qtractor don't exist yet.
So basically, it's a chicken/egg scenario.
Can this "send initial controllers" thing be broken out in some way as to allow the end user to drive it as needed? Anything would suffice, a button, a pull down menu option, anything.
All the best