2 - MidiTracks.
</li>
<li>
- 4 - AudioBuses.
+ 4 - AudioBusses.
</li>
<li>
- 8 - MidiBuses.
+ 8 - MidiBusses.
</li>
<li>
16 - VCAs.
to show inline with other strips.
</p>
<p>
- Some handy numbers to use might be: 15 (all tracks and buses), 31
+ Some handy numbers to use might be: 15 (all tracks and busses), 31
(add VCAs to that). Master or Monitor strips are generally not useful
on a surface that has dedicated controls for these strips as there are
/master* and /monitor* commands already. However, on a surface with
<p class-"note">
Audio Aux? say what? I am sure most people will have noticed that they
can find no <em>Aux</em> strips in the Ardour mixer. There are none.
- There are buses that can be used a number of ways. From analog days,
+ There are busses that can be used a number of ways. From analog days,
in OSC, a bus is something that gets used as a sub mix before ending up
going to Master. An auxiliary bus is used like a separate mixer and
it's output goes outside the program or computer to be used as:
a monitor mix, a back up recording, or what have you. In OSC where
controller strips may be limited, it may be useful not to use up a
strip for an aux that is not really a part of the mix. It is also
- useful to get a list of only aux buses if the control surface is a
+ useful to get a list of only aux busses if the control surface is a
phone used to provide talent monitor mix control on stage. Each
performer would be able to mix their own monitor. The user is free
- to enable both buses and auxes if they would prefer.
+ to enable both busses and auxes if they would prefer.
</p>
<h3>feedback</h3>