Main menu
You are here
How To - 11 Manage audio workflows with "Group Buses", "Auxiliary Buses" and "Master Buses"
26 September, 2024 - 17:01 — G3N-es
New How To.
Tell me if I understand it well, if you would make any changes, or if you disagree with anything.
https://sourceforge.net/p/qtractor/wiki/How%20To%20-%2011%20Manage%20aud...
Forums:
Thanks for this. I just read
Thanks for this. I just read it through once but have no comments yet as I found myself getting a little confused at times. Perhaps it's just me because I tend to drive things from primarily a MIDI perspective and use the buses to basically push the noise around and mix. In fact, I really never even deal with the inputs at all. I'm going to read it again tonight to see what I can get from it. One thing maybe worth noting is it can be quite difficult to read the names of the Aux Sends in those images due to the inability to "zoom" in the image. I don't know if the information is actually relevant to the topic you're discussing though.
Actually.... so I'm thinking the whole distinction between "Group Bus" and "Aux Bus" feels a little forced. I mean, a bus is a bus is a bus, right? The only difference really comes down to what signal is being fed to it and where the bus ends up sending the signal. For example, I don't think we should be assuming an Aux Bus is going to output into Master. I think you realized that along the way and then suggested an Aux Mix. See my point? I'm just worried we may be making assumptions about the end user's workflow? I may be overthinking though. Thanks again for focusing on this!
I was just thinking more about this and I think I can offer the following recommendation. Rather than jumping so quickly into what I'd describe as "Common Use-Cases of Buses" (which I think you're doing a great job of), it would be helpful to start off with breaking down the various means in which a bus can receive and output signal. For example, we know any bus can have signal sent to it via a track's
Audioselection, aAux Send, or even aInsert (Audio). Each of these means different things which may be worth discussing accordingly. On the output side, signal can be routed using anAux Send, or having its outputs sent to the previously mentionedInsert (Audio). Each of those may be worth discussing. Then once all the inputs and outputs are covered...... the "typical use cases" content would make for a great elaboration.re. Thanks for this. I just read
The first thing I want to point out is that I'm asking because I'm not sure whether to publish it or not.
On the one hand, I think it can be very helpful.
On the other hand, a big part of Qtractor's charm (and I think philosophy) is precisely that it doesn't predefine the tools.
It gives you fully functional modules for you to define as you please.
This simplifies things a lot and allows everyone to interpret and create their own solutions and workflows.
By defining what a group is and what an auxiliary bus is, I'm breaking that charm, and maybe I'm going against Qtractor's philosophy.
I'm predefining a way to create groups and auxiliary buses.
However, @windowsrefund you asked for the group functionality, because it's not intuitive to understand that by default, qtractor buses work as groups.
https://www.rncbc.org/drupal/node/2524
On the other hand, the tutorial gives an answer to why it is necessary and makes sense for the first bus to exist, and why it is logical that it is duplex and cannot be moved or deleted. Because it is the generic default bus, which hosts everything that does not have a specific group.
Don't worry about telling me that you don't see it appropriate because I myself have doubts.
"Actually.... so I'm thinking the whole distinction between "Group Bus" and "Aux Bus" feels a little forced"
I'm inclined to remove it. If after the second reading it still seems that way I will remove it without problems :).
I have decided to remove it for the reasons stated above
I have decided to remove it for the reasons stated above.
Thanks for reading and commenting.
re. decided to remove it...
even though,
for whatever reasons lead you to remove it, which might well be perfectly valid, nevertheless, you could just keep it in the flow of thought and make a note or statement as one's view, concept or idea regarding the subject at hand.
was it totally wrong? no? then, why? :)
cheers
Hey big thanks for that! It
Hey big thanks for that! It works like a charm. Mind me asking why you left a
Aux Sendon the track pointing toMaster? I'm guessing it was just left behind while testing?I like your little groove too. Very nice!
Add new comment