ardour/manual
13
0
Fork 0
Code Pull Requests Releases Activity

Rephrasing more, removing an outdated page

Browse Source
This commit is contained in:
Ed Ward 2017-06-12 16:54:47 +02:00
parent da762c68fe
commit 50a4622689
7 changed files with 114 additions and 77 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

63
include/adding-tracks-busses-and-vcas.html
View File

@ -1,36 +1,60 @@
<img class="right" src="/images/add-track-or-bus.png" alt="the add-track dialog" />
<p>A track, bus or VCA can be added to a session in various ways:</p>
<figure class="right">
<img src="/images/add-track-or-bus.png" alt="the add-track dialog">
<figcaption>
The Add Track/Bus/VCA dialog.
</figcaption>
</figure>
<p>
A track, bus or VCA can be added to a session by either:
</p>
<ul>
<li>Choose <kbd class="menu">Track &gt; Add Track, Bus or VCA&hellip;</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>
<li>Choosing <kbd class="menu">Track &gt; Add Track, Bus or VCA&hellip;</kbd>.</li>
<li><kbd class="mouse">Right</kbd>-clicking in an empty part of the track controls area.</li>
<li>Clicking the <kbd class="menu">Plus (&plus;)</kbd> button underneath the list of tracks in the mixer.</li>
</ul>
<p>
Any of these actions will open the Add Track/Bus/VCA dialog.
</p>
<table class="dl">
<tr><th>Add</th>
<td>Here you can select the number of tracks, busses or VCAs you wish to create, and
their <a href="@@track-types">types</a>.</td></tr>
<td>Selects the number of tracks, busses or VCAs to create, and their <a
href="@@track-types">types</a>.</td></tr>
<tr><th>Name</th>
<td>Defines the name of the new track(s). If multiple tracks are created, or if a track with the same name already exists, a space and number will be happened at the end (e.g.: Audio 1, Audio 2&hellip;)</td></tr>
<td>Defines the name of the new track(s). If multiple tracks are created, or if
a track with the same name already exists, a space and number will be happened
at the end (e.g.: Audio 1, Audio 2&hellip;)</td></tr>
<tr><th>Configuration</th>
<td>This menu lets you choose from a number of route templates, which determine the number of input ports and optionally contain plugins and other mixer strip configuration. The most common choices here are <em>mono</em> and <em>stereo</em>.</td></tr>
<td>This menu allows to choose from a number of route templates, which determine
the number of input ports and optionally contain plugins and other mixer strip
configuration. The most common choices here are <em>mono</em> and
<em>stereo</em>.</td></tr>
<tr><th>Record mode</th>
<td>This option is only available for audio tracks and affects how it behaves when recording. See <a href="@@track-types#trackmodes">Track Modes</a> for details.</td></tr>
<td>This option is only available for audio tracks and affects how it behaves
when recording. See <a href="@@track-types#trackmodes">Track Modes</a> for
details.</td></tr>
<tr><th>Instrument</th>
<td>This option is only available for MIDI tracks and busses and lets you select a
default instrument from the list of available plugins.</td></tr>
<td>This option is only available for MIDI tracks and busses and allows the
selection of a default instrument from the list of available plugins.</td></tr>
<tr><th>Group</th>
<td>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.</td></tr>
record enable, or editing, for example). This option assigns the new track/bus
to an existing group, or create a new group.</td></tr>
<tr><th>Insert</th>
<td>Defines where in the track list is the track created. The default is <em>Last</em>, i.e. after all the tracks and busses, and can also be <em>First</em>, <em>Before Selection</em> (to place it just above the selected track) or <em>After selection</em>.</td></tr>
<td>Defines where in the track list is the track created. The default is
<em>Last</em>, i.e. after all the tracks and busses, and can also be
<em>First</em>, <em>Before Selection</em> (to place it just above the selected
track) or <em>After selection</em>.</td></tr>
<tr><th>Output Ports</th>
<td>Defines how the number of output responds to adding a plugin with a different number of outputs than the track itself. in <em>Strict I/O</em> mode, the track will only use a few of the plugins I/O and will keep its own number of output fixed, while in <em>Flexible I/O</em> mode, it will automatically adapt to the I/O of its plugins. See <a href="@@trackbus-signal-flow">Signal flow</a> to learn more about those options.</td></tr>
<td>Defines how the number of output responds to adding a plugin with a
different number of outputs than the track itself. in <em>Strict I/O</em> mode,
the track will only use a few of the plugins I/O and will keep its own number of
output fixed, while in <em>Flexible I/O</em> mode, it will automatically adapt
to the I/O of its plugins. See <a href="@@trackbus-signal-flow">Signal flow</a>
to learn more about those options.</td></tr>
</table>
<p>
@ -41,9 +65,8 @@
<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>
<dfn>Removing</dfn> tracks and busses, is done by selecting them, <kbd
class="mouse">right</kbd>-clicking and choosing <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!
this option should be used with care!
</p>

