Correct busses spelling
This commit is contained in:
parent
9fa6ec830d
commit
0fec8c5f7c
@ -81,7 +81,7 @@
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Remote IDs are assigned to tracks and buses in the order that they appear in
|
||||
Remote IDs are assigned to tracks and busses in the order that they appear in
|
||||
the mixer window from left to right, starting from #1; manual assignment of
|
||||
remote IDs is not possible. The master bus and monitor section can be
|
||||
accessed by name.
|
||||
|
@ -110,13 +110,13 @@ here</em>"/></kbd>
|
||||
deal with this is to think of strip_types items being worth a number and
|
||||
then adding all those numbers together for a value to send.
|
||||
Strip Types will determine what kind of strips will be included in
|
||||
bank. This would include: Audio, MIDI, buses, VCAs, Master, Monitor
|
||||
bank. This would include: Audio, MIDI, busses, VCAs, Master, Monitor
|
||||
and hidden or selected strips.
|
||||
</p>
|
||||
<p>
|
||||
Aside from setting the track types for the main mix assignments, using
|
||||
/set_surface/strip_types with more than one surface button will allow
|
||||
switching between modes for example: inputs only, buses only,
|
||||
switching between modes for example: inputs only, busses only,
|
||||
selected only, hidden only, by having the buttons send values of: 3,
|
||||
12, 256, 512. A full mix button might have a value 31.
|
||||
</p>
|
||||
|
@ -28,10 +28,10 @@
|
||||
2 - MidiTracks.
|
||||
</li>
|
||||
<li>
|
||||
4 - AudioBuses.
|
||||
4 - AudioBusses.
|
||||
</li>
|
||||
<li>
|
||||
8 - MidiBuses.
|
||||
8 - MidiBusses.
|
||||
</li>
|
||||
<li>
|
||||
16 - VCAs.
|
||||
@ -60,7 +60,7 @@
|
||||
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
|
||||
@ -72,17 +72,17 @@
|
||||
<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>
|
||||
|
@ -18,7 +18,7 @@
|
||||
<li>
|
||||
Connect the output of that bus to one of the audio
|
||||
interface's playback ports that is not otherwise used. OSC
|
||||
will now include this bus in it's list of aux buses as it
|
||||
will now include this bus in it's list of aux busses as it
|
||||
no longer has it's output connected to the Master bus.
|
||||
</li>
|
||||
<li>
|
||||
@ -55,7 +55,7 @@
|
||||
<h4>Commands</h4>
|
||||
<dl class="bindings">
|
||||
<dt><kbd class="osc">/cue/connect</kbd></dt>
|
||||
<dd>Returns a list of aux buses.</dd>
|
||||
<dd>Returns a list of aux busses.</dd>
|
||||
<dt><kbd class="osc">/cue/aux <em>aux-number</em></kbd></dt>
|
||||
<dd>where <em>aux-number</em> is an integer which is the aux bus
|
||||
number this surface will use.</dd>
|
||||
@ -64,7 +64,7 @@
|
||||
<dt><kbd class="osc">/cue/previous_aux</kbd></dt>
|
||||
<dd>Sets the aux to one bus lower.</dd>
|
||||
<dt><kbd class="osc">/cue/connect</kbd></dt>
|
||||
<dd>Returns a list of aux buses.</dd>
|
||||
<dd>Returns a list of aux busses.</dd>
|
||||
<dt><kbd class="osc">/cue/fader <em>position</em></kbd></dt>
|
||||
<dd>where <em>position</em> is a float for the position of the fader
|
||||
between 0.0 and 1.0.</dd>
|
||||
|
@ -103,7 +103,7 @@
|
||||
and hidden strips. If it is desired to only see input tracks the
|
||||
others can be deselected. It is also possible to change these settings
|
||||
from the control surface. A set of buttons could select showing only
|
||||
inputs or only buses. If a group is selected in the GUI then showing
|
||||
inputs or only busses. If a group is selected in the GUI then showing
|
||||
only selected strips will show only that group. Showing hidden tracks
|
||||
is handy for cases where a groups of tracks that grouped to a bus or
|
||||
controlled by a VCA are hidden, but one of those tracks needs a tweak.
|
||||
|
@ -93,7 +93,7 @@
|
||||
kick, snare and overhead tracks, it may be helpful to connect the output of
|
||||
each to a bus called "drums", so that the drum kit's level can be set as a
|
||||
unit, and processing (such as equalization or compression) can be applied to
|
||||
the mix of all the tracks. Such buses are also called <dfn>groups</dfn>.
|
||||
the mix of all the tracks. Such busses are also called <dfn>groups</dfn>.
|
||||
</p>
|
||||
|
||||
<h2>Regions</h2>
|
||||
|
Loading…
Reference in New Issue
Block a user