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

Correcting CSS class (modxn instead of modx), removing 'you's

Browse Source
This commit is contained in:
Ed Ward 2017-03-13 11:23:50 +01:00
parent 4424b1aa27
commit 7349ebd9e9
2 changed files with 229 additions and 81 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

216
include/audiomidi-mixer-strips.html
View File

@ -2,7 +2,9 @@
<img class="right" src="/images/mixer-1-strip-numbered.png" alt="A mixer strip">
<p>
A <dfn>mixer strip</dfn> in Ardour is a vertical view of the track, from a mixing point of view. This view is convenient to deal with I/O, effects, panning/muting, gain, etc&hellip; It has a general "top to bottom" flow.
A <dfn>mixer strip</dfn> in Ardour is a vertical view of the track, from a
mixing point of view. This view is convenient to deal with I/O, effects,
panning/muting, gain, etc&hellip; It has a general "top to bottom" flow.
</p>
<p>
@ -28,7 +30,9 @@
<h2>Headers</h2>
<p>
At the top of the window, is the <a href="@@the-track-and-bus-group-list">group tabs</a> (here, <em>recm&hellip;</em>). This allows to group tracks together for common controls.
At the top of the window, is the <a href="@@the-track-and-bus-group-list">group
tabs</a> (here, <em>recm&hellip;</em>). This allows to group tracks together for
common controls.
</p>
<p>
@ -37,18 +41,26 @@
<ul>
<li>
The double arrow button allows to shrink/expand the width of the strip. <kbd class="mod1"></kbd><kbd class="mod3"></kbd><kbd class="mouse">Click</kbd> the button will shrink/expand all the tracks at once
The double arrow button allows to shrink/expand the width of the strip. <kbd
class="mod1n"></kbd><kbd class="mod3n"></kbd><kbd class="mouse">Click</kbd> the
button will shrink/expand all the tracks at once
</li>
<li>
The color bar shows the color of the track in the editor
</li>
<li>
The <kbd class="menu">X</kbd> button toggles the visibility of the track OFF. To turn it back ON, one can either go to the <a href="@@the-tracks-and-busses-list">Tracks and Busses list</a> in the Editor view and check the "V" column on the track's line or stay in the Mixer view and check the <kbd class="menu">Show</kbd> column of this strip in the <a href="@@strips-list">Strips list</a>.
The <kbd class="menu">X</kbd> button toggles the visibility of the track OFF. To
turn it back ON, one can either go to the <a
href="@@the-tracks-and-busses-list">Tracks and Busses list</a> in the Editor
view and check the "V" column on the track's line or stay in the Mixer view and
check the <kbd class="menu">Show</kbd> column of this strip in the <a
href="@@strips-list">Strips list</a>.
</li>
</ul>
<p>
<kbd class="mouse">Right</kbd> clicking on the color bar will bring up a context menu, which is exactly the same as clicking on the Track name button.
<kbd class="mouse">Right</kbd> clicking on the color bar will bring up a context
menu, which is exactly the same as clicking on the Track name button.
</p>
<h2>Track Name</h2>
@ -59,71 +71,113 @@
<dl>
<dt>Color&hellip;</dt><dd>Changes the strip/track color</dd>
<dt>Comments&hellip;</dt><dd>Shows an editor to put comments about the track, see below the Comments button</dd>
<dt>Comments&hellip;</dt><dd>Shows an editor to put comments about the track,
see below the Comments button</dd>
<dt>Inputs&hellip;</dt><dd>Shows the Routing grid for the inputs of the track</dd>
<dt>Outputs&hellip;</dt><dd>Shows the Routing grid for the outputs of the track</dd>
<dt>Save As Template&hellip;</dt><dd>Allows to save the track without its media content (I/O, effects,&hellip;) for later reuse</dd>
<dt>Rename&hellip;</dt><dd>Changes the name of the track (effective both in the Mixer and the Editor)</dd>
<dt><kbd class="option"></kbd>Active</dt><dd>Select the active status of the track. An inactive track won't output any sound</dd>
<dt><kbd class="option"></kbd>Strict I/O</dt><dd>While in <a href="@@trackbus-signal-flow">patchbayStrict I/O</a> mode, a track <em>always</em> has as many output as it has inputs, regardless of the effects. When disabled, a stereo effect put on a mono track will result in a stereo output for the strip.</dd>
<dt>Pin Connections&hellip;</dt><dd>Shows the <kbd class="menu">Pin Configuration</kbd> window, that shows (and allows to modify) all the signal flows inside the track</dd>
<dt>Adjust Latency&hellip;</dt><dd>Shows the <kbd class="menu">Track Latency</kbd> dialog, that allows fine-tune the latency to the track, in samples, msec or period</dd>
<dt><kbd class="option"></kbd>Protect Against Denormals</dt><dd>Uses a trick to get rid of <em>denormals</em>, which are very small numbers the CPU can have a hard time dealing with. To be used if the CPU consumption for plugins is noticeably higher than expected</dd>
<dt>Duplicate&hellip;</dt><dd>Copies the track to a new one, optionnaly with its playlist</dd>
<dt>Save As Template&hellip;</dt><dd>Allows to save the track without its media
content (I/O, effects,&hellip;) for later reuse</dd>
<dt>Rename&hellip;</dt><dd>Changes the name of the track (effective both in the
Mixer and the Editor)</dd>
<dt><kbd class="option">Active</kbd></dt><dd>Select the active status of the track.
An inactive track won't output any sound</dd>
<dt><kbd class="option">Strict I/O</kbd></dt><dd>While in <a href="@@trackbus-signal-flow">
patchbayStrict I/O</a> mode, a track <em>always</em> has as many output as it
has inputs, regardless of the effects. When disabled, a stereo effect put on
a mono track will result in a stereo output for the strip.</dd>
<dt>Pin Connections&hellip;</dt><dd>Shows the <kbd class="menu">Pin Configuration</kbd>
window, that shows (and allows to modify) all the signal flows inside the track</dd>
<dt>Adjust Latency&hellip;</dt><dd>Shows the <kbd class="menu">Track Latency</kbd>
dialog, that allows fine-tune the latency to the track, in samples, msec or period</dd>
<dt><kbd class="option">Protect Against Denormals</kbd></dt><dd>Uses a trick to
get rid of <em>denormals</em>, which are very small numbers the CPU can have
a hard time dealing with. To be used if the CPU consumption for plugins is
noticeably higher than expected</dd>
<dt>Duplicate&hellip;</dt><dd>Copies the track to a new one, optionnaly with
its playlist</dd>
<dt>Remove</dt><dd>Deletes the track and its playlist</dd>
</dl>
<h2>Inputs</h2>
<p>
The dropdown button shows the current input port(s), i.e. what's plugged to the "in" of the track. By default, each audio track is connected to the system inputs, ready for recording, as shown by the number(s). Clicking the dropdown Inputs button will allow to change the inputs, through a menu:
The dropdown button shows the current input port(s), i.e. what's plugged to the
"in" of the track. By default, each audio track is connected to the system
inputs, ready for recording, as shown by the number(s). Clicking the dropdown
Inputs button will allow to change the inputs, through a menu:
</p>
<dl>
<dt>Disconnect</dt><dd>Disconnects everything, i.e. the track has no input</dd>
<dt>In <em>n</em></dt><dd>Those are the system inputs, e.g. to record from the soundcard. A mono track will have <em>In 1</em> and <em>In 2</em> separated, while a stereo track can have <em>In 1+2</em></dd>
<dt><em>Track n output</em></dt><dd>All the outputs of compatible tracks, e.g., a mono track can only receive a mono signal, a MIDI track can only receive MIDI signal, &hellip;</dd>
<dt>Add Audio Port</dt><dd>Adds an audio input to the track, i.e. a mono audio track becomes a stero one</dd>
<dt>Add MIDI Port</dt><dd>Adds a MIDI input to the track. Adding it to an audio track makes it a mixed Audio/MIDI track. This can be usefull e.g. to feed some plugins with a MIDI signal to control the audio, like a vocoder</dd>
<dt>Routing Grid</dt><dd>Shows the <a href="@@patchbay"><kbd class="menu">Routing Grid</kbd> window</a>, which allows for more complex input configuration</dd>
<dt>In <em>n</em></dt><dd>Those are the system inputs, e.g. to record from the
soundcard. A mono track will have <em>In 1</em> and <em>In 2</em> separated,
while a stereo track can have <em>In 1+2</em></dd>
<dt><em>Track n output</em></dt><dd>All the outputs of compatible tracks, e.g.,
a mono track can only receive a mono signal, a MIDI track can only receive MIDI
signal, &hellip;</dd>
<dt>Add Audio Port</dt><dd>Adds an audio input to the track, i.e. a mono audio
track becomes a stero one</dd>
<dt>Add MIDI Port</dt><dd>Adds a MIDI input to the track. Adding it to an audio
track makes it a mixed Audio/MIDI track. This can be usefull e.g. to feed some
plugins with a MIDI signal to control the audio, like a vocoder</dd>
<dt>Routing Grid</dt><dd>Shows the <a href="@@patchbay"><kbd class="menu">Routing
Grid</kbd> window</a>, which allows for more complex input configuration</dd>
</dl>
<p>
The <kbd class="menu">Routing Grid</kbd> can also be shown by right clicking the dropdown Inputs button. It allows to make the connections through a matrix, and connect things that are not listed in the menu above, or connect to multiple sources at once, reduce the number of inputs, etc&hellip;
The <kbd class="menu">Routing Grid</kbd> can also be shown by right clicking the
dropdown Inputs button. It allows to make the connections through a matrix, and
connect things that are not listed in the menu above, or connect to multiple
sources at once, reduce the number of inputs, etc&hellip;
</p>
<p>
On audio tracks, is a Trim knob, as on traditional consoles. It set the base input level for the track, avoiding any clipping. Notice that it trims both any input, but (when playing back), also the level of the playlist as displayed in the Editor. It makes sense as while playing, the input of the track is the playlist, on which the mixer strip acts.
On audio tracks, is a Trim knob, as on traditional consoles. It set the base
input level for the track, avoiding any clipping. Notice that it trims both any
input, but (when playing back), also the level of the playlist as displayed in
the Editor. It makes sense as while playing, the input of the track is the
playlist, on which the mixer strip acts.
</p>
<p>
On midi tracks, it is replaced by a MIDI Input button, that allows/disallows MIDI input on the track.
On midi tracks, it is replaced by a MIDI Input button, that allows/disallows
MIDI input on the track.
</p>
<h2>Polarity</h2>
<p>
On audio tracks only, the Polarity button(s), 1 per input, allow to reverse the signal, i.e. a negative value will be positive and vice-versa. This can help deal with phasing issues.
On audio tracks only, the Polarity button(s), 1 per input, allow to reverse
the signal, i.e. a negative value will be positive and vice-versa. This can help
deal with phasing issues.
</p>
<h2>Processor box</h2>
<p>
The processor box is where the effects are added. By default, one effect is always present: the Fader (see below). The effects can be added <em>pre</em>-fader and appear in brown, or <em>post</em>-fader, where they will appear in dark green. The signal flow is represented by lines, red for the MIDI and green for the audio.
The processor box is where the effects are added. By default, one effect is
always present: the Fader (see below). The effects can be added
<em>pre</em>-fader and appear in brown, or <em>post</em>-fader, where they will
appear in dark green. The signal flow is represented by lines, red for the MIDI
and green for the audio.
</p>
<p>
It is also where the <a href="@@aux-sends">Sends</a> come from, wether external or auxiliary.
It is also where the <a href="@@aux-sends">Sends</a> come from, wether
external or auxiliary.
</p>
<p>
To learn more about the processor box, see <a href="@@processor-box">The Processor Box</a>.
To learn more about the processor box, see <a href="@@processor-box">The
Processor Box</a>.
</p>
<h2>Panner</h2>
<p>
The <dfn>Panner</dfn> visually displays how the sound will be distributed between the different outputs. They'll look and behave differently if the track is mono, stereo, or has multiple channels.
The <dfn>Panner</dfn> visually displays how the sound will be distributed
between the different outputs. They'll look and behave differently if the
track is mono, stereo, or has multiple channels.
</p>
<p>
@ -131,37 +185,53 @@
</p>
<dl>
<dt><kbd class="option"></kbd>Bypass</dt><dd>When checked, the panner is grayed, and the signal is not affected by it</dd>
<dt>Reset</dt><dd>Resets the panner to its default settings, e.g. for a mono signal, it is centered</dd>
<dt>Edit&hellip;</dt><dd>Shows a <kbd class="menu">Panner</kbd> dialog, which allows for fine tuning of the panner</dd>
<dt><kbd class="option">Bypass</kbd></dt><dd>When checked, the panner is grayed,
and the signal is not affected by it</dd>
<dt>Reset</dt><dd>Resets the panner to its default settings, e.g. for a mono
signal, it is centered</dd>
<dt>Edit&hellip;</dt><dd>Shows a <kbd class="menu">Panner</kbd> dialog, which
allows for fine tuning of the panner</dd>
</dl>
<p>
See <a href="@@panning">Panning</a> to learn more about how to control the panner, and what kind of panners are available inside Ardour.
See <a href="@@panning">Panning</a> to learn more about how to control the panner,
and what kind of panners are available inside Ardour.
</p>
<h2>Recording options</h2>
<p>
The most noticeable button here is the Record Enable one, with a red circle. When enabled, next time the Global record will be armed and playback started, everything that comes from the input of the track will be recorded. Right clicking a disabled record button allows to enable <kbd class="menu">Rec-Safe</kbd>, thus protecting the track against accidental recording.
The most noticeable button here is the Record Enable one, with a red circle.
When enabled, next time the Global record will be armed and playback started,
everything that comes from the input of the track will be recorded. Right clicking
a disabled record button allows to enable <kbd class="menu">Rec-Safe</kbd>,
thus protecting the track against accidental recording.
</p>
<p>
The buttons on the right, <kbd class="menu">In</kbd> and <kbd class="menu">Disk</kbd>, show what the user is listening to by lighting up, between the <em>In</em>put and the actual content of the playlist on <em>Disk</em>.
The buttons on the right, <kbd class="menu">In</kbd> and <kbd
class="menu">Disk</kbd>, show what the user is listening to by lighting up,
between the <em>In</em>put and the actual content of the playlist on
<em>Disk</em>.
</p>
<p>
They also allow to override the automatic switching by pressing them to lock one source or the other to be what the user is hearing.
They also allow to override the automatic switching by pressing them to lock
one source or the other to be what the user is hearing.
</p>
<h2>Mute/Solo</h2>
<p>
These buttons allow to Mute (or silence) the track, or Solo them, shutting down the gain of the other tracks (totally by default, can be set to partially in the options). See <a href="@@muting-and-soloing">Muting and Soloing</a> for more information.
These buttons allow to Mute (or silence) the track, or Solo them, shutting
down the gain of the other tracks (totally by default, can be set to partially
in the options). See <a href="@@muting-and-soloing">Muting and Soloing</a> for
more information.
</p>
<p>
Notice that by default, Solo overrides Mute, i.e. if a track is both Soloed and Muted, it will play. That can be changed in the preferences.
Notice that by default, Solo overrides Mute, i.e. if a track is both Soloed and
Muted, it will play. That can be changed in the preferences.
</p>
<p>
@ -169,36 +239,58 @@
</p>
<ul>
<li>Solo Isolate, as the name suggests, isolates tracks or busses from the solo system. When tracks or busses are soloed the isolated ones will not mute.</li>
<li>Solo Lock locks the solo into its current state (ie solo on or solo off). It will not allow the solo state to be changed until the lock is released.</li>
<li>Solo Isolate, as the name suggests, isolates tracks or busses from the solo
system. When tracks or busses are soloed the isolated ones will not mute.</li>
<li>Solo Lock locks the solo into its current state (ie solo on or solo off).
It will not allow the solo state to be changed until the lock is released.</li>
</ul>
<h2>Gain &amp; Meter</h2>
<p>
On the right of this part is a <a href="@@metering-in-ardour">Meter</a>, displaying the level of the track's output after the fader. In can be set to display the signal at any point, see below <em>Metering Point</em>. Right clicking this meter shows a menu allowing to switch the meter type.
On the right of this part is a <a href="@@metering-in-ardour">Meter</a>,
displaying the level of the track's output after the fader. In can be set to
display the signal at any point, see below <em>Metering Point</em>. Right
clicking this meter shows a menu allowing to switch the meter type.
</p>
<p>
The big Gain slider on the left allows to change the gain of the track. Its default O dB value is reminded with a white horizontal line, and its precise value is shown in a text field above it, that doubles as a way to type in a numeric value.
The big Gain slider on the left allows to change the gain of the track. Its
default OdB value is reminded with a white horizontal line, and its precise
value is shown in a text field above it, that doubles as a way to type in a
numeric value.
</p>
<p>
The text field above the meter shows the "Peak", i.e. the mawimum value that has been reached during playback. To avoid distortion, the value should stay below O dB, and if it goes above this value, the text field will turn red. Clicking on this field will reset the Peak value (for a new measurement or a new part of the track).
The text field above the meter shows the "Peak", i.e. the mawimum value that has
been reached during playback. To avoid distortion, the value should stay below OdB,
and if it goes above this value, the text field will turn red. Clicking on
this field will reset the Peak value (for a new measurement or a new part of the
track).
</p>
<p class="note">
Notice that if any gain automation has been set and the automation state is set on "Play" (see below), then the Gain fader is driven by the automation, and not by the user. The Gain fader will turn grey to show it's inactive.
Notice that if any gain automation has been set and the
automation state is set on "Play" (see below), then the Gain fader is driven by
the automation, and not by the user. The Gain fader will turn grey to show it's
inactive.
</p>
<h2>Control master</h2>
<h2>VCAs</h2>
<p>
If at least one control master exists, this button will show up, allowing the user to link this track to any control master.
If at least one <a href="@@control-masters-mixer-strips">VCA</a> exists, this
button will show up, allowing the user to link this track to any control master.
</p>
<p>
Clicking the button lists all the available control masters, and a menu option to <kbd class="menu">Unassign all</kbd>. Notice that a track can have be a slave to as many control masters as they are in the session, hence multiplying the number of C.M. buttons. The displayed number is the number of the Control Master, not the count of C.M. linked to the track. A track with no control master assigned will show a unique button with a "<kbd class="menu">-vca-</kbd>" label instead of this number.
Clicking the button lists all the available control masters, and a menu option
to <kbd class="menu">Unassign all</kbd>. Notice that a track can have be a slave
to as many VCAs as they are in the session, hence multiplying the number
of VCA buttons. The displayed number is the number of the VCA,
not the count of VCAs linked to the track. A track with no VCA assigned
will show a unique button with a "<kbd class="menu">-vca-</kbd>" label instead
of this number.
</p>
<h2>Fader automation/mix group/metering point</h2>
@ -210,22 +302,31 @@
</p>
<dl>
<dt>Manual</dt><dd><em>(default)</em> The playback won't use the fader automation data</dd>
<dt>Manual</dt><dd><em>(default)</em> The playback won't use the fader automation
data</dd>
<dt>Play</dt><dd>Enables playback/use of fader automation data</dd>
<dt>Write</dt><dd>While the transport is rolling, all fader changes will be recorded to the fader automation lane</dd>
<dt>Touch</dt><dd>While the transport is rolling, touching the fader will initiate recording all fader changes until the fader is released. When the fader is not being touched, existing automation data will be played/used to control the gain level.</dd>
<dt>Write</dt><dd>While the transport is rolling, all fader changes will be
recorded to the fader automation lane</dd>
<dt>Touch</dt><dd>While the transport is rolling, touching the fader will initiate
recording all fader changes until the fader is released. When the fader is not
being touched, existing automation data will be played/used to control the gain
level.</dd>
</dl>
<h3>Mix group</h3>
<p>
This button displays the mix group information as does the tab in the header (see above). It is convenient though, as it allows to quickly switch the track from one group to another with a drop down menu, also allowing to affect the track to a non-adjascent group (which the tab won't easily allow).
This button displays the mix group information as does the tab in the header
(see above). It is convenient though, as it allows to quickly switch the track
from one group to another with a drop down menu, also allowing to affect the
track to a non-adjascent group (which the tab won't easily allow).
</p>
<h3>Metering Point</h3>
<p>
The metering displayed in the meter is by default is 'Post', i.e. Post fader. It can be changed with this button to Any point of the signal flow:
The metering displayed in the meter is by default is 'Post', i.e. Post fader.
It can be changed with this button to Any point of the signal flow:
</p>
<dl>
@ -233,18 +334,23 @@
<dt>Pre</dt><dd>Pre-fader</dd>
<dt>Post</dt><dd>Post-fader</dd>
<dt>Out</dt><dd>The output of the track</dd>
<dt>Custom</dt><dd>A <em>Meter</em> processor is added to the processor box an can be set anywhere (by dragging and dropping) to probe the signal flow at that pointat the point</dd>
<dt>Custom</dt><dd>A <em>Meter</em> processor is added to the processor box and
can be set anywhere (by dragging and dropping) to probe the signal flow at
that point</dd>
</dl>
<h2>Output(s)</h2>
<p>
This button is exactly the same as the <em>Input</em> button, but applies to the <em>output</em> of the track.
This button is exactly the same as the <em>Input</em> button, but applies to
the <em>output</em> of the track.
</p>
<h2>Comments</h2>
<p>
This buttons open up a little text editor, that can be used to add some written notes to the track, as e.g. a particular setting. The button's caption is replaced by the beginning of the text, so it can be used as a "sub" name for the track.
This buttons open up a little text editor, that can be used to add some
written notes to the track, as e.g. a particular setting. The button's caption
is replaced by the beginning of the text, so it can be used as a "sub" name for
the track.
</p>

94
include/grid-controls.html
View File

@ -2,17 +2,26 @@
<img class="left" src="/images/toolbar-grid.png" alt="Editor toolbar's grid">
<p>
Ardour's editor utilizes a <dfn>grid</dfn> to assist in the placement of regions on the timeline, or with editing functions that need to happen at a specific point in time. You can choose if you want the cursor and various objects to snap to this grid, and how you want the snapping to behave. You can modify the grid units to fit your needs.
Ardour's editor utilizes a <dfn>grid</dfn> to assist in the placement of regions
on the timeline, or with editing functions that need to happen at a specific
point in time. This <dfn>snapping</dfn> of the cursor and various objects to the
grid can be toggled on or off, as does its behaviour, and grid units.
</p>
<h2>About Snapping</h2>
<p>
There are two ways to think about aligning material to a grid. The first and most obvious one is where an object's position is clamped to grid lines. In Ardour, this is called <dfn>absolute snap</dfn> and is commonly used when working with sampled material where audio begins exactly at the beginning of a file, note or region.
There are two ways to think about aligning material to a grid. The first and
most obvious one is where an object's position is clamped to grid lines. In
Ardour, this is called <dfn>absolute snap</dfn> and is commonly used when
working with sampled material where audio begins exactly at the beginning of a
file, note or region.
</p>
<p>
The second, <dfn>relative snap</dfn>, is used when an object's position relative to the grid lines is important. In music, this allows you to move objects around without changing the "feel" (or timing) of a performance.
The second, <dfn>relative snap</dfn>, is used when an object's position relative
to the grid lines is important. In music, this allows to move objects around
without changing the "feel" (or timing) of a performance.
</p>
<p>
@ -20,60 +29,87 @@
</p>
<p>
While dragging objects you may switch from absolute to relative snap by pressing the absolute snap modifier key(s).
While dragging objects, pressing the absolute snap modifier key(s) switches
from absolute to relative snap.
</p>
<p>
You may also disable snap entirely by using the snap modifier (see below).
The snap can also be entirely disabled by using the snap modifier (see below).
</p>
<p>
Note that in relative snap mode the reference point is taken to be the distance to the nearest grid line.
Note that in relative snap mode the reference point is taken to be the distance
to the nearest grid line.
</p>
<p>
Note also that when an object lies exactly on a grid line, there will be no difference between relative and absolute snap modes.
Note also that when an object lies exactly on a grid line, there will be no
difference between relative and absolute snap modes.
</p>
<p>
The realtive snap and snap modifiers (along with other modifier keys) may be set in <kbd class="menu">Edit &gt; Preferences &gt; User Interaction</kbd>
The realtive snap and snap modifiers (along with other modifier keys) may be set
in <kbd class="menu">Edit &gt; Preferences &gt; User Interaction</kbd>
</p>
<p>
For common use patterns, it is recommended that you assign a unique key for one snap modifier and two keys for the other in such a way that they share an otherwise unused key. For example, you may choose the snap modifier to be the <kbd class="mod2">&nbsp;</kbd> key and the relative snap modifier to be the <kbd class="mod2">&nbsp;</kbd> and <kbd class="mod4">&nbsp;</kbd> keys.
For common use patterns, it is recommended to assign a unique key for one
snap modifier and two keys for the other in such a way that they share an
otherwise unused key. For example, the snap modifier may be chosen to be the
<kbd class="mod2n"></kbd> key and the relative snap modifier to be the <kbd
class="mod2n"></kbd> and <kbd class="mod4n"></kbd> keys.
</p>.
<h2>Snap Modes</h2>
<p>
Using the above modifications, Ardour supports three different modes of snapping to the grid:
Using the above modifications, Ardour supports three different modes of snapping
to the grid:
</p>
<dl class="wide-table">
<dt><kbd class="menu">No Grid</kbd></dt>
<dd>disables the grid. All objects move freely in this mode.</br>
In <kbd class="menu">No Grid</kbd> mode, you may temporarily activate the grid by pressing the snap modifier (for absolute snap) or switch to relative snap by pressing the relative snap modifier.</dd>
<dd>disables the grid. All objects move freely in this mode.</br>
In <kbd class="menu">No Grid</kbd> mode, the grid may be temporarily activated
by pressing the snap modifier (for absolute snap) or switch to relative snap
by pressing the relative snap modifier.</dd>
<dt><kbd class="menu">Grid</kbd></dt>
<dd>activates normal snapping. All positions of objects snap to the grid. (See <a href="#gridunits">Grid Units</a> below to change the grid). If you try to move an object in "Grid"-mode, it does not change its position until you move the mouse far enough for the object to reach the next grid line.</br>
Sometimes you may wish to maintain an objects' position relative to the grid line. In order to do this, use the "snap relative" modifier. When holding down this modifier during a drag, the dragged object will jump while maintaining its original distance from the line.</br>
New objects will always be created at grid points.</br>
Holding down the snap modifier will disable the current grid setting and allow you to move the object freely.</br>
</dd>
<dd>activates normal snapping. All positions of objects snap to the grid. (See
<a href="#gridunits">Grid Units</a> below to change the grid).
Moving an object in "Grid"-mode, does not change its position until
the mouse is far enough for the object to reach the next grid line.</br>
To maintain an objects' position relative to the grid line, the "snap relative"
modifier can be used. When holding down this
modifier during a drag, the dragged object will jump while maintaining its
original distance from the line.</br>
New objects will always be created at grid
points.</br>
Holding down the snap modifier will disable the current grid
setting and allow you to move the object freely.</dd>
<dt><kbd class="menu">Magnetic</kbd></dt>
<dd>is a less strict type of snapping. Objects can still be moved to any position, but positions close to the relative or absolute grid points will snap. In order to move an object very close to a snap point, it may be necessary to zoom in to prevent snapping to that point, or to use the snap modifier to disable snap completely.</br>
As with Grid mode, the snap modifier will disable snap completely while the absolute snap modifier will move the "notch" of Magnetic snap to the grid lines.</dd>
<dd>is a less strict type of snapping. Objects can still be moved to any
position, but positions close to the relative or absolute grid points will snap.
In order to move an object very close to a snap point, it may be necessary to
zoom in to prevent snapping to that point, or to use the snap modifier to
disable snap completely.</br> As with Grid mode, the snap modifier will disable
snap completely while the absolute snap modifier will move the "notch" of
Magnetic snap to the grid lines.</dd>
</dl>
<h2>Syncing Regions to the Grid</h2>
<p>
By default, a region's beginning will be used as the reference for both types of snapping, but you can change this behaviour by setting a <dfn>sync point</dfn> in the region. Select the region(s) and press <kbd>V</kbd>. This will set the sync point to your edit point.
By default, a region's beginning will be used as the reference for both types of
snapping, this behaviour can be changed by setting a <dfn>sync point</dfn>
in the region, by selecting the region(s) and pressing <kbd>V</kbd>. This will set the
sync point to the current <a href="@@edit-point-control">edit point</a>.
</p>
<h2 id="gridunits">Grid Units</h2>
<p>
The selector next to the grid mode selector defines the size of the grid elements. You can set your grid to several different units:
The selector next to the grid mode selector defines the size of the grid
elements. The grid can be set to several different units:
</p>
<dl class="wide-table">
@ -102,15 +138,21 @@
</dl>
<p>
To use Region starts/ends/syncs/bounds as snap choices, you must have either
To use Region starts/ends/syncs/bounds as snap choices, it is necessary to have either:
</p>
<ul>
<li><em>No</em> tracks selected, which means that Ardour snaps to regions on any track, or </li>
<li>Several tracks selected, which means that Ardour only snaps to regions on those selected tracks.</li>
<li><em>No</em> tracks selected, which means that Ardour snaps to regions on any
track, or </li>
<li>Several tracks selected, which means that Ardour only snaps to regions on
those selected tracks.</li>
</ul>
<p>
If you are moving items on a track, and only the current track is selected, then you will only be able to snap to other regions on the same track. This means that enabling <kbd class="menu">Edit &gt; Preferences &gt; Editor &gt; Link Selections of Regions and Tracks</kbd> will make the "Region" grid unit unusable. Avoid the use of this option if you are going to use any of the Region grid units.
If items are moved on a track, and only the current track is selected, then
snapping will only happen with other regions on the same track. This means
that enabling <kbd class="menu">Edit &gt; Preferences &gt; Editor &gt; Link
Selections of Regions and Tracks</kbd> will make the "Region" grid unit
unusable. This option should not be used in conjunction with the use any of the
Region grid units.
</p>