3 Each track and bus has two buttons which have important implications
4 for signal flow: <dfn>mute</dfn> and <dfn>solo</dfn>. The behaviour
5 of these buttons is configurable in Ardour, to suit different studio
9 <h2>Without a monitor bus</h2>
11 If you are using Ardour without a monitor bus, there is only one way
12 in which mute and solo will work:</p>
15 Mute on a track or bus will mute that track on the master bus,
16 so that it will not be heard.
19 Solo on a track or bus will solo that track or bus and mute all
20 others. Soloing a bus will also solo any tracks or
21 busses which feed that bus.
25 <h2>With a monitor bus</h2>
27 For setups with a monitor bus, you have more options, mostly
28 governed by the setting of the
29 <kbd class="option">Solo controls are Listen controls</kbd> option
30 in <kbd class="menu">Edit > Preferences > Solo / mute.
33 With <kbd class="optoff">Solo controls are Listen controls</kbd>
34 unticked, behaviour is almost exactly the same as the situation
35 without a monitor bus. Mute and solo behave the same, and the monitor
36 bus is fed from the master bus, so it sees the same thing.
39 With <kbc class="option">Solo controls are Listen controls</kbd>
40 ticked, the master and monitor busses behave differently. In this
41 mode, solo controls are more properly called <dfn>listen</dfn>
42 controls, and Ardour's solo buttons will change their legend from
43 <samp>S</samp> to either <samp>A</samp> or <samp>P</samp> to
47 Now, without any mute or listen, the monitor bus remains fed by
52 Mute will mute the track or bus, so that it will not be heard
53 anywhere (neither on the master nor monitor busses), much as before.
56 Listen will disconnect the monitor bus from the master bus, so
57 that the monitor bus now only receives things that are "listened to".
58 Listen will not perform any muting, and hence the master bus will
59 not be affected by a listened track or bus.
63 When solo controls are listen controls, the listening point can be set
64 to either After-Fade Listen (AFL) or Pre-Fade Listen (PFL). The precise
65 point to get the signal from can further be configured using the
66 <kbd class="menu">PFL signals come from</kbd> and
67 <kbd class="menu">AFL signals come from</kbd> options.
70 The solo-mute arrangement with a monitor bus is shown below:
72 <img src="/images/solo-mute.png" alt="mute/solo signal flow" />
74 Here we have a number of tracks or busses (in orange). Each one has an
75 output which feeds the master bus. In addition, each has PFL and AFL
76 outputs; we have a choice of which to use. PFL/AFL from each track or
77 bus are mixed. Then, whenever anything is set to AFL/PFL, the monitor out
78 becomes just those AFL/PFL feeds; the rest of the time, the monitor out is
79 fed from the master bus.
82 In this scheme Solo has no effect other than to mute other non-soloed tracks;
83 with solo (rather then listen), the monitor out is fed from the master bus.
86 <h2>Other solo options</h2>
88 <kbd class="menu">Edit > Preferences > Solo / Mute</kbd> has some
92 <h3>Solo-in-place mute cut</h3>
94 When using solo-in-place (SiP), in other words when soloed tracks are being
95 listened to on the master bus, this fader specifies the gain that will be
96 applied to other tracks in order to mute them. Setting this level to
97 -∞ dB will mean that other tracks will not be heard at all; setting to
98 some higher value less than 0dB means that other non-soloed tracks will be h
99 eard, just reduced in volume compared to the soloed tracks. Using a value
100 larger than -∞ dB is sometimes called "Solo-In-Front" by other DAWs, because
101 the listener has the sense that soloed material is "in front" of other
102 material. In Ardour, this is not a distinct mode, but instead the mute cut
103 control offers any level of "in-front-ness" that you might want to use.
105 <h3>Exclusive solo</h3>
107 If this is enabled, only one track or bus will ever be soloed at once; soloing
108 track B while track A is currently soloed will un-solo track A before soloing
111 <h3>Show solo muting</h3>
113 If this is enabled, the mute button of tracks and busses will be drawn
114 outlined to indicate that the track or bus is muted because something else
115 is soloed. This is enabled by default, and we recommend that you leave it
116 that way unless you are extremely comfortable with Ardour's mute/solo
119 <h3>Soloing overrides muting</h3>
121 If this is enabled, a track or bus that is both soloed and muted will behave
124 <h3>Mute affects…</h3>
126 These options dictate whether muting the track will affect various routes out
127 of the track; through the sends, through the control outputs (to the monitor
128 bus) and to the main outputs.