This shatters my entire understanding (that I thought I had) of Qtractor and buses. But since there is a new kid in town (Pipewire) I have to be aware that this behaviour is a feature of the combination of Qtractor and the audio server (jackd or Pipewire).
As a jack user "Track -> Bus -> Bus -> Master Bus" is as 'natural' for me as "Track -> Bus -> Master Bus".
Now I learned that this isn't a given fact for another combination, say Qtractor and Pipewire.
So if I end up some day with a system that forces me to use Pipewire for Firefox & Co. I hope there is a way to configure it to output to a running jackd as the main audio system (as it's possible with Pulseaudio and jack sink). I don't feel like using a bad emulation of jack as long as I can use the original.
This shatters my entire understanding (that I thought I had) of Qtractor and buses. But since there is a new kid in town (Pipewire) I have to be aware that this behaviour is a feature of the combination of Qtractor and the audio server (jackd or Pipewire).
As a jack user "Track -> Bus -> Bus -> Master Bus" is as 'natural' for me as "Track -> Bus -> Master Bus".
Now I learned that this isn't a given fact for another combination, say Qtractor and Pipewire.
So if I end up some day with a system that forces me to use Pipewire for Firefox & Co. I hope there is a way to configure it to output to a running jackd as the main audio system (as it's possible with Pulseaudio and jack sink). I don't feel like using a bad emulation of jack as long as I can use the original.
EDIT:
Maybe I am a bit too harsh since Pipewire's emulation breaks some stuff but tries to avoid additional latencies that I get when I connect a Qtractor bus' output with another bus's input. Using a modular setup, e.g. with non-mixer-xt without additional latencies as in https://sourceforge.net/p/qtractor/wiki/How%20To%20-%209%20Distributing%20Plugins%27%20Load%20to%20multiple%20CPU%20Cores/ might be cool.