title: Working With Tracks
---
-
{% children %}
title: Track Types
---
+<p>
+ Ardour offers three <dfn>track types</dfn> depending on the type of
+ data they contain, and differentiates between three <dfn>track modes</dfn>,
+ depending on their recording behaviour.
+</p>
-
- <h2>Data Type</h2>
-<p>An Ardour track can be either ‘audio’ or ‘MIDI’. The only real difference between the two is the type of data that the track will record and play back. Either type of track can pass either type of data. Hence, for example, one might have a MIDI track that contains an instrument plugin; such a track would record and play back MIDI data from disk but would produce audio, since the instrument plugin would turn MIDI data into audio data.</p>
-<p>Nevertheless, when adding tracks to a session, you typically have an idea of what you need to use the new tracks for, and Ardour offers you three choices:</p>
+<h2>Track types</h2>
+<p>
+ An Ardour track can be of type <dfn>audio</dfn> or <dfn>MIDI</dfn>,
+ depending on the <dfn>data</dfn> that the track will primarily record
+ and play back. <em>However, either type of track can pass either
+ type of data.</em> Hence, for example, one might have a MIDI track that
+ contains an instrument plugin; such a track would record and play back
+ MIDI data from disk but would produce audio, since the instrument plugin
+ would turn MIDI data into audio data.
+</p>
+<p>
+ Nevertheless, when adding tracks to a session, you typically have an idea
+ of what you need to use the new tracks for, and Ardour offers you three
+ choices:
+</p>
<dl class="narrower-table">
-<dt>Audio Tracks</dt>
-<dd>an Audio Track is created with a user-specified number of inputs. The number of outputs is defined by the master bus channel count (for details see "<a href="#channelconfiguration">Channel Configuration</a>" below). This is the type of bus to use when planning to work with existing or newly recorded audio.</dd>
-<dt>MIDI Tracks</dt>
-<dd>A MIDI track is created with a single MIDI input, and a single MIDI output. This is the type of track to use when planning to record and play back MIDI. There are several methods to enable playback of a MIDI track: by adding an instrument plugin to the track, by connecting the track to a software synthesizer, or connecting it to external MIDI hardware. If you add an instrument plugin, MIDI track outputs audio (instead of MIDI data) and delivers the signal other parts of Ardour.</dd>
-<dt>Audio/MIDI Tracks</dt>
-<dd>There are a few notable plugins that can usefully accept both audio and MIDI data (Reaktor is one, and various "auto-tune" like plugins are another). It can be tricky to configure this type of track manually, so Ardour allows you to select this track type specifically for use when working with such plugins. It is <strong>not</strong> generally the right choice when working normal MIDI tracks, and a dialog will warn you of this.</dd>
+ <dt>Audio</dt>
+ <dd>An <dfn>Audio Track</dfn> is created with a user-specified number of
+ inputs. The number of outputs is defined by the master bus channel count
+ (for details see <a href="#channelconfiguration">Channel Configuration</a>
+ below). This is the type of track to use when planning to work with
+ existing or newly recorded audio.</dd>
+ <dt>MIDI</dt>
+ <dd>A <dfn>MIDI track</dfn> is created with a single MIDI input, and a
+ single MIDI output. This is the type of track to use when planning to
+ record and play back MIDI. There are several methods to enable playback
+ of a MIDI track: add an instrument plugin to the track, connect the
+ track to a software synthesizer, or connect it to external MIDI hardware.
+ <p class="note">
+ If you add an instrument plugin, the MIDI track outputs audio instead
+ of MIDI data.
+ </p></dd>
+ <dt>Audio/MIDI</dt>
+ <dd>There are a few notable plugins that can usefully accept both <dfn>Audio
+ and MIDI</dfn> data (Reaktor is one, and various "auto-tune" like plugins
+ are another). It can be tricky to configure this type of track manually,
+ so Ardour allows you to select this type specifically for use with such
+ plugins. It is <em>not</em> generally the right choice when working normal
+ MIDI tracks, and a dialog will warn you of this.</dd>
</dl>
<h2 id="trackmodes">Track Modes</h2>
-<p>Audio tracks in Ardour can have a "mode" which affects how they behave when recording. </p>
+<p>
+ Audio tracks in Ardour have a <dfn>mode</dfn> which affects how they behave
+ when recording:
+</p>
<dl class="narrower-table">
-<dt>Normal</dt>
-<dd>Tracks using this mode will record non-destructively - new data is written to new files, and when overdubbing, new regions will be layered on top of existing ones (with or without crossfades. This is the recommended mode for most workflows.
-</dd>
-<dt>Non-Layered</dt>
-<dd>Tracks using this mode will record non-destructively - new data is written to new files, but when overdubbing if new regions overlap existing regions, the existing regions are trimmed so that there are no overlaps. This can be a very useful way of working with spoken word material, especially in combination with push/pull trimming.
-</dd>
-<dt>Tape</dt>
-<dd>Tracks using this mode do <strong>destructive</strong> recording: all data is recorded to a single file and if you overdub a section of existing data, the existing data is destroyed (irrevocably - there is no undo). Fixed crossfades are added at every punch in and out point. This mode can be useful for certain kinds of dubbing workflows, but it not suggested for normal use.</dd>
+ <dt>Normal</dt>
+ <dd>Tracks in <dfn>normal mode</dfn> will record non-destructively —
+ new data is written to new files, and when overdubbing, new regions will be
+ layered on top of existing ones. This is the recommended mode for most workflows.
+ </dd>
+ <dt>Non-Layered</dt>
+ <dd>Tracks using <dfn>non-layered mode</dfn> will record non-destructively
+ — new data is written to new files, but when overdubbing, the existing
+ regions are trimmed so that there are no overlaps. This does not affect
+ the previously recorded audio data, and trimmed regions can be expanded
+ again at will. Non-layered mode can be very useful for spoken word material,
+ especially in combination with <a href="/missing">push/pull trimming</a>.
+ </dd>
+ <dt>Tape</dt>
+ <dd><dfn>Tape-mode</dfn> tracks do <strong>destructive</strong> recording:
+ all data is recorded to a single file and if you overdub a section of existing
+ data, the existing data is destroyed irrevocably — there is no undo.
+ Fixed crossfades are added at every punch in and out point. This mode can be
+ useful for certain kinds of re-recording workflows, but it not suggested for normal
+ use.</dd>
</dl>
-<p>The screenshot below shows a subtle difference between results of an overdub in normal mode (upper track) and non-layered mode (lower track). Both tracks were created using identical audio data. The upper track shows an overdub (the middle shorter region) in normal mode. In normal mode Ardour created a new region which if you look carefully has been layered on top of the the existing (longer) region. The lower track is in non-layered mode, and rather than overlay the overdub region, it split the existing region and inserted the new overdub region in between. </p>
-<p><img src="/files/a3/a3_nonlayered_example.png" alt="normal and non-layered overdubbing comparision"
-/></p>
+<img class="right" src="/files/a3/a3_nonlayered_example.png" alt="normal and non-layered overdubbing comparision"
+/>
+<p>
+ The screenshot on the right shows the subtle difference between an overdub
+ in <dfn>normal mode</dfn> (upper track) and one in <dfn>non-layered mode</dfn>
+ (lower track). Both tracks were created using identical audio data. <br />
+ The upper track shows a new region which has been <dfn>layered on
+ top</dfn> of the the existing (longer) region. You can see this if you look
+ carefully at the region name strips.<br />
+ The lower track has split the existing region in two, trimmed each new
+ region to create space for the new overdub, and inserted the overdub region
+ in between.
+</p>
<h2 id="channelconfiguration">Channel Configuration</h2>
-<p>Ardour tracks can have any number of inputs and any number of outputs, and the number of either can be changed at any time (subject to restrictions caused by any plugins in a track). However it is useful to not have to configure this sort of thing for the most common cases, and so the <a href="/working-with-tracks/adding-tracks">Add Tracks</a> dialog allows you to select "Mono", "Stereo" and few other typical configurations.</p>
-<h3>What does Mono or Stereo actually mean?</h3>
-<p>Given that tracks have a certain number of inputs and a certain number of outputs and that these numbers may not necessarily be the same, it is not immediately clear what terms like "Mono" or "Stereo" mean. Most people know that mono refer to "one channel" and stereo refers "two channels", but there is some ambiguity. One input channel? Two output channels? </p>
-<p>If you are using Ardour's default mode of automatically connecting track (and bus) inputs and outputs, then the designation "Mono" or "Stereo" <em>refers to the <strong>input</strong> of the track</em>. A Mono track will have a single input and a Stereo track will have two inputs. </p>
-<p>The number of outputs for each will be determined by the number of inputs of the <strong>master <a href="/introducing-ardour/understanding-basic-concepts-and-terminology/#busses">bus</a></strong>, to which the track outputs will be connected. For example, if you have a two-channel master bus then a Mono track has only one input but two outputs connected to the master bus; a Stereo track has two inputs and two outputs connected to the master.</p>
-<p>However, if you choose not to have Ardour make connections automatically, then tracks will be left disconnected by default. In this scenario, a Mono track has 1 input and 1 output, and a stereo track has 2 inputs and 2 outputs. It is up to you to connect them as you wish. This is not a particularly useful way to work unless you are doing something fairly unusual with signal routing and processing. It is almost always preferable to leave Ardour to make connections automatically, even if you later change them manually.</p>
+<p>
+ Ardour tracks can have any number of inputs and any number of outputs, and the
+ number of either can be changed at any time (subject to restrictions caused by
+ any plugins in a track). However it is useful to not have to configure this sort
+ of thing for the most common cases, and so the
+ <a href="/working-with-tracks/adding-tracks">Add Tracks</a> dialog allows you to
+ select "Mono", "Stereo" and few other typical multichannel presets<br />
+ The name of the preset describes the number of <dfn>input channels</dfn>
+ of the track or bus.
+</p>
+<p>
+ If you have configured Ardour to automatically connect new tracks and
+ busses for you, the number of outputs will be determined by the number of
+ inputs of the <dfn>master <a
+ href="/introducing-ardour/understanding-basic-concepts-and-terminology/#busses">bus</a></dfn>,
+ to which the track outputs will be connected.<br />
+ For example, if you have a two-channel master bus, then a Mono track has one
+ input and two outputs; a Stereo track has two inputs and two outputs.
+</p>
+<p class="note">
+ If you you set <kbd class="menu">Edit > Preferences > Audio
+ > Connection of Tracks and Busses</kbd> to <kbd
+ class="menu">manual</kbd>, then tracks will be left disconnected by default
+ and there will be as many outputs as there are inputs. It is up to you to connect
+ them as you wish. This is not a particularly useful way to work unless you are doing
+ something fairly unusual with signal routing and processing. It is almost always
+ preferable to leave Ardour to make connections automatically, even if you later
+ change some of them manually.
+</p>
+
title: Adding Tracks and Busses
---
-
-
- <h2>Adding and removing tracks</h2>
+<img class="right" src="/ardour/manual/html/screenshots/add-track-or-bus.png" alt="the add-track dialog" />
<p>A track or bus can be added to a session in various ways:</p>
<ul>
-<li>Choose Add Track or Bus… from the Track menu.
-</li>
-<li>Right-click in an empty part of the track controls area.
-</li>
-<li>Click the plus (+) button underneath the list of tracks in the mixer.
-</li>
+ <li>Choose <kbd class="menu">Track > Add Track or Bus</kbd>.</li>
+ <li><kbd class="mouse">Right</kbd>-click in an empty part of the track controls area.</li>
+ <li>Click the <kbd class="menu">Plus (+)</kbd> button underneath the list of tracks in the mixer.</li>
</ul>
-<p>Any of these actions will open the Add Track or Bus dialog. Note that any new tracks from this dialog will appear after the last currently selected track (if any).</p>
-<p><img src="/ardour/manual/html/screenshots/add-track-or-bus.png" alt="the add-track dialog"
-/></p>
-<p>From here, you can select firstly the number of tracks or busses to add, and the type; audio track, MIDI track or bus. There are also some options, which vary depending on the type of thing you are creating.</p>
-<p>These options are:</p>
-<dl class="wide-table">
-<dt>Configuration (for audio tracks and busses)</dt>
-<dd>this is the number of inputs the track is set up with. You can always change these counts later.</dd>
-<dt>Track mode (for audio tracks)</dt>
-<dd>this can be ‘normal’, ‘non-layered’ or ‘tape’. See <a href="/working-with-tracks/track-types/#trackmodes">Track Modes</a> on the Track Types page for details.</dd>
-<dt>Group</dt>
-<dd>tracks and busses can be assigned groups so that a selected range of operations are applied to all members of a group at the same time (selecting record enable, or editing, for example). This option lets you assign to an existing group, or create a new group.</dd>
-<dt>Instrument (for MIDI tracks)</dt>
-<dd>this is a short-cut to assign an instrument plugin to the new MIDI track. You can achieve the same effect by creating a MIDI track with no plugins and adding it yourself; this option just saves you a step.</dd>
+<p>
+ Any of these actions will open the Add Track or Bus dialog. Note that any
+ new tracks from this dialog will appear after the last currently selected
+ track, or at the end if no track is selected.
+</p>
+<dl>
+ <dt>Add</dt>
+ <dd>Here you can select the number of tracks or busses you wish to create, and
+ their <a href="/working-with-tracks/track-types/">types</a>.</dd>
+ <dt>Configuration</dt>
+ <dd>This menu lets you choose from a number of <dfn><a href="/missing">route
+ templates</a></dfn>, which determine the number of input ports and optionally
+ contain plugins and other mixer strip configuration.</dd>
+ <dt>Track mode</dt>
+ <dd>This option is only available for audio tracks. See <a href="/working-with-tracks/track-types/#trackmodes">Track Modes</a> for details.</dd>
+ <dt>Instrument</dt>
+ <dd>This option is only available for MIDI tracks and lets you select a
+ default instrument from the list of available plugins.</dd>
+ <dt>Group</dt>
+ <dd>Tracks and busses can be assigned groups so that a selected range of
+ operations are applied to all members of a group at the same time (selecting
+ record enable, or editing, for example). This option lets you assign to an
+ existing group, or create a new group.</dd>
</dl>
-<p>New tracks appear in both the editor and mixer windows. The editor window shows the timeline, with any recorded data, and the mixer shows just the processing elements of the track (its plugins, fader and so on).</p>
-<p>Tracks and busses can be removed by selecting them, right-clicking and choosing ‘Remove’ from the menu. A warning dialog will pop up, as track removal cannot be undone; use this option with care! </p>
+<p>
+ New tracks appear in both the editor and mixer windows. The editor window
+ shows the timeline, with any recorded data, and the mixer shows just the
+ processing elements of the track (its plugins, fader and so on).
+</p>
+
+<h2>Removing Tracks and Busses</h2>
+<p>
+ To <dfn>remove</dfn> tracks and busses, select them, <kbd
+ class="mouse">right</kbd>-click and choose <kbd
+ class="menu">Remove</kbd>
+ from the menu. A warning dialog will pop up, as track removal cannot be undone;
+ use this option with care!
+</p>
title: Selecting Tracks
---
-
+<p>
+ Tracks are <dfn>selected</dfn> by clicking on the Track header at the left
+ of the Editor window. You can select multiple tracks with <kbd class="mod1
+ mouse">Left</kbd> clicks, or a range of consecutive tracks with <kbd
+ class="mod3 mouse">Left</kbd>.
+</p>
+<p>
+ By default, <dfn>selecting regions</dfn> has no impact on
+ <dfn>track selection</dfn>.
+ You can select a track, then select a region in another track
+ (or vice versa) and both selections will co-exist happily.
+ Operations that are applied to tracks will use the track selection,
+ and those that apply to regions will use the region selection.
+ Similarly, deselecting a region will not deselect the track it
+ is in (if that track was selected).
+</p>
+<p>
+ In some workflows, and particularly if you have experience with
+ other <abbr title="Digital Audio Workstation">DAW</abbr>s, this
+ is not the most comfortable way to work. You may prefer to work
+ in a style where selecting a region will also select the track
+ that the region is in. Similarly, when the last selected region
+ in a track is deselected, the track will also become unselected.
+</p>
+<p>
+ To control this behaviour, set <kbd class="menu">Edit >
+ Preferences > Editor > Link selection of regions and tracks</kbd>.
+</p>
-
-
-{% children %}
title: Controlling Track Appearance
---
-
-
- <p>Ardour offers many options for controlling the specific appearance of tracks, including color, height, waveform style and more.</p>
-
-<h2>Global Options</h2>
-<p>These can all be found via <code>Edit > Preferences > Editor</code></p>
-<dl class="wide-table">
-<dt>Show meters on tracks in the editor</dt>
-<dd>By default, Ardour displays meters in the track header in the editor window. Disable this option to hide the meter.</dd>
-<dt>Show waveforms in regons</dt>
-<dd>By default, Ardour draws waveforms within audio regions. Disable this option hide the waveforms.</dd>
-<dt>Waveform scale</dt>
-<dd>
-<dl>
-<dt>Linear</dt>
-<dd></dd>
-<dt>Logarithmic</dt>
-<dd></dd>
-</dl>
-</dd>
-<dt>Waveform shape</dt>
-<dd>
-<dl>
-<dt>Traditional</dt>
-<dd>The "zero" line appears in the middle of the display and waveforms appear as positive and negative heights above <em>and</em> below a "zero" line</dd>
-<dt>Rectified</dt>
-<dd>The "zero" line appears at the bottom of the display and waveforms appear as absolute heights <em>above</em> the "zero" line</dd>
-</dl>
-</dd>
-</dl>
-
+<p>
+ Ardour offers many options for controlling the appearance of tracks,
+ including color, height, waveform style and more.
+ These can all be found in the <kbd class="menu">Edit > Preferences >
+ Editor</kbd> menu.
+</p>
{% children %}
title: Layering Display
---
-
-
- <p>Ardour allows arbitrary layering of regions - you can stack as many regions you wish over a given position. By default, the editor windows overlaps the regions. The overlapping layers saves vertical space.</p>
-<p>However, this display mode can be confusing for tracks with many overdubs, because its not always entirely clear how the overdubs are all layered with respect to each other. Although there are other methods of moving particular regions to the top of an overlapping set, and although Ardour also has playlists to let you manage takes a bit more efficiently than just continually overdubbing, there are times when being able to clearly see all regions in a track without any overlaps is reassuring and useful. </p>
-<p>Here is an image of a track with a rather drastic overdub/overlap situation, viewed in normal "overlaid" mode:</p>
-<p><img src="/files/a3/a3_overlaps_layered.png" alt="overlapping regions in overlaid mode" /></p>
-<p>To change this display, right click on the track header, and you'll see this menu:</p>
-<p><img src="/files/a3/a3_layers_menu.png" alt="layer display menu" /></p>
-<p>You will see that there are two choices for "Layers": overlaid (currently selected) and stacked. Click on stacked and the track display changes to this:</p>
-<p><img src="/files/a3/a3_layers_stacked.png" alt="overlapping regions in stacked mode" /></p>
-<p>You can still move regions around as usual, and in fact you can even drag them so that they overlay each again, but when you release the mouse button, things will flip back to them all being stacked cleaning. This display mode works best when you use sensible track heights. The number of "lanes" for the track is determined by the maximum number of regions existing in any one spot throughout the track, so if you have really stacked up 10 overdubs in one spot, you'll end up with 10 lanes. Obviously, using a large track height works much better for this than a small one.</p>
+<img class="right" style="clear:both" src="/images/track-layer-dialog.png"
+alt="Track layering menu" /></p>
+<p>
+ Ardour allows arbitrary <dfn>layering</dfn> of regions — you can
+ have as many regions you wish at a given position. By default, the regions are
+ <dfn>overlaid</dfn> in the editor window, to save vertical space.
+</p>
+<p>
+ However, this display mode can be confusing for tracks with many overdubs,
+ because its not obvious in which order the overdubs are layered. Although
+ there are other methods of moving particular regions to the top of an
+ overlapping set, and although Ardour also has playlists to let you manage
+ <a href="/working-with-playlists/playlist_usecases/">takes</a> a bit more
+ efficiently than just continually layering,
+ there are times when being able to clearly see all regions in a track without
+ any overlaps is reassuring and useful.
+</p>
+<p>
+ Here is an image of a track with a rather drastic overdub situation,
+ viewed in normal <dfn>overlaid mode</dfn>:
+</p>
+<img src="/files/a3/a3_overlaps_layered.png" alt="overlapping regions in overlaid mode" />
+<p>
+ To change this display, right click on the track header, and you'll see
+ the menu displayed above. There are two choices for layers. <kbd
+ class="menu">overlaid</kbd> is currently selected. Click on <kbd
+ class="menu">stacked</kbd> and the track display changes to this:
+</p>
+<img src="/files/a3/a3_layers_stacked.png" alt="overlapping regions in stacked mode" /></p>
+<p>
+ You can still move regions around as usual, and in fact you can
+ even drag them so that they overlay each again, but when you
+ release the mouse button, things will flip back to them all being
+ stacked cleanly. The number of <dfn>lanes</dfn> for the track is determined by
+ the maximum number of regions existing in any one spot throughout
+ the track, so if you have really stacked up 10 overdubs in one spot,
+ you'll end up with 10 lanes. Obviously, using a large track height
+ works much better for this than a small one.
+</p>
---
layout: default
-title: Track Coloring
+title: Track Color
---
+<p>
+ New tracks in Ardour are assigned a random color from a pastel color
+ palette, so they should never end up being particularly bright or
+ particularly dark.
+</p>
+<h2>Changing the color of specific tracks</h2>
+<p>
+ Select the tracks whose color you wish to change. Context-click
+ on the track header of one of them. From the context menu, select
+ <kbd class="menu">Color</kbd> and pick a hue to your taste in the
+ <a href="/missing">color dialog</a>. Every selected track will be
+ re-colored.
+</p>
+<p>
+ Note that if you are only changing one track, context-clicking on
+ that track's header will be enough to select it, saving the extra
+ mouse click.
+</p>
-
- <h2>Track Color</h2>
-<p>New tracks in Ardour are assigned a random color from a pastel color spectrum, so they should never end up being particularly bright or particularly dark. </p>
-<h3>Changing the color of specific tracks</h3>
-<p>Select the tracks whose color you wish to change. Context-click (right-click) on the track header of one of them. From the context menu, select "Color". A <a href="/missing">color dialog</a> will appear. Choose the new color for the track, and click "OK" in the dialog. Every selected track will be recolored, both in the editor and mixer window.</p>
-<p>Note that if you are only changing one track, context-clicking on that track's header will be enough to select it, saving the extra mouse click.</p>
-<h3>Changing the color of all tracks in a group</h3>
-<p>Tracks that belong to a <a href="/working-with-tracks/track-and-bus-groups">track/bus group</a> can share the color of the group by enabling the <code>Color</code> option for the group. </p>
-<p>When this is enabled, you can change the color of the entire group by following the process described above for specific tracks - the new color will be used by all tracks in the group.</p>
-<p>You can also explicitly change the group color by context-clicking on the group tab, selecting <code>Edit Group...</code> and then clicking on the Color selector in the dialog that is displayed. After you click "OK" in the color dialog that is provided for picking the color, all tracks in the group will be recolored to match the group color.</p>
+<h2>Changing the color of all tracks in a group</h2>
+<p>
+ Tracks that belong to a
+ <a href="/working-with-tracks/track-and-bus-groups">track/bus group</a>
+ can share a common color by enabling the <kbd
+ class="option">Color</kbd> option for the group. With this enabled,
+ any color change will be propagated to all group members.
+</p>
+<p>
+ You can also explicitly change the group color by context-clicking
+ on the group tab in the Mixer, selecting <kbd class="menu">Edit
+ Group...</kbd> and then clicking on the Color selector in that dialog
+ that is displayed.
+ </p>
title: Track Height
---
-
-
- <h2>Via the Context Menu</h2>
-<p>Context click (right click) on the track header to select a track and display a context menu that includes the <code>Height</code> choice. Choose this, and a submenu appears containing a number of preset heights. Choose one of them, and all selected tracks will be redrawn using that height.</p>
-
-<h2>Via Mouse Drag</h2>
-<p>Select the tracks you wish to resize. Move the pointer to the bottom edge of the track header. The cursor will change to a two-way vertical arrow shape. <kbd>Left-click-drag</kbd> to dynamically resize all the selected tracks.</p>
-
+<p>
+ Depending on the stage of your production, you may require a quick
+ overview over as many tracks as possible, a detailed view into just a
+ few, or a combination of the two. To facilitate this, the
+ <dfn>height</dfn> may be configured individually for each track in
+ the editor window.
+</p>
+<p>
+ A context click on a track header will display the
+ <kbd class="menu">Height</kbd> menu, and allow you to choose from a
+ list of standard sizes. All selected tracks will be redrawn using that
+ height.
+</p>
+<p>
+ Alternatively, select the tracks you wish to resize. Move the pointer
+ to the bottom edge of one track header. The cursor will change to a
+ two-way vertical arrow shape. <kbd class="mouse">Left</kbd>-drag to
+ dynamically resize all selected tracks.
+</p>
<h2>Fit to the Editor Window</h2>
-<p>Select the tracks you wish to display in the Editor window. Choose <code>Track > Height > Fit Selected Tracks</code> (or use the keyboard shortcut, <kbd>f</kbd>). Ardour ajusts the track heights and track view so that the selected tracks completely fill the vertical space available.</p>
-<p>You can use <code>Visual Undo</code> (default shortcut: <kbd>Shift-Z</kbd> to undo this operation.</p>
+<p>
+ Select the tracks you wish to display in the Editor window.
+ Choose <kbd class="menu">Track > Height > Fit Selected Tracks</kbd>
+ or use the keyboard shortcut, <kbd>f</kbd>. Ardour adjusts the track
+ heights and view so that the selected tracks completely fill the vertical
+ space available, unless the tracks cannot be fitted even at the smallest
+ possible size.
+</p>
+<p class="note">
+ You can use <dfn>Visual Undo</dfn> (default shortcut: <kbd class="mod3">Z</kbd>
+ to revert this operation.
+</p>
title: Controlling Track Ordering
---
-
-
- <p>Ardour does not impose any particular ordering of tracks and busses in either the editor or mixer windows. The default arrangement is as follows:</p>
-
-<h2>Editor Default Arrangement</h2>
-<ul>
-<li>Master bus on top</li>
-<li>Tracks and busses in their initial order, from top to bottom.</li>
-<li>Even if you use a Monitor section, it is never visible in the editor window.
-</li>
-</ul>
-
-<h2>Mixer Default Arrangement</h2>
-<ul>
-<li>Tracks in their initial order, from left to right
-</li>
-<li>Master bus on the right, in its own pane so that it is always visible no matter how other mixer strips are scrolled.
-</li>
-<li>If a Monitor section is used, that is at the right edge of the mixer window (it can be torn off, too)
-</li>
-</ul>
-
-<h2>Synchronized Editor and Mixer Window Ordering</h2>
-<p>The ordering within the editor and mixer windows is synchronized: if you reorder in one window, the ordering in the other window will change.</p>
-
-<h2>Reordering Specific Tracks... </h2>
-<h3>... in the Editor Window, via the Keyboard</h3>
-<p>Select the tracks you want to move. Then use <code>Track > Move Selected Tracks Up</code> (<kbd class="mod1">↑</kbd>) or <code>Track > Move Selected Tracks Down</code> (<kbd class="mod1">↓</kbd>) to move the selected track(s) up or down in the editor window.</p>
-
-<h3>... in the Editor Window, via Drag-n-Drop</h3>
-<p>Make the <a href="/ardours-interface/introducing-the-editor-window/editor-lists/">Editor Lists</a> visible. Select the <code>Tracks & Busses</code> tab. In the Tracks & Busses side panel, you can freely drag-and-drop tracks and busses into any order you prefer.</p>
-
-<h3>... in the Mixer Window, via Drag-n-Drop</h3>
-<p>Within the "Strips" pane (Mixer window, top left), you can freely drag-and-drop tracks and busses into any order you prefer.</p>
-
-<h2>"Collecting" Group Members</h2>
-<p>Tracks and Busses that are members of a group can be reordered so that they display contiguously within the Editor and Mixer windows. Context-click on the group tab and choose "Collect". </p>
-
-<h3>... via Adding New Tracks</h3>
-<p>When adding new tracks, the current selection determines their initial order. If one or several tracks are selected, new tracks will be placed after the rightmost (in the mixer) or bottom-most (in the editor) selected track. If no tracks are selected, new tracks will be last in the track order.</p>
-<h3>Note</h3>
-<blockquote><p>Because new tracks are automatically selected, you can quickly reorder them in the editor window via the keyboard (see above).</p></blockquote>
-
+<p>
+ Ardour does not impose any particular ordering of tracks and busses in
+ either the editor or mixer windows. The default arrangements are as follows:
+</p>
+<p>
+ In the <dfn>Editor</dfn>, the Master bus will always be on top unless
+ hidden. Tracks and busses will appear in their initial order, from top to
+ bottom. The monitor section (if used) will never be visible in the editor
+ window.
+</p>
+<p>
+ In the <dfn>Mixer</dfn>, the tracks and busses will be displayed in their
+ initial order, from left to right. The Master bus is always on the far
+ right and occupies its own pane, so that it is always visible no matter
+ how you scroll the other mixer strips. If a Monitor section is used,
+ it shows up at the right edge of the mixer window, from where it can be
+ torn off into a separate window.
+</p>
{% children %}
layout: default
title: Track Ordering and Remote Control IDs
---
-
-
- <p>Every track and bus in Ardour is assigned a remote control ID. When various protocols such as <a href="/using-control-surfaces/">Mackie Control or OSC</a> are used to control Ardour, these remote control IDs are used to identify which track(s) or buss(es) are the intended target of the commands. </p>
-<p>By default, remote ID's will be assigned to tracks and busses in the order that they are created, starting from 1. The master bus and monitor section have their own unique IDs (318 and 319).</p>
-<p>Ardour provides 3 methods to control remote control IDs, which can be chosen via <code>Edit > Preferences > User Interaction</code>:</p>
+<p>
+ Every track and bus in Ardour is assigned a <dfn>remote control ID</dfn>.
+ When a <a href="/using-control-surfaces/">control surface</a> or any other
+ remote control is used to control Ardour, these IDs are used to identify
+ which track(s) or buss(es) are the intended target of incoming commands.
+</p>
+<p>
+ By default, remote IDs will be assigned to tracks and busses in the order
+ that they are created, starting from 1. The master bus and monitor section
+ have their own unique IDs (318 and 319).
+</p>
+<p>
+ Ardour provides two methods to control remote control IDs, which can be
+ chosen via <kbd class="menu">Edit > Preferences > Control Surfaces
+ > Control surface remote ID</kbd>:
+</p>
<dl class="wide-table">
-<dt>Follow order of editor</dt>
-<dd>When enabled, remote control IDs will be reset to match the editor window order, so that the leftmost track/bus has RID 1. Manual assignment of RIDs is not possible.</dd>
-<dt>Follow order of mixer</dt>
-<dd>When enabled, remote control IDs will be reset to match the mixer window order, so that the leftmost track/bus has RID 1. Manual assignment of RIDs is not possible.</dd>
-<dt>Assigned by user</dt>
-<dd>When enabled, the remote control ID is completely independent of the ordering in either window, and RID's may be changed manually by the user.
-</dd>
+ <dt>follows order of mixer</dt>
+ <dd>This will reset the remote control IDs to match the mixer and editor
+ track order order, starting with rcID 1. Manual assignment of rcIDs is
+ not possible.</dd>
+ <dt>assigned by user</dt>
+ <dd>When enabled, the remote control ID is completely independent of the
+ ordering in either window, and may be changed manually by the user via the
+ <kbd class="menu"><em>trackname</em> > Remote Control ID...</kbd>
+ dialog in each mixer strip.
+ </dd>
</dl>
-<p> </p>
-<!-- remove if more text is added below --><!-- remove if more text is added below -->
title: Bus Controls
---
+<p>A typical control area or <dfn>bus header<dfn> is shown below:</p>
+<img src="/ardour/manual/html/screenshots/typical-bus-controls.png" alt="bus controls" />
-
- <p>A typical control area or "bus header" is shown below:</p>
-<p><img src="/ardour/manual/html/screenshots/typical-bus-controls.png" alt="bus controls"
- /></p>
-<p> At the top-left of the controls is the name of the bus. You can double click to edit the name, but the name must be unique within the session. Underneath the name is a copy of the bus' main level fader. The control buttons to the right-hand side are:</p>
+<p>
+ At the top-left of the controls is the name of the bus, which can be
+ edited by double-clicking on it. The new name must be unique within the
+ session. Underneath the name is a copy of the bus' main level fader.
+ The control buttons to the right-hand side are:
+</p>
<dl>
-<dt id="mute">m</dt>
-<dd>Mute — click to mute the bus. Right-click to display a menu which dictates what particular parts of the bus should be muted.</dd>
-<dt id="solo">s</dt>
-<dd>Solo — solo the bus. The behaviour of the solo system is described in detail in the section called “Mute and solo”.</dd>
-<dt id="automation">a</dt>
-<dd>Automation — click to open a menu related to automation for the bus. For details see <a href="/automation/">Automation</a>.</dd>
-<dt id="group">g</dt>
-<dd>Group — click to open a menu related to the bus group. For details see <a href="/working-with-tracks/track-and-bus-groups/">Track and bus groups</a>. </dd>
+ <dt id="mute">m</dt>
+ <dd><dfn>Mute</dfn> — click to mute the bus. Right-click to display
+ a menu which dictates what particular parts of the bus should be muted.</dd>
+ <dt id="solo">s</dt>
+ <dd><dfn>Solo</dfn> — solo the bus. The behaviour of the solo system
+ is described in detail in the section <a
+ href="/mixing/muting-and-soloing/">Muting and Soloing</a>.</dd>
+ <dt id="automation">a</dt>
+ <dd><dfn>Automation</dfn> — opens the automation menu for the
+ bus. For details see <a href="/automation/">Automation</a>.</dd>
+ <dt id="group">g</dt>
+ <dd><dfn>Group</dfn> — lets you assign the bus to an existing or a
+ new group. For details see <a href="/working-with-tracks/track-and-bus-groups/">Track and bus groups</a>. </dd>
</dl>
-<p> </p>
title: Audio Track Controls
---
-
-
- <p>A typical control area or "track header" for an audio track is shown below:</p>
-<p><img src="/ardour/manual/html/screenshots/typical-audio-track-controls.png" alt="audio track controls"
- /></p>
-<p> An audio track has the same <a href="/working-with-tracks/bus-controls">controls as a bus</a>, with the addition of two extras.
+<p>
+ A typical control area or <dfn>track header</dfn> for an audio track is
+ shown below:
+</p>
+<img src="/ardour/manual/html/screenshots/typical-audio-track-controls.png" alt="audio track controls"
+ />
+<p>
+ An audio track has the same
+ <a href="/working-with-tracks/bus-controls">controls as a bus</a>, with the
+ addition of two extras.
</p>
<dl>
-<dt id="record">[pink circle]</dt>
-<dd>Record - The red button with the pink circle enables recording to the track. When this is clicked it will gain a bright red outline, and the track will then be recorded onto when the main session record enable is turned on with the transport rolling.</dd>
-<dt id="playlist">p</dt>
-<dd>Playlist - Opens a playlist menu when clicked. The menu offers various operations related to the track's playlist. This, as you will recall, is simply a list of the regions that the track should play. Playlists may be swapped on a given track, and may be used by more than one track at the same time. They are often useful to keep different takes, for example, or to allow one set of regions to be played off two tracks with different processing. For more details see <a href="/working-with-playlists/">Working With Playlists</a>.</dd>
+ <dt id="record" style="color:pink">[•]</dt>
+ <dd><dfn>Record</dfn> — The button with the pink circle arms the track
+ for recording. When armed, the entire button will turn pink, and change to
+ bright red as soon as the transport is rolling and the track is recording.</dd>
+ <dt id="playlist">p</dt>
+ <dd><dfn>Playlist</dfn> &mdash Opens a playlist menu when clicked. The menu
+ offers various operations related to the track's <a
+ href="/working-with-playlists/">playlist</a>.
+ </dd>
</dl>
layout: default
title: MIDI Track Controls
---
-
-
- <p>A typical control area for a MIDI track is shown below:</p>
-<p><img src="/ardour/manual/html/diagrams/typical-midi-track-controls.png" alt="midi track controls"
- /></p>
-<p>To see the full set of MIDI track controls, as shown above, you need to increase the <a href="/working-with-tracks/controlling-track-appearance/track-height/">track height</a> beyond the default. MIDI tracks show only a few of the control elements when when there is insufficient vertical space.</p>
-<p>A MIDI track has the same basic <a href="/working-with-tracks/audio-track-controls">controls as an audio track</a>, with the addition of two extra elements. The set of buttons below the main track controls controls the MIDI channels that should be visible in the editor. A MIDI track's data may span any number of the 16 available MIDI channels, and sometimes it is useful to view only a subset of those channels; different instruments may, for example, be put on different MIDI channels. Clicking on a channel number toggles its visibility.</p>
-<p>To the right of the MIDI track controls is a representation of a piano keyboard called the ‘scroomer’. This performs a couple of functions. Firstly, the scrollbar controls the range of pitches that are visible on the track. Drag the body of the scrollbar up and down to display higher or lower pitches. Drag the scrollbar ‘handles’ to zooms in and out and increase and decrease the range of visible pitches. The piano keyboard gives a reference for the pitches visible on the track. In addition, clicking on the piano plays the corresponding MIDI note for reference. </p>
-<p>To edit the contents of a MIDI track see <a href="/editing-and-arranging/edit-midi/">Edit MIDI</a></p>
+<p>A typical <dfn>MIDI track header</dfn> looks like this:</p>
+<img src="/ardour/manual/html/diagrams/typical-midi-track-controls.png" alt="midi track controls"
+ />
+
+<p>
+ To see the full set of MIDI track controls, you need to increase the
+ <a href="/working-with-tracks/controlling-track-appearance/track-height/">track height</a>
+ beyond the default. MIDI tracks show only a few of the control elements
+ when there is insufficient vertical space.
+</p>
+<p>
+ A MIDI track has the same basic
+ <a href="/working-with-tracks/audio-track-controls">controls as an audio track</a>,
+ with the addition of two extra elements. The set of buttons below the main track
+ controls the <dfn>MIDI channel</dfn>(s) that will be visible in the editor. A MIDI track's
+ data may span any number of the 16 available MIDI channels, and sometimes it is
+ useful to view only a subset of those channels; different instruments may,
+ for example, be put on different channels. Clicking on a channel number toggles
+ its visibility.
+</p>
+<p>
+ To the right of the MIDI track controls is a representation of a piano keyboard
+ called the <dfn>scroomer</dfn>. This performs a couple of functions.
+ The scrollbar controls the range of pitches that are visible on the
+ track, as visualized by the piano keyboard.<br />
+ Drag the body of the scrollbar up and down to display higher or lower
+ pitches.<br />
+ Drag the scrollbar handles to zooms in and out and increase and decrease the
+ range of visible pitches.<br />
+ clicking on the piano plays the corresponding MIDI note for reference.
+</p>
+<p>
+ To edit the contents of a MIDI track see <a href="/editing-and-arranging/edit-midi/">Edit
+ MIDI</a>.
+</p>
layout: default
title: Track Context Menu
---
-
-
- <p>Within the editor window, context-click (right-click) on either a region or empty space within a track to display the <em>track context menu</em>. The context menu provides easy access to many track-level operations.</p>
-<p>If you click on a region, the first item in the menu is the name of the region. If you click on a <a href="/working-with-tracks/controlling-track-appearance/layering-display/">layered region</a>, the next item in the menu is <code>Choose Top</code>. If selected, you will see a dialog that allows you to reorder the stacking of layers at that point. See <a href="/missing">Adjusting Region Layering</a> for more details.</p>
-<p>The rest of the track context menu is structured as follows:</p>
-<dl class="narrower-table">
-<dt>Play</dt>
-<dd>
-<dl class="narrower-table">
-<dt>Play from Edit Point</dt>
-<dd>Play from the location of the current <a href="/editing-and-arranging/the-edit-point">edit point</a>.</dd>
-<dt>Play from Start </dt>
-<dd>Play from the start of the session</dd>
-<dt>Play Region(s)</dt>
-<dd>Plays the duration of the session from the start of the earliest selected region to the end of the latest selected region</dd>
-</dl>
-</dd>
-<dt>Select</dt>
-<dd>
-<dl class="narrower-table">
-<dt>Select All in Track</dt>
-<dt>Select All</dt>
-<dt>Invert Selection in Track</dt>
-<dt>Invert Selection</dt>
-<dt>Set Range to Loop Range</dt>
-<dt>Set Range to Punch Range</dt>
-<dt>Select All After Edit Point</dt>
-<dt>Select All Before Edit Point</dt>
-<dt>Select All After Playhead</dt>
-<dt>Select All Before Playhead</dt>
-<dt>Select All Between Playhead and Edit Point</dt>
-<dt>Select All Within Playhead and Edit Point</dt>
-<dt>Select Range Between Playhead and Edit Point</dt>
-</dl>
-</dd>
-<dt>Edit</dt>
-<dd>
+<p>
+ Within the editor window, context-click (right-click) on either a region
+ or empty space within a track to display the <dfn>track context menu</dfn>.
+ The context menu provides easy access to many track-level operations.
+</p>
+<p>
+ If you click on a <dfn>region</dfn>, the first item in the menu is the name of the
+ region. If you click on a
+ <a href="/working-with-tracks/controlling-track-appearance/layering-display/">layered region</a>,
+ the next item in the menu is <kbd class="menu">Choose Top</kbd>. If selected,
+ you will see a dialog that allows you to change the vertical order of layers
+ at that point. See <a href="/missing">Controlling Region Layering</a> for more details.
+</p>
+<p>
+ The rest of the track context menu is structured as follows:
+</p>
<dl class="narrower-table">
+ <dt>Play</dt>
+ <dd>
+ <dl class="narrower-table">
+ <dt>Play from Edit Point</dt>
+ <dd>Play from the location of the current <a href="/editing-and-arranging/the-edit-point">edit point</a>.</dd>
+ <dt>Play from Start </dt>
+ <dd>Play from the start of the session</dd>
+ <dt>Play Region(s)</dt>
+ <dd>Plays the duration of the session from the start of the earliest selected region to the end of the latest selected region</dd>
+ </dl>
+ </dd>
+ <dt>Select</dt>
+ <dd>
+ <dl class="narrower-table">
+ <dt>Select All in Track</dt>
+ <dt>Select All</dt>
+ <dt>Invert Selection in Track</dt>
+ <dt>Invert Selection</dt>
+ <dt>Set Range to Loop Range</dt>
+ <dt>Set Range to Punch Range</dt>
+ <dt>Select All After Edit Point</dt>
+ <dt>Select All Before Edit Point</dt>
+ <dt>Select All After Playhead</dt>
+ <dt>Select All Before Playhead</dt>
+ <dt>Select All Between Playhead and Edit Point</dt>
+ <dt>Select All Within Playhead and Edit Point</dt>
+ <dt>Select Range Between Playhead and Edit Point</dt>
+ </dl>
+ </dd>
+ <dt>Edit</dt>
+ <dd>
+ <dl class="narrower-table">
<dt>Cut</dt>
<dt>Copy</dt>
<dt>Paste</dt>
</dd>
<dt>Freeze</dt>
</dl>
-<p> </p>
-<!-- remove if/when more text is added here --><!-- remove if/when more text is added here -->
title: Track and Bus Groups
---
-
-
- <p> Tracks and busses can be put into groups. You can set members of a group can to share various settings - useful for managing tracks that are closely related to each other. Examples might include tracks that contain multiple-microphone recordings of a single source (an acoustic guitar, perhaps, or a drum-kit).</p>
-<p>You can group tracks and busses in various ways. In the editor window, a track's controls might look like these:</p>
-<p><img src="/ardour/manual/html/screenshots/track-in-group.png" alt="track headers for a group" /></p>
-<p> The green tab to the left of the track header indicates that this track is in a group called ‘Fred’. You can drag these tabs to add or remove tracks from a group. </p>
+<p>
+ Tracks and busses can be put into <dfn>groups</dfn>. Members of a group
+ can share various settings — useful for managing tracks that are closely
+ related to each other. Examples might include tracks that contain
+ multiple-microphone recordings of a single source (an acoustic guitar,
+ perhaps, or a drum-kit).
+</p>
+<p>
+ You can group tracks and busses in various ways. In the editor window,
+ a track's controls might look like these:</p>
+<img src="/ardour/manual/html/screenshots/track-in-group.png" alt="track headers for a group" />
+<p>
+ The green tab to the left of the track header indicates that this track
+ is in a group called <samp>Fred</samp>. You can drag these tabs to add
+ adjacent tracks to a group.
+</p>
<h2>Create New Groups</h2>
-<p>There are several ways to create groups for tracks and bussess:</p>
+<p>
+ There are several ways to <dfn>create groups</dfn> for tracks and bussess:
+</p>
<ul>
-<li><p>Context-click (right-click) on the group tab and use one of the "Create..." options there. You can create a group with no members, or one that starts with the currently selected tracks, or record-enabled tracks, or soloed tracks.</p></li>
-<li><p>Alternatively, click the ‘g’ button on a track header to open the Group menu. The menu lists the available groups. Selecting one of these groups will add the track or bus to that group. The menu also lets you create a new group.</p></li>
-<li><p>Finally, the Groups tab of the <a href="/ardours-interface/introducing-the-editor-window/editor-lists">Editor Lists</a> or the Mixer Window has a plus (+) button at the bottom of the list. Click on the plus sign to create a new group.</p></li>
+ <li>Context-click on the group tab and use one of the <kbd
+ class="menu">Create...</kbd> options there. You can create a group with
+ no members, or one that starts with the currently selected tracks, or
+ record-enabled tracks, or soloed tracks.</li>
+ <li>Alternatively, click the ‘g’ button on a track header to open the
+ Group menu. The menu lists the available groups. Selecting one of these
+ groups will add the track or bus to that group. The menu also lets you
+ create a new group.</li>
+ <li>Finally, the Groups tab of the
+ <a href="/ardours-interface/introducing-the-editor-window/editor-lists">Editor Lists</a>
+ or the Mixer Window has a <kbd class="menu">plus (+)</kbd> button at the
+ bottom of the list. Click on the plus sign to create a new group.</li>
</ul>
<h2>Remove Groups</h2>
-<p>Context-click on a group tab and select <code>Remove Group</code> from the menu. Removing a group does <strong>not</strong> remove the members of a group.</p>
-<p>You can also remove groups by selecting them in the Groups tab of the <a href="/ardours-interface/introducing-the-editor-window/editor-lists">Editor Lists</a> or Mixer Window and then pressing the "-" button at the bottom of the list.</p>
+<p>
+ Context-click on a <dfn>group tab</dfn> and select <kbd class="menu">>Remove
+ Group</kbd> from the menu. Removing a group does <em>not</em> remove
+ the members of a group.
+</p>
+<p>
+ You can also remove groups by selecting them in the Groups tab of the
+ <a href="/ardours-interface/introducing-the-editor-window/editor-lists">Editor Lists</a>
+ or Mixer Window and then pressing the "-" button at the bottom of the list.
+</p>
<h2>Add/Remove Tracks and Busses From a Group</h2>
-<p>Click the ‘g’ button to display a menu with a list of the available groups. Select one of these groups to add the track or bus to that group. Select "No Group" to remove it. </p>
-<p>Alternatively, you can also drag a group tab to add or remove tracks from the group.</p>
+<p>
+ Click the <kbd class="menu">g</kbd> button to display a menu with a list
+ of the available groups. Select one of these groups to add the track or bus
+ to that group. Select <kbd class="menu">No Group</kbd> to remove it.
+</p>
+<p>
+ Alternatively, you can also drag a group tab to add or remove tracks from
+ the group.
+</p>
<h2>Activate/Deactivate Groups via the Group Tab</h2>
-<p>Clicking on a group tab toggles the group between being active and inactive. An inactive group has no effect when editing its members. An active group will share one or more properties across its members. Tabs for disabled groups are coloured grey.</p>
+<p>
+ Clicking on a group tab toggles the group between being active and inactive.
+ An inactive group has no effect when editing its members. An active group
+ will share its configured properties across its members. Tabs for disabled
+ groups are coloured grey.</p>
<h2>Modify Group Properties</h2>
-<p>To edit the properties of a group, context-click (right-click) on its tab and choosing Edit Group…. This opens the track/bus group dialog, which is also used when creating new groups:</p>
-<p><img src="/ardour/manual/html/screenshots/route-group-dialogue.png" alt="the track/bus group dialog" /></p>
+<p>
+ To edit the properties of a group, context-click on its tab and choose
+ <kbd class="menu">Edit Group…</kbd>. This opens the track/bus group dialog,
+ which is also used when creating new groups:
+</p>
+
+<img src="/ardour/manual/html/screenshots/route-group-dialogue.png" alt="the track/bus group dialog" />
<h3>Group Color</h3>
-<p>Click on the color selector button to change a group's colour. This affects the colour of the group's tab in the editor and mixer windows. The color does <strong>not</strong> affect the color of the group members unless you also enable the shared <code>Color</code> property. </p>
-<p>Following these options are a list of the things that the members of the group can share. </p>
+<p>
+ Click on the color selector button to change a group's colour. This affects
+ the colour of the group's tab in the editor and mixer windows. The color does
+ <em>not</em> affect the color of the group members unless you also enable the
+ shared <kbd class="menu">Color</kbd> property.
+</p>
<h3>Shared Properties</h3>
-<p><code>Gain</code> means that the track faders will be synced to always have the same value; ‘Relative’ means that the gain changes are applied relative to each member's current value. If, for example, there are two tracks in a group with relative gain sharing, and their faders are set to -3dB and -1dB, a change of the first track to a gain of -6dB will result in the second track having a gain of -4dB (so that the difference in gains is the same).</p>
-<p><a href="/working-with-tracks/bus-controls/#mute"><code>Muting</code></a>, <a href="/working-with-tracks/bus-controls/#solo"><code>soloing</code></a>, <a href="/working-with-tracks/audio-track-controls/#record"><code>record enable</code></a>, <a href="/ardours-interface/introducing-the-editor-window/editor-lists/tracks--busses-list/#active"><code>active state</code></a>, <a href="/working-with-tracks/controlling-track-appearance/track-coloring/"><code>colour</code></a> and <a href="/recording/monitoring/"><code>monitoring</code></a> are all straightforward. They simply mean that all member tracks or busses will share the same settings in these respects.</p>
-<p><code>Selection</code> means that if a region is selected or deselected on one constituent track, corresponding regions on other member tracks will be similarly selected. Corresponding regions are those that are at the same position and have the same length. Since region editing operations are applied to all currently selected regions, this is the way to make edits apply across all tracks in the group. For more details see <a href="/working-with-regions/region-selection-equivalence/">Region Selection Equivalence</a></p>
+<p>
+ <kbd class="option">Gain</kbd> means that the track faders will be synced to
+ always have the same value; <kbd class="option">Relative</kbd> means that the
+ gain changes are applied relative to each member's current value. If, for
+ example, there are two tracks in a group with relative gain sharing, and their
+ faders are set to -3 dB and -1 dB, a change of the first track to a
+ gain of -6 dB will result in the second track having a gain of
+ -4 dB (the <em>difference</em> of the gains remains the same).
+</p>
+<p>
+ <a href="/working-with-tracks/bus-controls/#mute"><kbd class="option">Muting</kbd></a>,
+ <a href="/working-with-tracks/bus-controls/#solo"><kbd class="option">Soloing</kbd></a>,
+ <a href="/working-with-tracks/audio-track-controls/#record"><kbd class="option">record enable</kbd></a>,
+ <a href="/ardours-interface/introducing-the-editor-window/editor-lists/tracks--busses-list/#active"><kbd class="option">active state</kbd></a>, <a href="/working-with-tracks/controlling-track-appearance/track-coloring/"><code>colour</code></a> and <a href="/recording/monitoring/"><code>monitoring</code></a>
+ are all straightforward. They simply mean that all member tracks or busses will
+ share the same settings in these respects.
+</p>
+<p>
+ <kbd class="option">Selection</kbd> means that if a region is selected or
+ deselected on one member track, <a
+ href="/working-with-regions/corresponding-region-selection/">corresponding
+ regions</a> on other member tracks
+ will be similarly selected. Since region editing operations are applied to all
+ currently selected regions, this is the way to make edits apply across all tracks
+ in the group.
+</p>
<h3>Group Tab Context Menu</h3>
-<p>Context-clicking (right-clicking) on the group tab offers a further menu of group-related actions. </p>
+<p>Context-clicking on the group tab offers a further menu of group-related actions. </p>
<dl class="wide-table">
<dt>Create a New Group</dt>
<dd>create a new group</dd>
<dt>Disable All Groups</dt>
<dd>makes all groups inactive, including any hidden groups.</dd>
</dl>
-<p> </p>
-<!-- remove if more text is added below here --><!-- remove if more text is added below here -->
projects / ardour-manual-diverged / commitdiff
