2017-01-17 12:33:34 -05:00
|
|
|
|
2019-01-24 06:00:52 -05:00
|
|
|
<figure class="right">
|
|
|
|
<img src="/images/mixer-1-strip-numbered.png" alt="A mixer strip">
|
|
|
|
<figcaption>
|
|
|
|
A mixer strip
|
|
|
|
</figcaption>
|
|
|
|
</figure>
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
A <dfn>mixer strip</dfn> in Ardour is a vertical view of the track, from a
|
|
|
|
mixing point of view. This view is convenient to deal with I/O, effects,
|
|
|
|
panning/muting, gain, etc… It has a general "top to bottom" flow.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-02-13 22:47:33 -05:00
|
|
|
The mixer strips breaks down into:
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<ol>
|
|
|
|
<li>Header</li>
|
|
|
|
<li>Track name</li>
|
|
|
|
<li>Input(s)</li>
|
|
|
|
<li>Polarity <em>only for audio tracks</em></li>
|
|
|
|
<li>Processor box</li>
|
|
|
|
<li>Panner</li>
|
|
|
|
<li>Recording options</li>
|
|
|
|
<li>Mute/Solo</li>
|
|
|
|
<li>Gain & Meter</li>
|
|
|
|
<li>Control master</li>
|
|
|
|
<li>Fader automation/mix group/metering point</li>
|
|
|
|
<li>Output(s)</li>
|
|
|
|
<li>Comments</li>
|
|
|
|
</ol>
|
|
|
|
|
|
|
|
<h2>Headers</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
At the top of the window, is the <a href="@@the-track-and-bus-group-list">group
|
|
|
|
tabs</a> (here, <em>recm…</em>). This allows to group tracks together for
|
|
|
|
common controls.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-02-13 22:47:33 -05:00
|
|
|
Bellow are 3 buttons:
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<ul>
|
|
|
|
<li>
|
2017-03-13 06:23:50 -04:00
|
|
|
The double arrow button allows to shrink/expand the width of the strip. <kbd
|
|
|
|
class="mod1n"></kbd><kbd class="mod3n"></kbd><kbd class="mouse">Click</kbd> the
|
|
|
|
button will shrink/expand all the tracks at once
|
2017-01-17 12:33:34 -05:00
|
|
|
</li>
|
|
|
|
<li>
|
|
|
|
The color bar shows the color of the track in the editor
|
|
|
|
</li>
|
|
|
|
<li>
|
2017-03-13 06:23:50 -04:00
|
|
|
The <kbd class="menu">X</kbd> button toggles the visibility of the track OFF. To
|
|
|
|
turn it back ON, one can either go to the <a
|
|
|
|
href="@@the-tracks-and-busses-list">Tracks and Busses list</a> in the Editor
|
|
|
|
view and check the "V" column on the track's line or stay in the Mixer view and
|
|
|
|
check the <kbd class="menu">Show</kbd> column of this strip in the <a
|
|
|
|
href="@@strips-list">Strips list</a>.
|
2017-01-17 12:33:34 -05:00
|
|
|
</li>
|
|
|
|
</ul>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
<kbd class="mouse">Right</kbd> clicking on the color bar will bring up a context
|
|
|
|
menu, which is exactly the same as clicking on the Track name button.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Track Name</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-02-13 22:47:33 -05:00
|
|
|
Clicking the Track name button will bring up a menu:
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-03-14 12:43:24 -04:00
|
|
|
<table class="dl">
|
|
|
|
<tr><th>Color…</th><td>Changes the strip/track color</td></tr>
|
|
|
|
<tr><th>Comments…</th><td>Shows an editor to put comments about the track,
|
|
|
|
see below the Comments button</td></tr>
|
|
|
|
<tr><th>Inputs…</th><td>Shows the Routing grid for the inputs of the track</td></tr>
|
|
|
|
<tr><th>Outputs…</th><td>Shows the Routing grid for the outputs of the track</td></tr>
|
|
|
|
<tr><th>Save As Template…</th><td>Allows to save the track without its media
|
|
|
|
content (I/O, effects,…) for later reuse</td></tr>
|
|
|
|
<tr><th>Rename…</th><td>Changes the name of the track (effective both in the
|
|
|
|
Mixer and the Editor)</td></tr>
|
|
|
|
<tr><th><kbd class="option">Active</kbd></th><td>Select the active status of the track.
|
|
|
|
An inactive track won't output any sound</td></tr>
|
|
|
|
<tr><th><kbd class="option">Strict I/O</kbd></th><td>While in <a href="@@trackbus-signal-flow">
|
2017-03-13 06:23:50 -04:00
|
|
|
patchbayStrict I/O</a> mode, a track <em>always</em> has as many output as it
|
|
|
|
has inputs, regardless of the effects. When disabled, a stereo effect put on
|
2017-03-14 12:43:24 -04:00
|
|
|
a mono track will result in a stereo output for the strip.</td></tr>
|
|
|
|
<tr><th>Pin Connections…</th><td>Shows the <kbd class="menu">Pin Configuration</kbd>
|
|
|
|
window, that shows (and allows to modify) all the signal flows inside the track</td></tr>
|
|
|
|
<tr><th>Adjust Latency…</th><td>Shows the <kbd class="menu">Track Latency</kbd>
|
|
|
|
dialog, that allows fine-tune the latency to the track, in samples, msec or period</td></tr>
|
|
|
|
<tr><th><kbd class="option">Protect Against Denormals</kbd></th><td>Uses a trick to
|
2017-03-13 06:23:50 -04:00
|
|
|
get rid of <em>denormals</em>, which are very small numbers the CPU can have
|
|
|
|
a hard time dealing with. To be used if the CPU consumption for plugins is
|
2017-03-14 12:43:24 -04:00
|
|
|
noticeably higher than expected</td></tr>
|
2017-02-14 10:20:06 -05:00
|
|
|
<tr><th>Duplicate…</th><td>Copies the track to a new one, optionally with
|
2017-03-14 12:43:24 -04:00
|
|
|
its playlist</td></tr>
|
|
|
|
<tr><th>Remove</th><td>Deletes the track and its playlist</td></tr>
|
|
|
|
</table>
|
2017-01-17 12:33:34 -05:00
|
|
|
|
|
|
|
<h2>Inputs</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
The dropdown button shows the current input port(s), i.e. what's plugged to the
|
|
|
|
"in" of the track. By default, each audio track is connected to the system
|
|
|
|
inputs, ready for recording, as shown by the number(s). Clicking the dropdown
|
|
|
|
Inputs button will allow to change the inputs, through a menu:
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-03-14 12:43:24 -04:00
|
|
|
<table class="dl">
|
|
|
|
<tr><th>Disconnect</th><td>Disconnects everything, i.e. the track has no input</td></tr>
|
|
|
|
<tr><th>In <em>n</em></th><td>Those are the system inputs, e.g. to record from the
|
2017-03-13 06:23:50 -04:00
|
|
|
soundcard. A mono track will have <em>In 1</em> and <em>In 2</em> separated,
|
2017-03-14 12:43:24 -04:00
|
|
|
while a stereo track can have <em>In 1+2</em></td></tr>
|
|
|
|
<tr><th><em>Track n output</em></th><td>All the outputs of compatible tracks, e.g.,
|
2017-03-13 06:23:50 -04:00
|
|
|
a mono track can only receive a mono signal, a MIDI track can only receive MIDI
|
2017-03-14 12:43:24 -04:00
|
|
|
signal, …</td></tr>
|
|
|
|
<tr><th>Add Audio Port</th><td>Adds an audio input to the track, i.e. a mono audio
|
2017-02-14 10:20:06 -05:00
|
|
|
track becomes a stereo one</td></tr>
|
2017-03-14 12:43:24 -04:00
|
|
|
<tr><th>Add MIDI Port</th><td>Adds a MIDI input to the track. Adding it to an audio
|
2017-02-14 10:20:06 -05:00
|
|
|
track makes it a mixed Audio/MIDI track. This can be useful e.g. to feed some
|
2017-03-14 12:43:24 -04:00
|
|
|
plugins with a MIDI signal to control the audio, like a vocoder</td></tr>
|
|
|
|
<tr><th>Routing Grid</th><td>Shows the <a href="@@patchbay"><kbd class="menu">Routing
|
|
|
|
Grid</kbd> window</a>, which allows for more complex input configuration</td></tr>
|
|
|
|
</table>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
The <kbd class="menu">Routing Grid</kbd> can also be shown by right clicking the
|
|
|
|
dropdown Inputs button. It allows to make the connections through a matrix, and
|
|
|
|
connect things that are not listed in the menu above, or connect to multiple
|
|
|
|
sources at once, reduce the number of inputs, etc…
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
On audio tracks, is a Trim knob, as on traditional consoles. It set the base
|
|
|
|
input level for the track, avoiding any clipping. Notice that it trims both any
|
|
|
|
input, but (when playing back), also the level of the playlist as displayed in
|
|
|
|
the Editor. It makes sense as while playing, the input of the track is the
|
|
|
|
playlist, on which the mixer strip acts.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
On midi tracks, it is replaced by a MIDI Input button, that allows/disallows
|
|
|
|
MIDI input on the track.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Polarity</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
On audio tracks only, the Polarity button(s), 1 per input, allow to reverse
|
|
|
|
the signal, i.e. a negative value will be positive and vice-versa. This can help
|
|
|
|
deal with phasing issues.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Processor box</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
The processor box is where the effects are added. By default, one effect is
|
|
|
|
always present: the Fader (see below). The effects can be added
|
|
|
|
<em>pre</em>-fader and appear in brown, or <em>post</em>-fader, where they will
|
|
|
|
appear in dark green. The signal flow is represented by lines, red for the MIDI
|
|
|
|
and green for the audio.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-02-14 10:20:06 -05:00
|
|
|
It is also where the <a href="@@aux-sends">Sends</a> come from, whether
|
2017-03-13 06:23:50 -04:00
|
|
|
external or auxiliary.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
To learn more about the processor box, see <a href="@@processor-box">The
|
|
|
|
Processor Box</a>.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Panner</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
The <dfn>Panner</dfn> visually displays how the sound will be distributed
|
|
|
|
between the different outputs. They'll look and behave differently if the
|
|
|
|
track is mono, stereo, or has multiple channels.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
|
|
|
Right clicking the Panner will show a menu:
|
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-03-14 12:43:24 -04:00
|
|
|
<table class="dl">
|
|
|
|
<tr><th><kbd class="option">Bypass</kbd></th><td>When checked, the panner is grayed,
|
|
|
|
and the signal is not affected by it</td></tr>
|
|
|
|
<tr><th>Reset</th><td>Resets the panner to its default settings, e.g. for a mono
|
|
|
|
signal, it is centered</td></tr>
|
|
|
|
<tr><th>Edit…</th><td>Shows a <kbd class="menu">Panner</kbd> dialog, which
|
|
|
|
allows for fine tuning of the panner</td></tr>
|
|
|
|
</table>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
See <a href="@@panning">Panning</a> to learn more about how to control the panner,
|
|
|
|
and what kind of panners are available inside Ardour.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Recording options</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
The most noticeable button here is the Record Enable one, with a red circle.
|
|
|
|
When enabled, next time the Global record will be armed and playback started,
|
|
|
|
everything that comes from the input of the track will be recorded. Right clicking
|
|
|
|
a disabled record button allows to enable <kbd class="menu">Rec-Safe</kbd>,
|
|
|
|
thus protecting the track against accidental recording.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
The buttons on the right, <kbd class="menu">In</kbd> and <kbd
|
|
|
|
class="menu">Disk</kbd>, show what the user is listening to by lighting up,
|
|
|
|
between the <em>In</em>put and the actual content of the playlist on
|
|
|
|
<em>Disk</em>.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
They also allow to override the automatic switching by pressing them to lock
|
|
|
|
one source or the other to be what the user is hearing.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Mute/Solo</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
These buttons allow to Mute (or silence) the track, or Solo them, shutting
|
|
|
|
down the gain of the other tracks (totally by default, can be set to partially
|
|
|
|
in the options). See <a href="@@muting-and-soloing">Muting and Soloing</a> for
|
|
|
|
more information.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
Notice that by default, Solo overrides Mute, i.e. if a track is both Soloed and
|
|
|
|
Muted, it will play. That can be changed in the preferences.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-02-13 22:47:33 -05:00
|
|
|
The two led button above are related to solo:
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<ul>
|
2017-03-13 06:23:50 -04:00
|
|
|
<li>Solo Isolate, as the name suggests, isolates tracks or busses from the solo
|
|
|
|
system. When tracks or busses are soloed the isolated ones will not mute.</li>
|
2017-02-14 10:20:06 -05:00
|
|
|
<li>Solo Lock locks the solo into its current state (i.e. solo on or solo off).
|
2017-03-13 06:23:50 -04:00
|
|
|
It will not allow the solo state to be changed until the lock is released.</li>
|
2017-01-17 12:33:34 -05:00
|
|
|
</ul>
|
|
|
|
|
|
|
|
<h2>Gain & Meter</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
On the right of this part is a <a href="@@metering-in-ardour">Meter</a>,
|
|
|
|
displaying the level of the track's output after the fader. In can be set to
|
|
|
|
display the signal at any point, see below <em>Metering Point</em>. Right
|
|
|
|
clicking this meter shows a menu allowing to switch the meter type.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
The big Gain slider on the left allows to change the gain of the track. Its
|
|
|
|
default OdB value is reminded with a white horizontal line, and its precise
|
|
|
|
value is shown in a text field above it, that doubles as a way to type in a
|
|
|
|
numeric value.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2018-06-17 11:18:27 -04:00
|
|
|
The text field above the meter shows the "Peak", i.e. the maximum value that has
|
2017-03-13 06:23:50 -04:00
|
|
|
been reached during playback. To avoid distortion, the value should stay below OdB,
|
|
|
|
and if it goes above this value, the text field will turn red. Clicking on
|
|
|
|
this field will reset the Peak value (for a new measurement or a new part of the
|
|
|
|
track).
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<p class="note">
|
2017-03-13 06:23:50 -04:00
|
|
|
Notice that if any gain automation has been set and the
|
|
|
|
automation state is set on "Play" (see below), then the Gain fader is driven by
|
2018-11-10 06:05:33 -05:00
|
|
|
the automation, and not by the user. The Gain fader will turn grey to show it is
|
2017-03-13 06:23:50 -04:00
|
|
|
inactive.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
2017-03-13 06:23:50 -04:00
|
|
|
<h2>VCAs</h2>
|
2017-01-17 12:33:34 -05:00
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
If at least one <a href="@@control-masters-mixer-strips">VCA</a> exists, this
|
|
|
|
button will show up, allowing the user to link this track to any control master.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
Clicking the button lists all the available control masters, and a menu option
|
2018-06-17 11:25:18 -04:00
|
|
|
to <kbd class="menu">Unassign all</kbd>. Notice that a track can be a slave
|
2017-03-13 06:23:50 -04:00
|
|
|
to as many VCAs as they are in the session, hence multiplying the number
|
|
|
|
of VCA buttons. The displayed number is the number of the VCA,
|
|
|
|
not the count of VCAs linked to the track. A track with no VCA assigned
|
|
|
|
will show a unique button with a "<kbd class="menu">-vca-</kbd>" label instead
|
|
|
|
of this number.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Fader automation/mix group/metering point</h2>
|
|
|
|
|
|
|
|
<h3>Fader automation mode</h3>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-02-13 22:47:33 -05:00
|
|
|
This button allows to choose the mode used regarding automation:
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-03-14 12:43:24 -04:00
|
|
|
<table class="dl">
|
|
|
|
<tr><th>Manual</th><td><em>(default)</em> The playback won't use the fader automation
|
|
|
|
data</td></tr>
|
|
|
|
<tr><th>Play</th><td>Enables playback/use of fader automation data</td></tr>
|
|
|
|
<tr><th>Write</th><td>While the transport is rolling, all fader changes will be
|
|
|
|
recorded to the fader automation lane</td></tr>
|
|
|
|
<tr><th>Touch</th><td>While the transport is rolling, touching the fader will initiate
|
2017-03-13 06:23:50 -04:00
|
|
|
recording all fader changes until the fader is released. When the fader is not
|
|
|
|
being touched, existing automation data will be played/used to control the gain
|
2017-03-14 12:43:24 -04:00
|
|
|
level.</td></tr>
|
|
|
|
</table>
|
2017-01-17 12:33:34 -05:00
|
|
|
|
|
|
|
<h3>Mix group</h3>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
This button displays the mix group information as does the tab in the header
|
|
|
|
(see above). It is convenient though, as it allows to quickly switch the track
|
|
|
|
from one group to another with a drop down menu, also allowing to affect the
|
2017-02-14 10:20:06 -05:00
|
|
|
track to a non-adjacent group (which the tab won't easily allow).
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<h3>Metering Point</h3>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-01-17 12:33:34 -05:00
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
The metering displayed in the meter is by default is 'Post', i.e. Post fader.
|
|
|
|
It can be changed with this button to Any point of the signal flow:
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-02-13 22:47:33 -05:00
|
|
|
|
2017-03-14 12:43:24 -04:00
|
|
|
<table class="dl">
|
|
|
|
<tr><th>In</th><td>The input of the track</td></tr>
|
|
|
|
<tr><th>Pre</th><td>Pre-fader</td></tr>
|
|
|
|
<tr><th>Post</th><td>Post-fader</td></tr>
|
|
|
|
<tr><th>Out</th><td>The output of the track</td></tr>
|
|
|
|
<tr><th>Custom</th><td>A <em>Meter</em> processor is added to the processor box and
|
2017-03-13 06:23:50 -04:00
|
|
|
can be set anywhere (by dragging and dropping) to probe the signal flow at
|
2017-03-14 12:43:24 -04:00
|
|
|
that point</td></tr>
|
|
|
|
</table>
|
2017-01-17 12:33:34 -05:00
|
|
|
|
|
|
|
<h2>Output(s)</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
This button is exactly the same as the <em>Input</em> button, but applies to
|
|
|
|
the <em>output</em> of the track.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Comments</h2>
|
|
|
|
|
|
|
|
<p>
|
2017-03-13 06:23:50 -04:00
|
|
|
This buttons open up a little text editor, that can be used to add some
|
|
|
|
written notes to the track, as e.g. a particular setting. The button's caption
|
|
|
|
is replaced by the beginning of the text, so it can be used as a "sub" name for
|
|
|
|
the track.
|
2017-01-17 12:33:34 -05:00
|
|
|
</p>
|
2017-03-14 23:57:34 -04:00
|
|
|
|