part: chapter
---
+---
+title: About Ardour's documentation
+part: subchapter
+---
+
+<h2>Conventions Used In This Manual</h2>
+
+<p>
+ This section covers some of the typographical and language conventions used in this manual.
+</p>
+
+<h3>Keyboards and Modifiers</h3>
+
+<p>
+ <dfn>Keyboard bindings</dfn> are shown like this: <kbd>s</kbd> or <kbd class="mod1">x</kbd>.
+</p>
+
+<p>
+ <kbd class="mod1">x</kbd> means "press the <kbd class="mod1"> </kbd> key, keep it pressed and then also press the <kbd>x</kbd> key.
+</p>
+
+<p>
+ You may also see key combinations such as <kbd class="mod12">e</kbd>, which mean that you should hold down the <kbd class="mod1"> </kbd> key <em>and</em> the <kbd class="mod2"> </kbd> key, and then, while keeping them both down, press the <kbd>e</kbd> key.
+</p>
+
+<p>
+ Note that different platforms have different conventions for which modifier key (Control or Command) to use as the primary or most common modifier. When viewing this manual from a machine identifying itself as running OS X, you will see <kbd>Cmd </kbd> where appropriate (for instance in the first example above). On other machines you will see <kbd>Ctrl </kbd> instead.
+</p>
+
+<h3>Mouse Buttons</h3>
+
+<p>
+ We refer to <a href="/setting-up-your-system/the-mouse">mouse buttons</a> as <kbd class="mouse">Left</kbd>, <kbd class="mouse">Middle</kbd> and <kbd class="mouse">Right</kbd>. Ardour can use additional buttons, but they have no default behaviour in the program.
+</p>
+
+<h4>Mouse click modifiers</h4>
+
+<p>
+ Many editing functions are performed by clicking the mouse while holding a modifier key, for example <kbd class="mouse mod1">Left</kbd>.
+</p>
+
+<h4>Mouse wheel</h4>
+
+<p>
+ Some GUI elements can optionally be controlled with the mouse wheel when the pointer is hovering over them. The notation for mouse wheel action is <kbd class="mouse">⇑</kbd> <kbd class="mouse">⇐</kbd> <kbd class="mouse">⇓</kbd> <kbd class="mouse">⇒</kbd>.
+</p>
+
+<h4>Context-click</h4>
+
+<p>
+ The term <dfn>context-click</dfn> is used to indicate that you should (typically) <kbd class="mouse">Right</kbd>-click on a particular element of the graphical user interface. Although right-click is the common, default way to do this, there are other ways to accomplish the same thing—this term refers to any of them, and the result is always that a menu specific to the item you clicked on will be displayed.
+</p>
+
+<h4>"The Pointer"</h4>
+
+<p>
+ When the manual refers to the "pointer", it means the on-screen representation of the mouse position or the location of a touch action if you are using a touch interface.
+</p>
+
+<h3>Other user input</h3>
+
+<p>
+ Ardour supports hardware controllers, such as banks of <kbd class="fader">faders</kbd>, <kbd class="knob">knobs</kbd>, or <kbd class="button">buttons</kbd>.
+</p>
+
+<h3>Menu Items</h3>
+
+<p>
+ Menu items are indicated like this:<br />
+ <kbd class="menu">Top > Next > Deeper</kbd>.<br />
+ Each ">"-separated item indicates one level of a nested (sub-)menu.
+</p>
+
+<h3>Preference/Dialog Options</h3>
+
+<p>
+ Choices in various dialogs, notably the Preferences and Properties dialog, are
+ indicated like this:<br />
+ <kbd class="option">Edit > Preferences > Audio > Some
+ Option</kbd>.<br />
+ Each successive item indicates either a (sub-) menu or a tabbed dialog
+ navigation. The final item is the one to choose or select.
+</p>
+
+<p>
+ If you are requested to deselect an option, you will see something like
+ this:<br />
+ <kbd class="optoff">Edit > Preferences > Audio > Some other
+ Option</kbd>.<br />
+</p>
+
+<h3>User Input</h3>
+
+<p>
+ Some dialogs or features may require you to type in some <kbd class="input">data such as this</kbd>. In rare cases, you will be required to perform certain operations at the command line of your operating system:
+</p>
+
+<kbd class="cmd lin">cat /proc/cpuinfo</kbd>
+<kbd class="cmd mac">sleep 3600</kbd>
+<kbd class="cmd win">ping www.google.com</kbd>
+
+<h3>Program Output</h3>
+
+<p>
+ Important messages from Ardour or other programs will be displayed <samp>like this</samp>.
+</p>
+
+<h3>Notes</h3>
+
+<p class="note">
+ Important notes about things that might not otherwise be obvious are shown in this format.
+</p>
+
+<h3>Warnings</h3>
+
+<p class="warning">
+ Hairy issues that might cause things to go wrong, lose data, impair sound quality, or eat your proverbial goldfish, are displayed in this way.
+</p>
+
---
title: Welcome to Ardour!
<li>they are not available in source code form, making modifications, improvements, bugfixes by technically inclined users or their friends or consultants impossible.</li>
</ul>
+---
+title: Additional Resources
+part: subchapter
+---
+
+<p>
+ In addition to this documentation, you may check a variety of other <dfn>resources</dfn>:
+</p>
+
+<ul>
+ <li>the <a href="https://ardour.org/whatsnew.html">Ardour release
+ notes</a></li>
+ <li>the <a href="https://community.ardour.org/forums">Ardour
+ Forums</a></li>
+ <li>information about <a href="https://community.ardour.org/community">Ardour
+ Support</a> via mailing lists and IRC (chat)</li>
+</ul>
+
+<p>
+ The <dfn>IRC channels</dfn> in particular are where most of the day-to-day development and debugging is done, and there are plenty of experienced users to help you if you run into problems.
+</p>
+
+<p>
+ Please be prepared to hang around for a few hours, the chat is usually busiest from 19:00 UTC to 04:00 UTC. If you can, keep your chat window open, so that you don't miss a belated answer. Also, don't ask for permission to ask a question, just ask your question with the understanding that the answer (from the "right" people or not) could come seconds, minutes, hours, or never.
+</p>
+
+
---
title: Creating Music with Ardour
part: subchapter
---
+<p class="fixme"> misplaced</p>
<p>
Ardour can be used in many different ways, from extremely simple to
extremely complex. Many projects will be handled using the following
</dl>
----
-title: Using This Documentation
-part: chapter
----
-
-
----
-title: About Ardour documentation
-part: subchapter
----
-
-<h2>Conventions Used In This Manual</h2>
-
-<p>
- This section covers some of the typographical and language conventions used in this manual.
-</p>
-
-<h3>Keyboards and Modifiers</h3>
-
-<p>
- <dfn>Keyboard bindings</dfn> are shown like this: <kbd>s</kbd> or <kbd class="mod1">x</kbd>.
-</p>
-
-<p>
- <kbd class="mod1">x</kbd> means "press the <kbd class="mod1"> </kbd> key, keep it pressed and then also press the <kbd>x</kbd> key.
-</p>
-
-<p>
- You may also see key combinations such as <kbd class="mod12">e</kbd>, which mean that you should hold down the <kbd class="mod1"> </kbd> key <em>and</em> the <kbd class="mod2"> </kbd> key, and then, while keeping them both down, press the <kbd>e</kbd> key.
-</p>
-
-<p>
- Note that different platforms have different conventions for which modifier key (Control or Command) to use as the primary or most common modifier. When viewing this manual from a machine identifying itself as running OS X, you will see <kbd>Cmd </kbd> where appropriate (for instance in the first example above). On other machines you will see <kbd>Ctrl </kbd> instead.
-</p>
-
-<h3>Mouse Buttons</h3>
-
-<p>
- We refer to <a href="/setting-up-your-system/the-mouse">mouse buttons</a> as <kbd class="mouse">Left</kbd>, <kbd class="mouse">Middle</kbd> and <kbd class="mouse">Right</kbd>. Ardour can use additional buttons, but they have no default behaviour in the program.
-</p>
-
-<h4>Mouse click modifiers</h4>
-
-<p>
- Many editing functions are performed by clicking the mouse while holding a modifier key, for example <kbd class="mouse mod1">Left</kbd>.
-</p>
-
-<h4>Mouse wheel</h4>
-
-<p>
- Some GUI elements can optionally be controlled with the mouse wheel when the pointer is hovering over them. The notation for mouse wheel action is <kbd class="mouse">⇑</kbd> <kbd class="mouse">⇐</kbd> <kbd class="mouse">⇓</kbd> <kbd class="mouse">⇒</kbd>.
-</p>
-
-<h4>Context-click</h4>
-
-<p>
- The term <dfn>context-click</dfn> is used to indicate that you should (typically) <kbd class="mouse">Right</kbd>-click on a particular element of the graphical user interface. Although right-click is the common, default way to do this, there are other ways to accomplish the same thing—this term refers to any of them, and the result is always that a menu specific to the item you clicked on will be displayed.
-</p>
-
-<h4>"The Pointer"</h4>
-
-<p>
- When the manual refers to the "pointer", it means the on-screen representation of the mouse position or the location of a touch action if you are using a touch interface.
-</p>
-
-<h3>Other user input</h3>
-
-<p>
- Ardour supports hardware controllers, such as banks of <kbd class="fader">faders</kbd>, <kbd class="knob">knobs</kbd>, or <kbd class="button">buttons</kbd>.
-</p>
-
-<h3>Menu Items</h3>
-
-<p>
- Menu items are indicated like this:<br />
- <kbd class="menu">Top > Next > Deeper</kbd>.<br />
- Each ">"-separated item indicates one level of a nested (sub-)menu.
-</p>
-
-<h3>Preference/Dialog Options</h3>
-
-<p>
- Choices in various dialogs, notably the Preferences and Properties dialog, are
- indicated like this:<br />
- <kbd class="option">Edit > Preferences > Audio > Some
- Option</kbd>.<br />
- Each successive item indicates either a (sub-) menu or a tabbed dialog
- navigation. The final item is the one to choose or select.
-</p>
-
-<p>
- If you are requested to deselect an option, you will see something like
- this:<br />
- <kbd class="optoff">Edit > Preferences > Audio > Some other
- Option</kbd>.<br />
-</p>
-
-<h3>User Input</h3>
-
-<p>
- Some dialogs or features may require you to type in some <kbd class="input">data such as this</kbd>. In rare cases, you will be required to perform certain operations at the command line of your operating system:
-</p>
-
-<kbd class="cmd lin">cat /proc/cpuinfo</kbd>
-<kbd class="cmd mac">sleep 3600</kbd>
-<kbd class="cmd win">ping www.google.com</kbd>
-
-<h3>Program Output</h3>
-
-<p>
- Important messages from Ardour or other programs will be displayed <samp>like this</samp>.
-</p>
-
-<h3>Notes</h3>
-
-<p class="note">
- Important notes about things that might not otherwise be obvious are shown in this format.
-</p>
-
-<h3>Warnings</h3>
-
-<p class="warning">
- Hairy issues that might cause things to go wrong, lose data, impair sound quality, or eat your proverbial goldfish, are displayed in this way.
-</p>
-
----
-title: Additional Resources
-part: subchapter
----
-
-<p>
- In addition to this documentation, you may check a variety of other <dfn>resources</dfn>:
-</p>
-
-<ul>
- <li>the <a href="https://ardour.org/whatsnew.html">Ardour release
- notes</a></li>
- <li>the <a href="https://community.ardour.org/forums">Ardour
- Forums</a></li>
- <li>information about <a href="https://community.ardour.org/community">Ardour
- Support</a> via mailing lists and IRC (chat)</li>
-</ul>
-
-<p>
- The <dfn>IRC channels</dfn> in particular are where most of the day-to-day development and debugging is done, and there are plenty of experienced users to help you if you run into problems.
-</p>
-
-<p>
- Please be prepared to hang around for a few hours, the chat is usually busiest from 19:00 UTC to 04:00 UTC. If you can, keep your chat window open, so that you don't miss a belated answer. Also, don't ask for permission to ask a question, just ask your question with the understanding that the answer (from the "right" people or not) could come seconds, minutes, hours, or never.
-</p>
-
-
---
title: System Configuration
part: part
</ul>
-
---
-title: Ardour Main Window
+title: Ardour's Interface
part: part
---
+
+---
+title: About Ardour's Interface
+part: chapter
+---
+
<p>
In Ardour, you work in two main windows: the <dfn>Editor</dfn> and the
<dfn>Mixer</dfn>.
<p class="fixme">Add content</p>
+
---
title: Status Bar
part: chapter
---
-<p class="fixme">Add content</p>
+<img src="/images/status-bar.png" alt="The status bar">
+<p>The status bar is an informative bar at the top of the window, showing:</p>
+<ul>
+ <li><dfn>File:</dfn> the file format used in the session, including when recording</li>
+ <li><dfn>TC:</dfn> is the timecode, i.e. the number of frames per second used by the session (for videos)</li>
+ <li><dfn>Audio:</dfn> gives the sample rate used in the session, and the latency computed from the buffer size</li>
+ <li><dfn>Buffers:</dfn> decribe how much data is buffered, see below</li>
+ <li><dfn>DSP:</dfn> for Digital Sound Processing, shows how much of the CPU is used by Ardour and its plugins</li>
+ <li><dfn>X:</dfn> shows the number of xruns since Ardour's launch, see below</li>
+ <li><dfn>Disk:</dfn> reports the remaining hard disk space as the time that can be recorded with the current session setting</li>
+ <li><dfn>a Clock</dfn> showing the system time</li>
+ <li><dfn>a Log button</dfn> that indicates if Ardour has encountered any warning or error.</li>
+</ul>
+
+<p>The buffers are labelled as <kbd class="menu">p</kbd> for playback and <kbd class="menu">c</kbd> for capture. If the
+system is fast enough, these buffers should be 100% full at all times, showing the system has time to precompute
+all the data before delivering it to the audio system. A buffer constantly under 20% is a sign of an underpowered
+computer system or of too much processing.</p>
+
+<p>An Xrun (short for buffer over- or under-run) happens when the system has been forced to skip audio frames, e.g. if the latency
+asked is too short for the computing power of the machine. It usually results in clicks, pops and crackles if it happens while recording.</p>
+
+<p>The log button turns yellow when a warning is shows, and red when an error occurs. Clicking the log button gives acces to the log.</p>
---
title: Transport bar and times
part: chapter
---
-<p class="fixme">There is no discussion of starting playback anywhere in here. Starting/stopping needs to be explained</p>
-
<p>
Ardour offers many ways to <dfn>control playback</dfn> of your session, including the transport bar, key bindings and remote controls. You can also use markers to define locations or ranges within the session and rapidly move around between them.
</p>
<li>the Mode Selector, allowing to switch between Editor and Mixer views, or edit the Preferences.</li>
</ul>
-
-
---
title: The Transport Bar
part: subchapter
---
-
<p>
The <dfn>Transport Bar</dfn> groups all the actions regarding the control of playback and recording.
</p>
-<img src="/images/transport.png" alt="The transport controls" />
+<p class="center"><img src="/images/transport.png" alt="The transport controls" /></p>
<p>
This bar is made of (from left to right):
<ul>
<li>
- <dfn>Midi Panic</dfn>: allows to immediately stop all midi output.
+ <dfn>Midi Panic</dfn>: Immediately stops all midi output.
</li>
<li>
<dfn>Enable/disable Audio Click</dfn>: Toggles (on/off) a click track (metronome) along the <a href="/tempo-meter/tempo-and-meter/">tempo</a>.
<dfn>Go to End of the Session</dfn>: Jumps forward to the end of the session, as defined by the <a href="/working-with-markers/">end marker</a>.
</li>
<li>
- <dfn>Play Loop Range</dfn>: Repeats the defined <a href="/controlling-playback/looping-the-transport/">loop</a> as defined by the <a href="/working-with-markers/loop-range/">Loop range</a>, until the "Stop playback" button is pressed. Clicking the "Play loop Range" button while already active switches to normal Play mode, which allows to exit the loop without stopping and restarting the playback.
+ <dfn>Play Loop Range</dfn>: Repeats the defined <a href="/controlling-playback/looping-the-transport/">loop</a> as defined by the <a href="/working-with-markers/loop-range/">Loop range</a>, until the "Stop playback" button is pressed. Clicking the "Play loop Range" button while already active switches to normal Play mode, which exits the loop without stopping and restarting playback.
</li>
<li>
<dfn>Play Range/Selection</dfn>: If a range has been defined using the Range Mode button, plays the range, of if an audio or MIDI region is selected, plays this region. In both cases, the playback stops at the end of the range or selected region.
</li>
<li>
- <dfn>Play from playhead</dfn>: Starts the playback and optionally record (more bellow).
+ <dfn>Play from playhead</dfn>: Starts the playback and optionally record (more below).
</li>
<li>
<dfn>Stop</dfn>: Whatever the playing mode (loop, range, …) stops all playback. Depending on other settings, some effects (like chorus or reverb) might still be audible for a while.
</li>
<li>
- <dfn>Toggle Record</dfn>: Global switch button to activate/deactivate recording. While active, the button blinks red. The button doesn't start
the recording itself: if one or more tracks are marked as record-enabled, pressing the "Play from Playhead" starts the recording on this/these track(s). See <a href="/recording/">Recording</a>.
+ <dfn>Toggle Record</dfn>: Global switch button to activate/deactivate recording. While active, the button blinks red. The button doesn't start
recording by itself: if one or more tracks are marked as record-enabled, pressing the "Play from Playhead" starts recording on those tracks. See <a href="/recording/">Recording</a>.
</li>
</ul>
-<p class="fixme">Language in the above paragraphs is awkward</p>
+<p class="fixme">Add default keyboard shortcuts to the above.</p>
<p class="note">
All these actions are bound to keyboard shortcuts, which allows for speedier use and more focused work.
<dfn>Follow Edits</dfn> is a toggle that can be used to control whether or not making a selection (range or object) will move the playhead to the start of the selection.
</li>
<li>
- <dfn>Auto Return</dfn> is a toggle switch too. When active, pressing the Stop button returns the playhead to its previous position, and when inactive, pressing Stop keeps the playhead at its current location. Activating Auto Return can be useful for earing back the same part of the audio before and after having tweaked it, without having to loop on it.
+ <dfn>Auto Return</dfn> is a toggle switch too. When active, pressing the Stop button returns the playhead to its previous position, and when inactive, pressing Stop keeps the playhead at its current location. Activating Auto Return can be useful for hearing the same piece of audio before and after tweaking it, without having to set a loop range on it.
</li>
</ul>
-
---
title: Times
part: subchapter
</p>
<h2>Mouse Modes</h2>
+
<dl class="wide-table">
+
<dt id="object">Grab Mode</dt>
<dd>The <dfn>Grab Mode</dfn> is used for selecting, moving, deleting and
copying objects. When in object mode, the mouse pointer appears as a hand
whenever it is over the track canvas or the rulers. The mouse can now be
used to select and perform operations on objects such as regions, markers etc.
This is the most common mode to work in, as it allows you to select and move regions,
- as well as modify automation points on the automation tracks.
- </dd>
+ as well as modify automation points on the automation tracks.</dd>
<dt>Range Mode</dt>
<dd>When in <dfn>Range Mode</dfn>, the mouse pointer appears as a vertical line
If none of your tracks are selected, the Range Tool will operate on all the
session track visualized in the Editor.<br>
If you want to edit only particular tracks, select them before you apply
- the range tool.
- </dd>
+ the range tool.</dd>
<dt>Cut Tool Mode</dt>
<dd>When in <dfn>Cut Tool Mode</dfn>, the mouse pointer appears as a pair of scissors
<dt>Audition Tool</dt>
<dd>Clicking a region using the <dfn>audition tool</dfn> will play this
- region to the control room outputs.
- <p>You can also <dfn>scrub</dfn> with this tool by clicking and dragging in
+ region to the control room outputs.<br>
+ You can also <dfn>scrub</dfn> with this tool by clicking and dragging in
the direction you wish to listen. The amount you drag in one direction or
- the other will determine the playback speed.</p>
- </dd>
+ the other will determine the playback speed.</dd>
<dt>Draw Tool</dt>
<dd>When in <dfn>Draw Tool</dfn> mode, the mouse pointer will change to
region is moved, the region gain envelope is moved along with it.<br>
The draw tool works on automation too, allowing the creation and modification
of control points on the automation curves.<br>
- Last, it is used on a MIDI region to edit the notes.
- </dd>
+ Last, it is used on a MIDI region to edit the notes.</dd>
<dt>Internal/Region Edit Mode</dt>
<dd>When in <dfn>Internal Edit</dfn> mode, the mouse pointer will change to
cross-hairs. This tool acts on gegion gain and automation as the Draw tool.<br>
- on a MIDI region, it allows to lasso-select multiple notes at a time.</dd>
+ On a MIDI region, it allows to lasso-select multiple notes at a time.</dd>
</dl>
+
+
<p class="fixme">Make sure the Internal Edit and Draw tool act as described</p>
<img class="left" src="/images/toolbar-grid.png" alt="Editor toolbar's grid">
-<p class="fixme">Get rid of all the <br>s, they look like shit</p>
-
<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
<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
+ 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.</br>
unit selector.
</p>
-<p class="fixme">Add images</p>
-
-
---
title: the Nudge Controls
<img class="left" src="/images/toolbar-nudge.png" alt="Editor toolbar's Nudge">
<p>
- If there are no selected objects, the <dfn>nudge controls</dfn> can be
- used to move the playhead backward or forward by a fixed amount. The left
- and right buttons move either backward or forward in time, and the small
+ The <dfn>nudge controls</dfn> will move the selected region(s) by a fixed amount
+ of time. The left and right buttons move either backward or forward in time, and the small
clock to the left of these buttons sets the amount of time to nudge by.
As with all other clocks, you can right-click on the clock to choose the
time representation you want to use.
</p>
<p>
- Note that this is a secondary purpose of the nudge controls—it is
- usually used to move selected <dfn>objects</dfn> by specific distances, rather than
- the playhead.
+ If there are no selected objects, the nudge controls can be
+ used to move the playhead backward or forward by the amount shown on the clock.
</p>
---
<p>
- At the right of the editor is an optional area which provides one of a
+ At the right of the editor window is an optional area which provides one of a
range of useful lists of parts of your session. It is not shown by default
when you first start using Ardour. The <dfn>Editor list</dfn> can be hidden
or shown using <kbd class="menu">View > Show Editor List</kbd>. The very
---
<p>
- For information on this list see
- <a href="/working-with-markers/rangesmarks-list/">Ranges
- & Marks List</a> in the "Working with Markers" section of the manual.
+ The <dfn>Ranges & Marks List</dfn> is a tab in the <dfn>Editor
+ Lists</dfn> area on the right of the Editor window. If the editor
+ list area isn't visible it can be enabled by checking
+ <kbd class="option">View > Show Editor List</kbd>.
+ The Ranges & Marks list can be used as a single point
+ of control for all range and location markers (including the punch and
+ loop ranges), or as a supplement to other methods of working with them.
</p>
+<h2>Common elements</h2>
+<p>
+ Each section has a set of <dfn>editable <a
+ href="/ardours-interface/using-ardour-clock-displays/">clock widgets</a></dfn>
+ which display
+ the location of a marker, or the start, end, and duration times of a range,
+ respectively.<br />
+ The <kbd class="menu">Use PH</kbd> buttons allow you to set
+ the corresponding clock to the current playhead position.
+ A <kbd class="mouse">Middle</kbd> click on any of the clocks will move
+ the playhead to that location. Both functions are also available from the
+ clock context menus.<br />
+ Right clicking on any of the clocks brings up a context menu that allows
+ changing of the display between Timecode, Bars:Beats, Minutes:Seconds,
+ and Samples.<br />
+</p>
+<p>
+ The <kbd class="menu">—</kbd> (subtract) button in front of each
+ user-defined range or marker in the list allows that particular item to
+ be removed. The name fields of custom ranges and markers can be edited.
+</p>
+<p>
+ The <kbd class="option">Hide</kbd> checkboxes make markers and ranges invisible
+ on the respective ruler to reduce visual clutter; the markers remain
+ active however, and can be used normally.<br />
+ Selecting <kbd class="option">Lock</kbd> prevents the respective marker
+ from being moved until unlocked.
+ Where applicable, <kbd class="option">Glue</kbd> fixes the marker position
+ relative to the current musical position expressed in bars and beats, rather
+ than the absolute time. This will make the respective marker follow
+ changes in the tempo map.
+</p>
+<p>
+ At the bottom of the list are buttons to add new markers or ranges.
+</p>
+ <h2>List sections</h2>
+
+<dl>
+ <dt>Loop/Punch Ranges</dt>
+ <dd>This list shows the current <dfn>loop</dfn> and <dfn>punch</dfn> range
+ settings. Since these are built-in ranges, you cannot rename or remove them.</dd>
+ <dt>Markers (Including CD Index)</dt>
+ <dd>This section lists the session's <dfn>markers</dfn>. By ticking <kbd
+ class="option">CD</kbd>, you instruct Ardour to create a <dfn>CD track
+ index</dfn> from this marker, which will be included in the TOC or CUE file when you
+ export.</dd>
+ <dt>Ranges (Including CD Track Ranges)</dt>
+ <dd>This is the list of <dfn>ranges</dfn> (including <dfn>CD track
+ ranges</dfn>). Ticking <kbd class="option">CD</kbd> will convert
+ the range to a <dfn>CD track</dfn>, which will again be included in
+ exported TOC or CUE files. This is relevant for Disk-At-Once recordings
+ that may contain audio data between tracks.</dd>
+</dl>
& Marks List</kbd> in the Editor list.
</p>
----
-title: Ranges & Marks List
-part: subchapter
----
-
-<p>
- The <dfn>Ranges & Marks List</dfn> is a tab in the <dfn>Editor
- Lists</dfn> area on the right of the Editor window. If the editor
- list area isn't visible it can be enabled by checking
- <kbd class="option">View > Show Editor List</kbd>.
- The Ranges & Marks list can be used as a single point
- of control for all range and location markers (including the punch and
- loop ranges), or as a supplement to other methods of working with them.
-</p>
-
-<h2>Common elements</h2>
-
-<p>
- Each section has a set of <dfn>editable <a
- href="/ardours-interface/using-ardour-clock-displays/">clock widgets</a></dfn>
- which display
- the location of a marker, or the start, end, and duration times of a range,
- respectively.<br />
- The <kbd class="menu">Use PH</kbd> buttons allow you to set
- the corresponding clock to the current playhead position.
- A <kbd class="mouse">Middle</kbd> click on any of the clocks will move
- the playhead to that location. Both functions are also available from the
- clock context menus.<br />
- Right clicking on any of the clocks brings up a context menu that allows
- changing of the display between Timecode, Bars:Beats, Minutes:Seconds,
- and Samples.<br />
-</p>
-<p>
- The <kbd class="menu">—</kbd> (subtract) button in front of each
- user-defined range or marker in the list allows that particular item to
- be removed. The name fields of custom ranges and markers can be edited.
-</p>
-<p>
- The <kbd class="option">Hide</kbd> checkboxes make markers and ranges invisible
- on the respective ruler to reduce visual clutter; the markers remain
- active however, and can be used normally.<br />
- Selecting <kbd class="option">Lock</kbd> prevents the respective marker
- from being moved until unlocked.
- Where applicable, <kbd class="option">Glue</kbd> fixes the marker position
- relative to the current musical position expressed in bars and beats, rather
- than the absolute time. This will make the respective marker follow
- changes in the tempo map.
-</p>
-<p>
- At the bottom of the list are buttons to add new markers or ranges.
-</p>
- <h2>List sections</h2>
-
-<dl>
- <dt>Loop/Punch Ranges</dt>
- <dd>This list shows the current <dfn>loop</dfn> and <dfn>punch</dfn> range
- settings. Since these are built-in ranges, you cannot rename or remove them.</dd>
- <dt>Markers (Including CD Index)</dt>
- <dd>This section lists the session's <dfn>markers</dfn>. By ticking <kbd
- class="option">CD</kbd>, you instruct Ardour to create a <dfn>CD track
- index</dfn> from this marker, which will be included in the TOC or CUE file when you
- export.</dd>
- <dt>Ranges (Including CD Track Ranges)</dt>
- <dd>This is the list of <dfn>ranges</dfn> (including <dfn>CD track
- ranges</dfn>). Ticking <kbd class="option">CD</kbd> will convert
- the range to a <dfn>CD track</dfn>, which will again be included in
- exported TOC or CUE files. This is relevant for Disk-At-Once recordings
- that may contain audio data between tracks.</dd>
-</dl>
---
title: Moving Markers
projects / ardour-manual-diverged / blobdiff