However, it fixes the strange behavior I started the thread with.
In the regular version of Qtractor:
1- You can directly interconnect inserts as long as you do it in the correct order.
2- You can directly connect bus outputs to insert inputs.
In this version:
These direct connection exceptions no longer apply.
It now only works in strictly recommended mode.
No direct interconnection will work unless you use an intermediary.
If you use this rule, there are no issues:
1- Buses should only be connected to hardware inputs and outputs.
2- Inserts should only be connected to external applications from Qtractor.
3- Auxiliary sends are used for internal Qtractor interconnections.
But this rule leaves out cases, for example, recording a bus output on a new track. Interconnecting tracks.
It's a good rule to create a reliable environment for people new to Qtractor who encounter this problem. But I think the logical thing would be for the problem not to exist and to be able to organize the flow freely.
I consider this a step backward.
The good thing is that we've verified that how this is organized directly influences the "zero copy" issue, and suggests that a solution may exist.
Much worse now regarding the Zero Copy issue.
However, it fixes the strange behavior I started the thread with.
In the regular version of Qtractor:
1- You can directly interconnect inserts as long as you do it in the correct order.
2- You can directly connect bus outputs to insert inputs.
In this version:
These direct connection exceptions no longer apply.
It now only works in strictly recommended mode.
No direct interconnection will work unless you use an intermediary.
If you use this rule, there are no issues:
1- Buses should only be connected to hardware inputs and outputs.
2- Inserts should only be connected to external applications from Qtractor.
3- Auxiliary sends are used for internal Qtractor interconnections.
But this rule leaves out cases, for example, recording a bus output on a new track. Interconnecting tracks.
It's a good rule to create a reliable environment for people new to Qtractor who encounter this problem. But I think the logical thing would be for the problem not to exist and to be able to organize the flow freely.
I consider this a step backward.
The good thing is that we've verified that how this is organized directly influences the "zero copy" issue, and suggests that a solution may exist.