From: Jörn Nettingsmeier
+ Ardour offers three track types depending on the type of
+ data they contain, and differentiates between three track modes,
+ depending on their recording behaviour.
+ 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. 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:
+ An Ardour track can be of type audio or MIDI,
+ depending on the data that the track will primarily record
+ and play back. However, 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.
+
+ 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:
+
+ If you add an instrument plugin, the MIDI track outputs audio instead
+ of MIDI data.
+ Audio tracks in Ardour can have a "mode" which affects how they behave when recording.
+ Audio tracks in Ardour have a mode which affects how they behave
+ when recording:
+ 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.
+ The screenshot on the right shows the subtle difference between an overdub
+ in normal mode (upper track) and one in non-layered mode
+ (lower track). Both tracks were created using identical audio data. 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 Add Tracks dialog allows you to select "Mono", "Stereo" and few other typical configurations. 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? If you are using Ardour's default mode of automatically connecting track (and bus) inputs and outputs, then the designation "Mono" or "Stereo" refers to the input of the track. A Mono track will have a single input and a Stereo track will have two inputs. The number of outputs for each will be determined by the number of inputs of the master bus, 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. 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.
+ 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
+ Add Tracks dialog allows you to
+ select "Mono", "Stereo" and few other typical multichannel presets
+ 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 master bus,
+ to which the track outputs will be connected.
+ If you you set Edit > Preferences > Audio
+ > Connection of Tracks and Busses to manual, 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.
+ A track or bus can be added to a session in various ways: 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). 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. These options are:
+ 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.
+ 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). 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!
+ 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).
+
+ To remove tracks and busses, select them, right-click and choose Remove
+ from the menu. A warning dialog will pop up, as track removal cannot be undone;
+ use this option with care!
+
+ Tracks are selected by clicking on the Track header at the left
+ of the Editor window. You can select multiple tracks with Left clicks, or a range of consecutive tracks with Left.
+
+ By default, selecting regions has no impact on
+ track selection.
+ 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).
+
+ In some workflows, and particularly if you have experience with
+ other DAWs, 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.
+
+ To control this behaviour, set Edit >
+ Preferences > Editor > Link selection of regions and tracks.
+ Ardour offers many options for controlling the specific appearance of tracks, including color, height, waveform style and more. These can all be found via
+ Ardour offers many options for controlling the appearance of tracks,
+ including color, height, waveform style and more.
+ These can all be found in the Edit > Preferences >
+ Editor menu.
+ 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. 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. Here is an image of a track with a rather drastic overdub/overlap situation, viewed in normal "overlaid" mode: To change this display, right click on the track header, and you'll see this menu: 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: 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.Data Type
-Track types
+
-
Track Modes
-
-
-
+ The upper track shows a new region which has been layered on
+ top of the the existing (longer) region. You can see this if you look
+ carefully at the region name strips.
+ 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.
+Channel Configuration
-What does Mono or Stereo actually mean?
-
+ The name of the preset describes the number of input channels
+ of the track or bus.
+
+ 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.
+Adding and removing tracks
+
-
-
-
+
-Removing Tracks and Busses
+Global Options
-Edit > Preferences > Editor
-
-
+
-
-
-
-
+ Ardour allows arbitrary layering of regions — you can + have as many regions you wish at a given position. By default, the regions are + overlaid in the editor window, to save vertical space. +
++ 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 + takes 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. +
++ Here is an image of a track with a rather drastic overdub situation, + viewed in normal overlaid mode: +
+ ++ To change this display, right click on the track header, and you'll see + the menu displayed above. There are two choices for layers. overlaid is currently selected. Click on stacked and the track display changes to this: +
+ ++ 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 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. +
diff --git a/_manual/10_working-with-tracks/04_controlling-track-appearance/02_track-coloring.html b/_manual/10_working-with-tracks/04_controlling-track-appearance/02_track-coloring.html index 1657e28..867adde 100644 --- a/_manual/10_working-with-tracks/04_controlling-track-appearance/02_track-coloring.html +++ b/_manual/10_working-with-tracks/04_controlling-track-appearance/02_track-coloring.html @@ -1,17 +1,39 @@ --- layout: default -title: Track Coloring +title: Track Color --- ++ 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. +
++ Select the tracks whose color you wish to change. Context-click + on the track header of one of them. From the context menu, select + Color and pick a hue to your taste in the + color dialog. Every selected track will be + re-colored. +
++ 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. +
- -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.
-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 color dialog 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.
-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.
-Tracks that belong to a track/bus group can share the color of the group by enabling the Color
option for the group.
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.
-You can also explicitly change the group color by context-clicking on the group tab, selecting Edit Group...
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.
+ Tracks that belong to a + track/bus group + can share a common color by enabling the Color option for the group. With this enabled, + any color change will be propagated to all group members. +
++ You can also explicitly change the group color by context-clicking + on the group tab in the Mixer, selecting Edit + Group... and then clicking on the Color selector in that dialog + that is displayed. +
diff --git a/_manual/10_working-with-tracks/04_controlling-track-appearance/03_track-height.html b/_manual/10_working-with-tracks/04_controlling-track-appearance/03_track-height.html index 3a988b6..227fc28 100644 --- a/_manual/10_working-with-tracks/04_controlling-track-appearance/03_track-height.html +++ b/_manual/10_working-with-tracks/04_controlling-track-appearance/03_track-height.html @@ -3,15 +3,36 @@ layout: default title: Track Height --- - - -Context click (right click) on the track header to select a track and display a context menu that includes the Height
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.
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. Left-click-drag to dynamically resize all the selected tracks.
- ++ 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 + height may be configured individually for each track in + the editor window. +
++ A context click on a track header will display the + Height menu, and allow you to choose from a + list of standard sizes. All selected tracks will be redrawn using that + height. +
++ 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. Left-drag to + dynamically resize all selected tracks. +
Select the tracks you wish to display in the Editor window. Choose Track > Height > Fit Selected Tracks
(or use the keyboard shortcut, f). Ardour ajusts the track heights and track view so that the selected tracks completely fill the vertical space available.
You can use Visual Undo
(default shortcut: Shift-Z to undo this operation.
+ Select the tracks you wish to display in the Editor window. + Choose Track > Height > Fit Selected Tracks + or use the keyboard shortcut, f. 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. +
++ You can use Visual Undo (default shortcut: Z + to revert this operation. +
diff --git a/_manual/10_working-with-tracks/05_controlling-track-ordering.html b/_manual/10_working-with-tracks/05_controlling-track-ordering.html index ef8bb02..b58688f 100644 --- a/_manual/10_working-with-tracks/05_controlling-track-ordering.html +++ b/_manual/10_working-with-tracks/05_controlling-track-ordering.html @@ -3,48 +3,23 @@ layout: default title: Controlling Track Ordering --- - - -Ardour does not impose any particular ordering of tracks and busses in either the editor or mixer windows. The default arrangement is as follows:
- -The ordering within the editor and mixer windows is synchronized: if you reorder in one window, the ordering in the other window will change.
- -Select the tracks you want to move. Then use Track > Move Selected Tracks Up
(â) or Track > Move Selected Tracks Down
(â) to move the selected track(s) up or down in the editor window.
Make the Editor Lists visible. Select the Tracks & Busses
tab. In the Tracks & Busses side panel, you can freely drag-and-drop tracks and busses into any order you prefer.
Within the "Strips" pane (Mixer window, top left), you can freely drag-and-drop tracks and busses into any order you prefer.
- -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".
- -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.
-- +Because new tracks are automatically selected, you can quickly reorder them in the editor window via the keyboard (see above).
+ Ardour does not impose any particular ordering of tracks and busses in + either the editor or mixer windows. The default arrangements are as follows: +
++ In the Editor, 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. +
++ In the Mixer, 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. +
{% children %} diff --git a/_manual/10_working-with-tracks/05_controlling-track-ordering/02_track-ordering-and-remote-control-ids.html b/_manual/10_working-with-tracks/05_controlling-track-ordering/02_track-ordering-and-remote-control-ids.html index 266293f..f258326 100644 --- a/_manual/10_working-with-tracks/05_controlling-track-ordering/02_track-ordering-and-remote-control-ids.html +++ b/_manual/10_working-with-tracks/05_controlling-track-ordering/02_track-ordering-and-remote-control-ids.html @@ -2,20 +2,32 @@ layout: default title: Track Ordering and Remote Control IDs --- - - -Every track and bus in Ardour is assigned a remote control ID. When various protocols such as Mackie Control or OSC 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.
-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).
-Ardour provides 3 methods to control remote control IDs, which can be chosen via Edit > Preferences > User Interaction
:
+ Every track and bus in Ardour is assigned a remote control ID. + When a control surface 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. +
++ 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). +
++ Ardour provides two methods to control remote control IDs, which can be + chosen via Edit > Preferences > Control Surfaces + > Control surface remote ID: +
Â
- diff --git a/_manual/10_working-with-tracks/06_bus-controls.html b/_manual/10_working-with-tracks/06_bus-controls.html index b0751be..05477aa 100644 --- a/_manual/10_working-with-tracks/06_bus-controls.html +++ b/_manual/10_working-with-tracks/06_bus-controls.html @@ -3,21 +3,28 @@ layout: default title: Bus Controls --- +A typical control area or bus header is shown below:
+ - -A typical control area or "bus header" is shown below:
- -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:
++ 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: +
Â
diff --git a/_manual/10_working-with-tracks/07_audio-track-controls.html b/_manual/10_working-with-tracks/07_audio-track-controls.html index 10e0b0c..3df59ba 100644 --- a/_manual/10_working-with-tracks/07_audio-track-controls.html +++ b/_manual/10_working-with-tracks/07_audio-track-controls.html @@ -3,17 +3,26 @@ layout: default title: Audio Track Controls --- - - -A typical control area or "track header" for an audio track is shown below:
- -An audio track has the same controls as a bus, with the addition of two extras. +
+ A typical control area or track header for an audio track is + shown below: +
+ ++ An audio track has the same + controls as a bus, with the + addition of two extras.
A typical control area for a MIDI track is shown below:
- -To see the full set of MIDI track controls, as shown above, you need to increase the track height beyond the default. MIDI tracks show only a few of the control elements when when there is insufficient vertical space.
-A MIDI track has the same basic controls as an audio track, 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.
-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.
-To edit the contents of a MIDI track see Edit MIDI
+A typical MIDI track header looks like this:
+ + ++ To see the full set of MIDI track controls, you need to increase the + track height + beyond the default. MIDI tracks show only a few of the control elements + when there is insufficient vertical space. +
++ A MIDI track has the same basic + controls as an audio track, + with the addition of two extra elements. The set of buttons below the main track + controls the MIDI channel(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. +
+
+ To the right of the MIDI track controls is a representation of a piano keyboard
+ called the scroomer. 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.
+ 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.
+ clicking on the piano plays the corresponding MIDI note for reference.
+
+ To edit the contents of a MIDI track see Edit + MIDI. +
diff --git a/_manual/10_working-with-tracks/09_track-context-menu.html b/_manual/10_working-with-tracks/09_track-context-menu.html index 9db78b1..6badb70 100644 --- a/_manual/10_working-with-tracks/09_track-context-menu.html +++ b/_manual/10_working-with-tracks/09_track-context-menu.html @@ -2,45 +2,56 @@ layout: default title: Track Context Menu --- - - -Within the editor window, context-click (right-click) on either a region or empty space within a track to display the track context menu. The context menu provides easy access to many track-level operations.
-If you click on a region, the first item in the menu is the name of the region. If you click on a layered region, the next item in the menu is Choose Top
. If selected, you will see a dialog that allows you to reorder the stacking of layers at that point. See Adjusting Region Layering for more details.
The rest of the track context menu is structured as follows:
-+ Within the editor window, context-click (right-click) on either a region + or empty space within a track to display the track context menu. + The context menu provides easy access to many track-level operations. +
++ If you click on a region, the first item in the menu is the name of the + region. If you click on a + layered region, + the next item in the menu is Choose Top. If selected, + you will see a dialog that allows you to change the vertical order of layers + at that point. See Controlling Region Layering for more details. +
++ The rest of the track context menu is structured as follows: +
Â
- diff --git a/_manual/10_working-with-tracks/10_track-and-bus-groups.html b/_manual/10_working-with-tracks/10_track-and-bus-groups.html index ab5362c..223c8dd 100644 --- a/_manual/10_working-with-tracks/10_track-and-bus-groups.html +++ b/_manual/10_working-with-tracks/10_track-and-bus-groups.html @@ -3,47 +3,119 @@ layout: default title: Track and Bus Groups --- - - -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).
-You can group tracks and busses in various ways. In the editor window, a track's controls might look like these:
- -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.
++ Tracks and busses can be put into groups. 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). +
++ You can group tracks and busses in various ways. In the editor window, + a track's controls might look like these:
+ ++ 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 + adjacent tracks to a group. +
There are several ways to create groups for tracks and bussess:
++ There are several ways to create groups for tracks and bussess: +
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.
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.
Finally, the Groups tab of the Editor Lists or the Mixer Window has a plus (+) button at the bottom of the list. Click on the plus sign to create a new group.
Context-click on a group tab and select Remove Group
from the menu. Removing a group does not remove the members of a group.
You can also remove groups by selecting them in the Groups tab of the Editor Lists or Mixer Window and then pressing the "-" button at the bottom of the list.
++ Context-click on a group tab and select >Remove + Group from the menu. Removing a group does not remove + the members of a group. +
++ You can also remove groups by selecting them in the Groups tab of the + Editor Lists + or Mixer Window and then pressing the "-" button at the bottom of the list. +
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.
-Alternatively, you can also drag a group tab to add or remove tracks from the group.
++ 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. +
++ Alternatively, you can also drag a group tab to add or remove tracks from + the group. +
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.
++ 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.
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:
- ++ To edit the properties of a group, context-click on its tab and choose + Edit Groupâ¦. This opens the track/bus group dialog, + which is also used when creating new groups: +
+ +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 not affect the color of the group members unless you also enable the shared Color
property.
Following these options are a list of the things that the members of the group can share.
++ 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 + not affect the color of the group members unless you also enable the + shared Color property. +
Gain
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).
Muting
, soloing
, record enable
, active state
, colour
and monitoring
are all straightforward. They simply mean that all member tracks or busses will share the same settings in these respects.
Selection
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 Region Selection Equivalence
+ Gain 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 -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 difference of the gains remains the same). +
+
+ Muting,
+ Soloing,
+ record enable,
+ active state, colour
and monitoring
+ are all straightforward. They simply mean that all member tracks or busses will
+ share the same settings in these respects.
+
+ Selection means that if a region is selected or + deselected on one member track, corresponding + regions 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. +
Context-clicking (right-clicking) on the group tab offers a further menu of group-related actions.
+Context-clicking on the group tab offers a further menu of group-related actions.
Â
- diff --git a/source/ardour/manual/html/screenshots/add-track-or-bus.png b/source/ardour/manual/html/screenshots/add-track-or-bus.png index 4c18f70..576f91a 100644 Binary files a/source/ardour/manual/html/screenshots/add-track-or-bus.png and b/source/ardour/manual/html/screenshots/add-track-or-bus.png differ