Add new comment

https://sourceforge.net/p/qtractor/wiki/How%20To%20-%2010%20Get%20%22SOL...
Explaining the limitation of Qtractor of not being able to move the original Master, and that the sends only work upwards, I think goes beyond the purpose of the tutorial. There would be too much to explain and the focus would be lost. But thank you, because you have made me realize that a scenario to monitor buses in ONLY, does not imply an intermediate difficulty, but an advanced one. I will change the level of difficulty.

Related to what you mention.

It is true that it is a bit annoying not to be able to delete, change location or change the type (from duplex to output or input) in the default master.

The only thing we can do is rename it.
(In my case I use it as a stereo input and output bus for instruments. Whether they are recorded externally or internally with plugins, they end up on the Output InstrumentStereo bus. This allows me to treat them together before mixing them with the voices.)

I understand that it must be for architectural reasons. Qtractor must always have an audio input and output.

Two possible solutions come to mind.

Complex solution:
- If it is deleted: it disappears from the user interface. In the connections it appears with the name (disabled) both in its input and in its output. The tracks that had it assigned also appear associated with (disabled). Internally, in the programming part, you would simply assign a gain/volume of 0 to that Bus.

To summarize, if you delete it, hide it from the interface, assign it a name (disabled) and apply a gain of 0.

- If it becomes Output type, everything indicated above applies to the input bus and vice versa.

- If you move it, it acts as deleted and a new one is automatically created to take its place.

Simple solution:
Always delete it. This way, we would also have a Bus (Disabled). Sometimes it is useful.
(I have had to create an Output. This allows parallel sending to several buses and better mixing wet and dry signals.)

The drawback I see with this solutions is that it can be a bit jarring to have an output and input disabled in the connections.
Another major drawback with "simple solution" is that it would no longer be compatible with previous versions of sessions.

Conclusion:
I have already gotten used to this limitation. :)