manual/include/muting-and-soloing.html

139 lines
5.0 KiB
HTML
Raw Normal View History

2013-01-29 19:26:36 -05:00
2014-02-18 17:12:27 -05:00
<p>
Each track and bus has two buttons which have important implications
for signal flow: <dfn>mute</dfn> and <dfn>solo</dfn>. The behaviour
of these buttons is configurable in Ardour, to suit different studio
2014-02-18 17:12:27 -05:00
set-ups.
</p>
2013-01-29 19:26:36 -05:00
<h2>Without a monitor bus</h2>
2014-02-18 17:12:27 -05:00
<p>
2018-03-28 08:19:23 -04:00
When using Ardour without a monitor bus, there is only one way
2014-02-18 17:12:27 -05:00
in which mute and solo will work:</p>
2013-01-29 19:26:36 -05:00
<ul>
2014-02-18 17:12:27 -05:00
<li>
Mute on a track or bus will mute that track on the master bus,
2018-03-28 08:19:23 -04:00
so that it will not be heard.
2014-02-18 17:12:27 -05:00
</li>
<li>
Solo on a track or bus will solo that track or bus and mute all
others. Soloing a bus will also solo any tracks or
2014-02-18 17:12:27 -05:00
busses which feed that bus.
</li>
2013-01-29 19:26:36 -05:00
</ul>
2014-02-18 17:12:27 -05:00
2013-01-29 19:26:36 -05:00
<h2>With a monitor bus</h2>
2014-02-18 17:12:27 -05:00
<p>
2018-03-28 08:19:23 -04:00
For setups with a monitor bus, more options are available, mostly
governed by the setting of the
<kbd class="option">Solo controls are Listen controls</kbd> option
2018-03-28 08:19:23 -04:00
in <kbd class="menu">Edit &gt; Preferences &gt; Mixer.</kbd>
2014-02-18 17:12:27 -05:00
</p>
<p>
With <kbd class="optoff">Solo controls are Listen controls</kbd>
unticked, behaviour is almost exactly the same as the situation
without a monitor bus. Mute and solo behave the same, and the monitor
2014-02-18 17:12:27 -05:00
bus is fed from the master bus, so it sees the same thing.
</p>
<p>
2018-03-28 08:19:23 -04:00
With <kbd class="option">Solo controls are Listen controls</kbd>
ticked, the master and monitor busses behave differently. In this
mode, solo controls are more properly called <dfn>listen</dfn>
controls, and Ardour's solo buttons will change their legend from
2018-03-28 08:19:23 -04:00
<kbd class="menu">S</kbd> to either <kbd class="menu">A</kbd> or <kbd class="menu">P</kbd> to
2014-02-18 17:12:27 -05:00
reflect this.
</p>
<p>
Now, without any mute or listen, the monitor bus remains fed by
2014-02-18 17:12:27 -05:00
the master bus. Also:
</p>
2013-01-29 19:26:36 -05:00
<ul>
2014-02-18 17:12:27 -05:00
<li>
Mute will mute the track or bus, so that it will not be heard
2014-02-18 17:12:27 -05:00
anywhere (neither on the master nor monitor busses), much as before.
</li>
<li>
Listen will disconnect the monitor bus from the master bus, so
that the monitor bus now only receives things that are "listened to".
Listen will not perform any muting, and hence the master bus will
2014-02-18 17:12:27 -05:00
not be affected by a listened track or bus.
</li>
2013-01-29 19:26:36 -05:00
</ul>
2014-02-18 17:12:27 -05:00
<p>
When solo controls are listen controls, the listening point can be set
to either After-Fade Listen (AFL) or Pre-Fade Listen (PFL). The precise
point to get the signal from can further be configured using the
<kbd class="menu">PFL signals come from</kbd> and
2014-02-18 17:12:27 -05:00
<kbd class="menu">AFL signals come from</kbd> options.
</p>
<p>
The solo-mute arrangement with a monitor bus is shown below:
</p>
2018-03-28 08:19:23 -04:00
<figure class="center">
<img src="/images/solo-mute.png" alt="mute/solo signal flow">
<figcaption>Mute/solo signal flow</figcaption>
</figure>
2017-02-13 14:38:01 -05:00
<p>
Here we have a number of tracks or busses (in orange). Each one has an
output which feeds the master bus. In addition, each has PFL and AFL
outputs; we have a choice of which to use. PFL/AFL from each track or
bus are mixed. Then, whenever anything is set to AFL/PFL, the monitor out
becomes just those AFL/PFL feeds; the rest of the time, the monitor out is
2014-02-18 17:12:27 -05:00
fed from the master bus.
</p>
<p>
In this scheme Solo has no effect other than to mute other non-soloed tracks;
2014-02-18 17:12:27 -05:00
with solo (rather then listen), the monitor out is fed from the master bus.
</p>
2013-01-29 19:26:36 -05:00
<h2>Other solo options</h2>
2014-02-18 17:12:27 -05:00
<p>
2018-03-28 08:19:23 -04:00
<kbd class="menu">Edit &gt; Preferences &gt; Mixer</kbd> has some
2014-02-18 17:12:27 -05:00
more solo options:
</p>
2013-01-29 19:26:36 -05:00
<h3>Solo-in-place mute cut</h3>
2014-02-18 17:12:27 -05:00
<p>
When using solo-in-place (SiP), in other words when soloed tracks are being
listened to on the master bus, this fader specifies the gain that will be
2014-02-18 17:12:27 -05:00
applied to other tracks in order to mute them. Setting this level to
2017-04-07 11:03:28 -04:00
-&infin;&nbsp;dB will mean that other tracks will not be heard at all; setting to
2014-02-18 17:12:27 -05:00
some higher value less than 0dB means that other non-soloed tracks will be h
eard, just reduced in volume compared to the soloed tracks. Using a value
2017-04-07 11:03:28 -04:00
larger than -&infin;&nbsp;dB is sometimes called "Solo-In-Front" by other DAWs, because
the listener has the sense that soloed material is "in front" of other
material. In Ardour, this is not a distinct mode, but instead the mute cut
2018-03-28 08:19:23 -04:00
control offers any level of "in-front-ness" that is desired.
2014-02-18 17:12:27 -05:00
</p>
2018-03-28 08:19:23 -04:00
2013-01-29 19:26:36 -05:00
<h3>Exclusive solo</h3>
2014-02-18 17:12:27 -05:00
<p>
If this is enabled, only one track or bus will ever be soloed at once; soloing
track B while track A is currently soloed will un-solo track A before soloing
2014-02-18 17:12:27 -05:00
track B.
</p>
2018-03-28 08:19:23 -04:00
2013-01-29 19:26:36 -05:00
<h3>Show solo muting</h3>
2014-02-18 17:12:27 -05:00
<p>
If this is enabled, the mute button of tracks and busses will be drawn
outlined to indicate that the track or bus is muted because something else
2018-03-28 08:19:23 -04:00
is soloed. This is enabled by default, and it is recommended to leave it
that way unless extremely comfortable with Ardour's mute/solo
2014-02-18 17:12:27 -05:00
behaviour.
</p>
2018-03-28 08:19:23 -04:00
2013-01-29 19:26:36 -05:00
<h3>Soloing overrides muting</h3>
2014-02-18 17:12:27 -05:00
<p>
If this is enabled, a track or bus that is both soloed and muted will behave
2014-02-18 17:12:27 -05:00
as if it is soloed.
</p>
2018-03-28 08:19:23 -04:00
<h3>Mute affects&hellip;</h3>
2014-02-18 17:12:27 -05:00
<p>
These options dictate whether muting the track will affect various routes out
of the track; through the sends, through the control outputs (to the monitor
2014-02-18 17:12:27 -05:00
bus) and to the main outputs.
</p>