It's true it works!!!
It's great, as you say, that brings back the functionality of the faders in the buses. And once it's back, what we all discussed recently about implementing faders in plugins is now resolved. It's no longer necessary.
It's a shame that it doesn't work the other way around from "insert" > "input bus" to export mixes. Although I already have a trick for that: Sends to a bus dedicated to monitoring connected to the "speakers" input of the system and record the PipeWire monitor output.
As I explained to @fasteddy13, it gives a coherent explanation for someone who is just starting out or is taking up Qtractor again after a long time (there have been changes such as the functioning of AuxSends). And that coherence is based on: Each tool serves a purpose. That avoids disappointment and lack of understanding of what's happening.
If you can't think that you're doing something wrong, or that Qtractor simply isn't functional. And nothing could be further from the truth.
Although the ideal would be that all the connections could be made. I think that's how it should be. But as long as that is not the case...
I have the intuition that there must be a solution.
There must be a way to avoid the problem without having to rewrite everything from scratch.
It's true it works!!!
It's great, as you say, that brings back the functionality of the faders in the buses. And once it's back, what we all discussed recently about implementing faders in plugins is now resolved. It's no longer necessary.
It's a shame that it doesn't work the other way around from "insert" > "input bus" to export mixes. Although I already have a trick for that: Sends to a bus dedicated to monitoring connected to the "speakers" input of the system and record the PipeWire monitor output.
As I explained to @fasteddy13, it gives a coherent explanation for someone who is just starting out or is taking up Qtractor again after a long time (there have been changes such as the functioning of AuxSends). And that coherence is based on: Each tool serves a purpose. That avoids disappointment and lack of understanding of what's happening.
If you can't think that you're doing something wrong, or that Qtractor simply isn't functional. And nothing could be further from the truth.
Although the ideal would be that all the connections could be made. I think that's how it should be. But as long as that is not the case...
I have the intuition that there must be a solution.
There must be a way to avoid the problem without having to rewrite everything from scratch.