X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmuting-and-soloing.html;h=fc93dddf44b9effdca8df1620e965063d802728d;hb=8e3323a3235528bfaaf945aa0a2a9f9187e0c81e;hp=5b685379993b018650a38f8b7216ba16a6a32fbe;hpb=081e7af0b6f6dec0ca685d3a538eacf20394c2cc;p=ardour-manual diff --git a/include/muting-and-soloing.html b/include/muting-and-soloing.html index 5b68537..fc93ddd 100644 --- a/include/muting-and-soloing.html +++ b/include/muting-and-soloing.html @@ -8,12 +8,12 @@
- If you are using Ardour without a monitor bus, there is only one way + When using Ardour without a monitor bus, there is only one way in which mute and solo will work:
- For setups with a monitor bus, you have more options, mostly + For setups with a monitor bus, more options are available, mostly governed by the setting of the Solo controls are Listen controls option - in Edit > Preferences > Solo / mute. + in Edit > Preferences > Mixer.
With Solo controls are Listen controls @@ -36,11 +36,11 @@ bus is fed from the master bus, so it sees the same thing.
- With
@@ -69,7 +69,12 @@
The solo-mute arrangement with a monitor bus is shown below:
- + + +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 @@ -80,12 +85,12 @@
In this scheme Solo has no effect other than to mute other non-soloed tracks; - with solo (rather then listen), the monitor out is fed from the master bus. + with solo (rather than listen), the monitor out is fed from the master bus.
- Edit > Preferences > Solo / Mute has some + Edit > Preferences > Mixer has some more solo options:
@@ -95,36 +100,39 @@ listened to on the master bus, this fader specifies the gain that will be applied to other tracks in order to mute them. Setting this level to -∞ dB will mean that other tracks will not be heard at all; setting to - 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 + some higher value less than 0dB means that other non-soloed tracks will be heard, just + reduced in volume compared to the soloed tracks. Using a value larger than -∞ 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 - control offers any level of "in-front-ness" that you might want to use. + control offers any level of "in-front-ness" that is desired. +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 track B.
+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 - is soloed. This is enabled by default, and we recommend that you leave it - that way unless you are extremely comfortable with Ardour's mute/solo + is soloed. This is enabled by default, and it is recommended to leave it + that way unless extremely comfortable with Ardour's mute/solo behaviour.
+If this is enabled, a track or bus that is both soloed and muted will behave as if it is soloed.
-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 bus) and to the main outputs.
-