23
include/controlling-track-ordering.html
View File

@ -4,33 +4,38 @@
either the editor or mixer windows. The default arrangements are as follows:
</p>
<p>
<ul>
<li>
In the <dfn>Editor</dfn> window, 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) is never visible in the editor window.
</p>
</li>
<p>
<li>
In the <dfn>Mixer</dfn> window, 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
many other mixer strips are present. If a Monitor section is used, it shows
up at the right edge of the mixer window; it can also be torn off into a
separate window.
</p>
</li>
</ul>
<h2>Reordering Tracks</h2>
<p>
The <dfn>track ordering</dfn> of the Editor and Mixer is
<dfn>synchronized</dfn>: if you reorder in one window, the ordering in the
other window will follow.
<dfn>synchronized</dfn>: if a track is reordered in one window, the ordering
in the other window will follow.
</p>
<h3>Reordering in the Editor Window</h3>
<p>
Select the tracks to be moved, then use <kbd class="menu">Track &gt; Move Selected Tracks Up</kbd> (shortcut: <kbd class="mod1">&uarr;</kbd>) or <kbd class="menu">Track &gt; Move Selected Tracks Down</kbd> (shortcut: <kbd class="mod1">&darr;</kbd>).
Reordering is done by selecting the tracks to be moved, then using
<kbd class="menu">Track &gt; Move Selected Tracks Up</kbd> (shortcut:
<kbd class="mod1">&uarr;</kbd>) or <kbd class="menu">Track &gt; Move Selected
Tracks Down</kbd> (shortcut: <kbd class="mod1">&darr;</kbd>).
</p>
<p>
@ -52,8 +57,8 @@
<p>
Tracks and Busses that are members of a group can be reordered so that they
display contiguously within the Editor and Mixer windows. <kbd
class=mouse>Right</kbd>-click on the group tab and choose <kbd
display contiguously within the Editor and Mixer windows, by <kbd
class=mouse>Right</kbd>-clicking on the group tab and choosing <kbd
class="menu">Collect</kbd>.
</p>

11
include/select-regions.html
View File

@ -14,13 +14,15 @@
propagated to other tracks.
</p>
<h2>Region Selection and Track Selection</h2>
<h2>Track Selection</h2>
<p>
Please read <a href="@@selecting-tracks">Region &amp; Track Selection</a>
for more information on how selecting regions and selecting tracks interact.
Tracks are <dfn>selected</dfn> by clicking on the Track header at the left
of the Editor window. Multiple tracks can be selected with <kbd class="mod1
mouse">Left</kbd> clicks, or a range of consecutive tracks with <kbd
class="mod3 mouse">Left</kbd>.
</p>
<h2>Selecting a Region</h2>
<h2>Region Selection</h2>
<p>
Using the <a href="@@toolbox">Grab Mode tool</a>, <kbd class="mouse">left</kbd>
clicking on a region selects it. If <a href="@@toolbox">Smart mode</a> is
@ -72,4 +74,3 @@
selects it. This will do nothing for whole-file regions, since they do not exist
anywhere in a playlist or track.
</p>

14
include/selecting-tracks.html
View File

