1_
Exactly, fast and powerful. In 2 clicks and 2 seconds you get something much more functional than in 60 clicks and 60 seconds.
2_
Actually, if you want, the most appropriate thing would be to rename the "Default Master" to "Default Group" and create a master at the end (which is its most logical place).
This way you guarantee that if you create new tracks they will end up in the Default Group without having to configure anything.
Also, if you create more groups, the tracks without a group will rest in the Default Group.
Before this new flow, there would never have been a reason to have renamed the "Default Master" as "Ignore". Because it always made sense for there to be a "Default Group".
Reaching this conclusion is not intuitive, it has cost me a lot, and that was for me the real conceptual error. Calling Master something that really isn't. Master Default is not a Master, it is a Group that assumes Master functions to simplify the simplest workflows.
But of course, documentation would have been needed to explain what a Group is, what an Auxiliary Bus is and what a Master Bus is and how to take advantage of these concepts with Qtractor to create powerful workflows...
I'm working on it :), in less than a week the How to should be finished.
The current flow is much more flexible and allows you to improvise more without having to think too much :).
Hi, @windowsrefund :
1_
Exactly, fast and powerful. In 2 clicks and 2 seconds you get something much more functional than in 60 clicks and 60 seconds.
2_
Actually, if you want, the most appropriate thing would be to rename the "Default Master" to "Default Group" and create a master at the end (which is its most logical place).
This way you guarantee that if you create new tracks they will end up in the Default Group without having to configure anything.
Also, if you create more groups, the tracks without a group will rest in the Default Group.
Before this new flow, there would never have been a reason to have renamed the "Default Master" as "Ignore". Because it always made sense for there to be a "Default Group".
Reaching this conclusion is not intuitive, it has cost me a lot, and that was for me the real conceptual error. Calling Master something that really isn't. Master Default is not a Master, it is a Group that assumes Master functions to simplify the simplest workflows.
But of course, documentation would have been needed to explain what a Group is, what an Auxiliary Bus is and what a Master Bus is and how to take advantage of these concepts with Qtractor to create powerful workflows...
I'm working on it :), in less than a week the How to should be finished.
The current flow is much more flexible and allows you to improvise more without having to think too much :).