@ -1,22 +1,27 @@
<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
of the Editor window. Multiple tracks can be selected 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
A track can be selected, then 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 class="fixme">
Is it still true ?
</p>
<p>
In some workflows, and particularly if you have experience with
In some workflows, and particularly in comparison 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
@ -28,3 +33,6 @@
Preferences &gt; Editor &gt; Link selection of regions and tracks</kbd>.
</p>
<p class="fixme">
This menu doesn't exist anymore
</p>

15
include/track-context-menu.html
View File

@ -1,15 +1,16 @@
<p>
Within the editor window, context-clicking (<kbd class="mouse">right</kbd> click) on either a region
or empty space within a track displays the <dfn>track context menu</dfn>.
The context menu provides easy access to many track-level operations.
Within the editor window, context-clicking (<kbd class="mouse">right</kbd>
click) on either a region or empty space within a track displays the <dfn>track
context menu</dfn>. The context menu provides easy access to many track-level
operations.
</p>
<p>
If a <dfn>region</dfn> is clicked, the first item in the menu is the name of the
region. If a <a href="@@layering-display">layered region</a> is clicked,
If a <dfn>region</dfn> is clicked, the first item in the menu is the name of
the region. If a <a href="@@layering-display">layered region</a> is clicked,
the next item in the menu is <kbd class="menu">Choose Top</kbd>. If selected,
a dialog appears that allows you to change the vertical order of layers
at that point. See <a href="@@layering-display">Layering Display</a> for more details.
a dialog appears that allows to change the vertical order of layers at that
point. See <a href="@@layering-display">Layering Display</a> for more details.
</p>
<p>
The rest of the track context menu is structured as follows:

57
include/track-types.html
View File

@ -16,9 +16,8 @@
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:
Nevertheless, when adding tracks to a session, its content is typically
known, and Ardour offers three choices:
</p>
<table class="dl">
<tr><th>Audio</th>
@ -34,16 +33,16 @@
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 alongside
If an instrument plugin is added, the MIDI track outputs audio alongside
MIDI data.
</p></td></tr>
<tr><th>Audio/MIDI</th>
<td>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
are another). It can be tricky to configure this type of track manually,
so Ardour allows 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.</td></tr>
MIDI tracks, and a dialog will warn of this.</td></tr>
</table>
<h2 id="trackmodes">Track Modes</h2>
@ -69,8 +68,8 @@
</td></tr>
<tr><th>Tape</th>
<td><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&mdash;there is no
all data is recorded to a single file and if a section of
existing data is overdub, the existing data is destroyed irrevocably&mdash;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
@ -81,10 +80,14 @@
<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>
(lower track). Both tracks were created using identical audio data.
</p>
<p>
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>
top</dfn> of the the existing (longer) region. It can be seen by the region
name strips.
</p>
<p>
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.
@ -96,27 +99,31 @@
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="@@adding-tracks-busses-and-vcas">Add Tracks</a> dialog allows you to
select "Mono", "Stereo" and few other typical multichannel presets<br>
<a href="@@adding-tracks-busses-and-vcas">Add Tracks</a> dialog allows to
select "Mono", "Stereo" and few other typical multichannel presets
</p>
<p>
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
If Ardour is configured to automatically connect new tracks and
busses, the number of outputs will be determined by the number of
inputs of the <dfn>master <a
href="@@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
to which the track outputs will be connected.
</p>
<p>
For example, with a two-channel master bus, 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 &gt; Preferences &gt; Audio
&gt; Connection of Tracks and Busses</kbd> to <kbd
If <kbd class="menu">Edit &gt; Preferences &gt; Audio
&gt; Connection of Tracks and Busses</kbd> is set 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.
and there will be as many outputs as there are inputs. It is up to the user to connect
them as desired. This is not a particularly useful way to work unless something
fairly unusual is done with signal routing and processing. It is almost always
preferable to leave Ardour make connections automatically, even if some changes
are manually done later.
</p>

8
master-doc.txt
View File

@ -951,14 +951,6 @@ uri: working-with-tracks/adding-tracks-and-busses
part: subchapter
---
---
title: Selecting Tracks
include: selecting-tracks.html
link: selecting-tracks
uri: working-with-tracks/selecting-tracks
part: subchapter
---
---
title: Controlling Track Ordering
include: controlling-track-ordering.html