---
-title: Times
+layout: default
+title: Editing Clocks
---
-
-
-
-<p>
-
- <dfn>Clocks</dfn> in Ardour are used to display <dfn>time values</dfn> precisely.
-
- In many cases, they are also one way to edit (change) time values, and in a few
-
- cases, the only way. All clocks share the same basic appearance and functionality,
-
- which is described below, but a few clocks serve particularly important roles.
-
-</p>
-
-
-
-<h2>Transport Clocks</h2>
-
-
-
-<p>
-
- In the transport bar of the editor window there are two clocks (unless you
-
- are on a very small screen), that display the current position of the playhead
-
- and additional information related to transport control and the timeline. These
-
- are called the <dfn>transport clocks</dfn>; the left one is the primary
-
- transport clock and the right one is the secondary transport clock.
-
- They look like this:
-
-</p>
-
-
-
-<img src="/images/new_main_clocks.png" alt="An image of the transport clocks in Ardour" />
-
-
-
-<p>
-
- Editing the time in the transport clocks will reposition the playhead in the same
-
- way that various other editing operations will.
-
-</p>
-
-
-
-<h3>The Big Clock</h3>
-
-<p>
-
- To show the current playhead position in a big, resizable window, activate
-
- <kbd class="menu">Window > Big Clock</kbd>. The big clock is very useful
-
- when you need to work away from the screen but still want to see the playhead
-
- position clearly (such as when working with a remote control device across
-
- a room). The big clock will change its visual appearance to indicate when active
-
- recording is taking place. Below on the left is a screenshot showing a fairly
-
- large big clock window filling a good part of the display, and on the right,
-
- the same clock during active recording.
-
-</p>
-
-<a href="/images/bigclock.png"><img src="/images/bigclock.png" height="100" alt="an image of the big clock filling a screen" /></a>Â <a href="/images/bigclock-recording.png"><img src="/images/bigclock-recording.png" height="100" alt="an image of the big clock while recording"
-
-/></a>
-
-
-
-<h3>The Special Role of the Secondary Transport Clock</h3>
-
-<p>
-
- On a few occasions Ardour needs to display time values to the user, but there
-
- is no obvious way to specify what units to use. The most common case is the big
-
- cursor that appears when dragging regions. For this and other similar cases,
-
- Ardour will display time using the same units as the secondary clock.
-
-</p>
-
-<h4>Why are there two transport clocks?</h4>
-
-<p>
-
- Having two transport clocks lets you see the playhead position in two different
-
- time units without having to change any settings. For example, you can see the
-
- playhead position in both timecode units and BBT time.
-
-</p>
-
-
-
-<h3>Selection and Punch Clocks</h3>
-
-<p>
-
- The transport bar also contains a set of 5 clocks that show the current
-
- <dfn>selection range</dfn> and <dfn>punch ranges</dfn>. Clicking on the punch
-
- range clocks will locate to either the beginning or end of the punch range.
-
- Similarly, clicking on the range clocks will locate to either the beginning
-
- or end of the current selection. In this screen shot there is no current
-
- selection range, so the selection clocks show an "off" state.
-
-</p>
-
-
-
-<img src="/images/selectionpunchclocks.png" alt="An image of the the selection and punch clocks in Ardour 3" />
-
-
-
<h2>Clock Modes</h2>
<p>
-
Every clock in Ardour has four different, selectable <dfn>clock
-
modes</dfn>. Each mode displays time using different units.
-
You can change the clock mode by <kbd class="mouse">Right</kbd>-clicking
-
on the clock and selecting the desired mode from the menu. Some clocks are
-
entirely independent of any other clock's mode; others are linked so that
-
changing one changes all clocks in that group. The different modes are:
-
</p>
<dl>
-
- <dt>Timecode</dt>
-
- <dd>Time is shown as <dfn><abbr title="Society of Motion Picture and Television
-
+ <dt>Timecode</dt><dd>Time is shown as <dfn><abbr title="Society of Motion Picture and Television
Engineers">SMPTE</abbr> timecode</dfn> in Hours:Minutes:Seconds:Frames,
-
measured from the timecode zero point on the timeline (which may not
-
correspond to the session start and/or absolute zero on the timeline,
-
depending on configurable timecode offsets).
-
The frames value is dictated by either the session <abbr title="Frames Per
-
Second">FPS</abbr> setting, or, if slaved to an external timecode master,
-
the master's setting. In the transport clocks, the FPS value is shown below
-
the time display, along with an indication of the current timecode source
-
(<samp>INT</samp> means that Ardour is its own timecode source).</dd>
-
- <dt>BBT</dt>
-
- <dd>Time is shown as Bars:Beats:Ticks, indicating <dfn>musical time</dfn> measured
-
+ <dt>BBT</dt><dd>Time is shown as Bars:Beats:Ticks, indicating <dfn>musical time</dfn> measured
from the start of the session. The transport clocks show the current tempo
-
in <abbr title="Beats Per Minute">bpm</abbr> and meter below the time
-
display.</dd>
-
- <dt>Minutes:Seconds</dt>
-
- <dd>Time is shown as Hours:Minutes:Seconds.Milliseconds, measured from the
-
+ <dt>Minutes:Seconds</dt><dd>Time is shown as Hours:Minutes:Seconds.Milliseconds, measured from the
absolute start of the timeline (ignoring the session start and any timecode
-
offsets).</dd>
-
- <dt>Samples</dt>
-
- <dd>Time is shown as a <dfn>sample count</dfn> from the absolute start of the timeline
-
+ <dt>Samples</dt><dd>Time is shown as a <dfn>sample count</dfn> from the absolute start of the timeline
(ignoring the session start and any timecode offsets). The number of
-
samples per second is given by the current sample rate, and in the transport
-
clocks, this rate is shown below the time display along with any
-
pullup/pulldown adjustment.</dd>
-
</dl>
-
-
-<h3>Special Modes for the Transport Clocks</h3>
-
-<p>
-
- In addition to the time-unit modes mentioned above, each of the two transport
-
- clocks (if you work on a small screen, you may only have one) can be
-
- independently set to display <dfn>Delta to Edit Point</dfn> in whatever time
-
- units its current mode indicates. This setting means that the clock shows the
-
- distance between the playhead and the current edit point, and it may show a
-
- positive or negative value depending on the temporal order of these two points.
-
- The clocks will use a different color when in this mode to avoid confusion.
-
-</p>
-
-<p>
-
- To switch either (or both!) of the transport clocks into this mode, use
-
- <kbd class="menu"> Edit > Preferences > Transport</kbd> and select
-
- the relevant checkboxes.
-
-</p>
-
-<p>
-
- Note that when in <samp>Delta to Edit Point</samp> mode, the transport clocks
-
- cannot be edited.
-
-</p>
-
-
-
<h2>Changing clock values with the keyboard</h2>
<p>
-
New values for the clock can be typed in after clicking on the relevant clock.
-
Clicking on the clock will show a thin vertical cursor bar just to the right
-
of the next character to be overwritten. Enter time in the same order as the
-
current clock mode—if the clock is in Timecode mode, you need to enter
-
hours, minutes, seconds, frames. So, to change to a time of 12:15:20:15 you
-
would type <kbd class="input">1 2 1 5 2 0 1 5</kbd>. Each number you type will
-
appear in a different color, from right to left, overwriting the existing value.
-
Mid-edit, after typing <kbd class="input">3 2 2 2</kbd> the clock might look like this:
-
</p>
-<img src="/images/clockedit.png" alt="An image of a clock being edited in Ardour 3" />
+<img src="/images/clockedit.png" alt="An image of a clock being edited in Ardour">
<p>
-
To finish the edit, press <kbd>↵</kbd> or <kbd>Tab</kbd>. To exit an
-
edit without changing the clock press <kbd>ESC</kbd>. If you mis-type an entry
-
so that the new value would be illegal (for example, resulting in more than 30
-
frames when Timecode is set to 30 frames per second), the clock will reset at
-
the end of the edit, and move the cursor back to the start so that you can
-
start over.
-
</p>
-
-
-<h3>Avoiding the mouse entirely</h3>
+<h2>Avoiding the mouse entirely</h2>
<p>
-
There is a shortcut available for those who wish to be able to edit the transport
-
clocks entirely without the mouse. It can be found in
-
<kbd class="menu">Window > Key Bindings > Transport > Focus On
-
Clock</kbd>. If bound to a key (<kbd>÷</kbd> on the numerical
-
keypad is the
-
default), then pressing that key is equivalent to clicking on the primary (left)
-
transport clock, and editing can begin immediately.
-
</p>
-
-
-<h3>Entering Partial Times</h3>
+<h2>Entering Partial Times</h2>
<p>
-
One detail of the editing design that is not immediately obvious is that it is
-
possible to enter part of a full time value. Suppose that the clock is in BBT
-
mode, displaying <samp>024|03|0029</samp>, and you want to alter the value to
-
the first beat of the current bar. Click on the clock and type
-
<kbd class="input">0 1 0 0 0 0</kbd>. Similarly, if it is in Minutes:Seconds
-
mode, displaying <samp>02:03:04.456</samp>, and you want to get to exactly 2
-
hours, click on the clock and type <kbd class="input">0 0 0 0 0 0 0</kbd> to
-
reset the minutes, seconds and milliseconds fields.
-
</p>
-
-
-<h3>Entering Delta Times</h3>
+<h2>Entering Delta Times</h2>
<p>
-
You can also type values into the clock that are intended as a relative change,
-
rather than a new absolute value. Simply end the edit by pressing
-
<kbd>+</kbd> or <kbd>-</kbd> (the ones on any keypad will also work). The plus
-
key will add the entered value to the current value of the clock, minus will
-
subtract it. For example, if the clock is in Samples mode and displays
-
<samp>2917839</samp>, you move it back 2000 samples by typing
-
<kbd class="input">2 0 0 0</kbd> and <kbd>-</kbd>, rather than ending with
-
- Enter or Tab. </p>
-
-
+ Enter or Tab.
+</p>
<h2>Changing clock values with the mouse</h2>
-
-
<h3>Using a scroll wheel</h3>
-
-
<p>
-
Position the mouse pointer over the clock, and move the scroll wheel. Moving
-
the scroll wheel up (<kbd class="mouse">⇑</kbd>) increases the value
-
shown on the clock, moving it down (<kbd class="mouse">⇑</kbd>)
-
decreases it. The step size is equal to the unit of the field
-
you are hovering over (seconds, hours, etc.).
-
</p>
-
-
<h3>Dragging the mouse</h3>
-
-
<p>
-
Position the mouse pointer over the clock, press the left mouse button and drag.
-
Dragging upwards increases the value shown on the clock, dragging downwards
-
decreases it, again with a step size equal to the unit of the field you
-
began the drag on.
-
</p>
</p>
<ul>
<li>time-constrained region copying</li>
- <li><a href="/using-control-surfaces/midi-learn/"><abbr title="Musical
+ <li><a href="/using-control-surfaces/
generic-midi/midi-learn/"><abbr title="Musical
Instrument Digital Interface">MIDI</abbr> bindings</a>
created by "learning" them from incoming MIDI data</li>
</ul>
---
<p>
- In Ardour, you work in two main windows: the <dfn>Editor</dfn> and the
+ In Ardour, work is done in two main windows: the <dfn>Editor</dfn> and the
<dfn>Mixer</dfn>.
</p>
-<figure>
- <img src="/images/global-editor-window-split.png" alt="Ardour's editor window">
- <img style="margin-left:2em;" src="/images/global-mixer-window-split.png" alt="Ardour's mixer window">
- <figcaption>
+<figure style="width:100%;">
+
+ <div class="container" style="float:left; width: 615px; height: 445px; background-image: url('/images/editor_split_OSTitlebar.png');">
+ <a href="/ardours-interface/main-menu/" alt="Menu"><div class="hoverimg" style="left: 12px; top: 18px; width: 194px; height: 15px; background-image: url('/images/editor_split_Menu.png');"></div></a>
+ <a href="/ardours-interface/status-bar/" alt="Status Bar"><div class="hoverimg" style="left: 219px; top: 18px; width: 379px; height: 15px; background-image: url('/images/editor_split_StatusBar.png');"></div></a>
+ <a href="/ardours-interface/the-transport-bar/" alt="Transport Bar"><div class="hoverimg" style="left: 10px; top: 36px; width: 199px; height: 39px; background-image: url('/images/editor_split_TransportBar.png');"></div></a>
+ <a href="/ardours-interface/transport-clocks/" alt="Transport Clocks"><div class="hoverimg" style="left: 214px; top: 35px; width: 147px; height: 39px; background-image: url('/images/editor_split_TransportClocks.png');"></div></a>
+ <a href="/ardours-interface/selection-and-punch-clocks/" alt="Selection and Punch Clocks"><div class="hoverimg" style="left: 366px; top: 35px; width: 133px; height: 39px; background-image: url('/images/editor_split_SelectionandPunchClocks.png');"></div></a>
+ <a href="/ardours-interface/status-indicators/" alt="Status and Mode buttons"><div class="hoverimg" style="left: 504px; top: 35px; width: 94px; height: 39px; background-image: url('/images/editor_split_StatusandModebuttons.png');"></div></a>
+ <a href="/ardours-interface/audio-midi-mixer-strips/" alt="Editors Mixer Strip"><div class="hoverimg" style="left: 6px; top: 78px; width: 56px; height: 332px; background-image: url('/images/editor_split_EditorsMixerStrip.png');"></div></a>
+ <a href="/ardours-interface/the-summary/" alt="Summary"><div class="hoverimg" style="left: 72px; top: 385px; width: 394px; height: 51px; background-image: url('/images/editor_split_Summary.png');"></div></a>
+ <a href="/ardours-interface/editor-lists/" alt="Editors List"><div class="hoverimg" style="left: 474px; top: 105px; width: 122px; height: 309px; background-image: url('/images/editor_split_EditorsList.png');"></div></a>
+ <a href="/ardours-interface/the-nudge-controls/" alt="Nudge Controls"><div class="hoverimg" style="left: 512px; top: 79px; width: 94px; height: 23px; background-image: url('/images/editor_split_NudgeControls.png');"></div></a>
+ <a href="/ardours-interface/the-edit-point-control/" alt="Edit Point"><div class="hoverimg" style="left: 461px; top: 80px; width: 45px; height: 23px; background-image: url('/images/editor_split_EditPoint.png');"></div></a>
+ <a href="/ardours-interface/the-grid-controls/" alt="Grid Controls"><div class="hoverimg" style="left: 349px; top: 80px; width: 108px; height: 23px; background-image: url('/images/editor_split_GridControls.png');"></div></a>
+ <a href="/ardours-interface/the-zoom-controls/" alt="Zoom Controls"><div class="hoverimg" style="left: 215px; top: 79px; width: 129px; height: 23px; background-image: url('/images/editor_split_ZoomControls.png');"></div></a>
+ <a href="/ardours-interface/the-toolbox/" alt="Toolbox"><div class="hoverimg" style="left: 69px; top: 79px; width: 140px; height: 23px; background-image: url('/images/editor_split_Toolbox.png');"></div></a>
+ <a href="/ardours-interface/the-ruler/" alt="Rulers"><div class="hoverimg" style="left: 72px; top: 105px; width: 394px; height: 62px; background-image: url('/images/editor_split_Rulers.png');"></div></a>
+ <div class="hoverimg" style="left: 69px; top: 170px; width: 8px; height: 197px; background-image: url('/images/editor_split_Groupstabs.png');"></div>
+ <div class="hoverimg" style="left: 81px; top: 320px; width: 386px; height: 62px; background-image: url('/images/editor_split_aMIDITrack.png');"></div>
+ <div class="hoverimg" style="left: 81px; top: 285px; width: 386px; height: 33px; background-image: url('/images/editor_split_anotherAudioTrack.png');"></div>
+ <div class="hoverimg" style="left: 81px; top: 248px; width: 386px; height: 34px; background-image: url('/images/editor_split_Automation.png');"></div>
+ <div class="hoverimg" style="left: 81px; top: 207px; width: 386px; height: 37px; background-image: url('/images/editor_split_anAudioTrack.png');"></div>
+ <div class="hoverimg" style="left: 81px; top: 170px; width: 386px; height: 33px; background-image: url('/images/editor_split_MasterBusTrack.png');"></div>
+ </div>
+
+ <div class="container" style="float:left; width: 627px; height: 430px; background-image: url('/images/mixer_split_OsTitleBar.png');">
+ <a href="/ardours-interface/main-menu/" alt="Menu Bar"><div class="hoverimg" style="left: 18px; top: 17px; width: 193px; height: 16px; background-image: url('/images/mixer_split_MenuBar.png');"></div></a>
+ <a href="/ardours-interface/status-bar/" alt="Status Bar"><div class="hoverimg" style="left: 226px; top: 17px; width: 379px; height: 16px; background-image: url('/images/mixer_split_StatusBar.png');"></div></a>
+ <a href="/ardours-interface/the-transport-bar/" alt="Transport Bar"><div class="hoverimg" style="left: 12px; top: 37px; width: 198px; height: 38px; background-image: url('/images/mixer_split_TransportBar.png');"></div></a>
+ <a href="/ardours-interface/transport-clocks/" alt="Transport Clocks"><div class="hoverimg" style="left: 216px; top: 38px; width: 146px; height: 38px; background-image: url('/images/mixer_split_TransportClocks.png');"></div></a>
+ <a href="/ardours-interface/selection-and-punch-clocks/" alt="Punch and Selection Clocks"><div class="hoverimg" style="left: 369px; top: 38px; width: 135px; height: 38px; background-image: url('/images/mixer_split_PunchandSelectionClocks.png');"></div></a>
+ <a href="/ardours-interface/status-indicators/" alt="Status and Mode buttons"><div class="hoverimg" style="left: 511px; top: 37px; width: 94px; height: 38px; background-image: url('/images/mixer_split_StatusandModebuttons.png');"></div></a>
+ <a href="/ardours-interface/favorite-plugins-window/" alt="Favorite Plugins"><div class="hoverimg" style="left: 6px; top: 79px; width: 116px; height: 136px; background-image: url('/images/mixer_split_FavoritePlugins.png');"></div></a>
+ <a href="/ardours-interface/the-strips-list/" alt="Strips List"><div class="hoverimg" style="left: 6px; top: 220px; width: 115px; height: 97px; background-image: url('/images/mixer_split_StripsList.png');"></div></a>
+ <a href="/ardours-interface/the-groups-list/" alt="Group List"><div class="hoverimg" style="left: 6px; top: 321px; width: 116px; height: 99px; background-image: url('/images/mixer_split_GroupList.png');"></div></a>
+ <a href="/ardours-interface/audio-midi-mixer-strips/" alt="an Audio Strip"><div class="hoverimg" style="left: 128px; top: 97px; width: 57px; height: 320px; background-image: url('/images/mixer_split_anAudioStrip.png');"></div></a>
+ <a href="/ardours-interface/audio-midi-mixer-strips/" alt="another Audio Strip"><div class="hoverimg" style="left: 191px; top: 97px; width: 55px; height: 320px; background-image: url('/images/mixer_split_anotherAudioStrip.png');"></div></a>
+ <a href="/ardours-interface/audio-midi-mixer-strips/" alt="a MIDI Strip"><div class="hoverimg" style="left: 251px; top: 97px; width: 55px; height: 320px; background-image: url('/images/mixer_split_aMIDIStrip.png');"></div></a>
+ <a href="/ardours-interface/busses-mixer-strips/" alt="a Bus Strip"><div class="hoverimg" style="left: 313px; top: 97px; width: 56px; height: 320px; background-image: url('/images/mixer_split_aBusStrip.png');"></div></a>
+ <a href="/ardours-interface/control-masters/" alt="Control Masters"><div class="hoverimg" style="left: 373px; top: 81px; width: 98px; height: 331px; background-image: url('/images/mixer_split_ControlMasters.png');"></div></a>
+ <a href="/ardours-interface/the-master-bus-strip/" alt="the Master Strip"><div class="hoverimg" style="left: 477px; top: 81px; width: 54px; height: 331px; background-image: url('/images/mixer_split_theMasterStrip.png');"></div></a>
+ <a href="/ardours-interface/the-monitor-section/" alt="Monitor Section"><div class="hoverimg" style="left: 536px; top: 80px; width: 82px; height: 332px; background-image: url('/images/mixer_split_MonitorSection.png');"></div></a>
+ <div class="hoverimg" style="left: 133px; top: 80px; width: 223px; height: 11px; background-image: url('/images/mixer_split_GroupTabs.png');"></div>
+ </div>
+
+ <!--<figcaption>
<ol class="multicol3">
<li>Main menu</li>
<li>Status bar</li>
-</ol><ol class="multicol3" start="3">
- <li>Transport bar & Times</li>
+
</ol><ol class="multicol3" start="3">
+ <li>Transport bar and Times</li>
<li>Mode switch</li>
-</ol><ol class="multicol3" start="5">
+
</ol><ol class="multicol3" start="5">
<li>The <dfn>Mixer</dfn> window</li>
<li>The <dfn>Editor</dfn> window</li>
</ol>
+ </figcaption>-->
+ <figcaption>
+ The Editor and Mixer windows. Click on a section to access its description.
</figcaption>
</figure>
<p>
- Switching between the Editor and the Mixer windows done :
+ Switching between the Editor and the Mixer windows is done :
</p>
-
<ul>
- <li>with the Mode Switch buttons (#4 in the screenshot) in the upper right</li>
+ <li>with the <a href="/ardours-interface/status-indicators/">Mode Selector buttons</a> in the upper right</li>
<li>with the <kbd class="mod2">M</kbd> shortcut</li>
<li>with the menu <kbd class="menu">Window > Editor <em>(or Mixer)</em> > Show</kbd>.</li>
</ul>
setup) using <kbd class="menu">Window > Editor <em>(or Mixer)</em> > Detach</kbd> option in the same submenu.
</p>
+<h2>The Editor</h2>
+
+<p>
+ The <dfn>Editor</dfn> window includes the editor track <dfn>canvas</dfn>
+ where audio and MIDI data can be arranged along a timeline. This is the
+ window where editing and arranging a project is done. The window
+ has a general "horizontal" sense to it: the timeline flows from left to
+ right, the playhead showing the current position in the session moves
+ from left to right — the window really represents <dfn>time</dfn>
+ in a fairly literal way.
+</p>
+<p>
+ It is possible to show a single channel strip in the editor window, and
+ some people find this enough to work on mixing without actually opening
+ the mixer window. Most of the time though, both of these windows will be
+ needed at various stages of a session's lifetime.
+</p>
+
+<h2>The Mixer</h2>
+
+<p>
+ The <dfn>Mixer</dfn> window represents signal flow and is the window that will
+ probably be used most when mixing a session. It
+ includes <dfn>channel strips</dfn> for each track and bus in the session.
+ It has a general "vertical" sense to it: signals flow from the top of each
+ channel strip through the processing elements in the strip to reach the
+ output listed at the bottom.
+</p>
+<p>
+ To learn more about the process of mixing, see <a href="/mixing/">Mixing<a>.
+</p>
+
+
{% children %}
title: Main Menu
---
-
-
<p>
The <dfn>Main Menu</dfn> is made of 8 menus that allow the user to interact with Ardour, and below is a reference of all the menu actions.
</p>
<dt class="sub1">Play Selection</dt><dd>Only plays the selected part of the session, be it a range or selected regions</dd>
<dt class="sub1">Play Selection w/Preroll</dt><dd>As the previous menu, except it starts the playback 1/2 bar before the beginning of the selection</dd>
<dt class="sub1">Start/Continue/Stop</dt><dd>FIXME</dd>
- <dt class="sub1">Play from Edit Point and Return</dt><dd>Starts the playback at the <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">Edit point</a>, and when stopped, goes back to the orginial location</dd>
+ <dt class="sub1">Play from Edit Point and Return</dt><dd>Starts the playback at the <a href="/ardours-interface/the-edit-point-control/">Edit point</a>, and when stopped, goes back to the orginial location</dd>
<dt class="sub1">Play Loop Range</dt><dd>If a <a href="/working-with-markers/loop-range/">Loop range</a> is defined, play it and loop until stopped</dd>
<dt>Start Recording</dt><dd>This is a shortcut to trigger the global recording, and start playback at once</dd>
<dt>Stop and Forget Capture</dt><dd>Stops the recording, removes the newly created material, and goes back to the original position</dd>
<dt class="sub1">Playhead to Active Mark</dt><dd>If a marker is selected, set the position of the playhead at the position of the marker</dd>
<dt class="sub1">Center Playhead</dt><dd>Centers the view on the playhead without changing the zoom level (putting the playhead in the middle of the screen)</dd>
- <dt class="sub1">Nudge Playhead Forward</dt><dd>Shifts the position of the playhead to the right by the amount shown in the <a href="/ardours-interface/the-editor/the-toolbar/the-nudge-controls/">nudge timer</a></dd>
+ <dt class="sub1">Nudge Playhead Forward</dt><dd>Shifts the position of the playhead to the right by the amount shown in the <a href="/ardours-interface/the-nudge-controls/">nudge timer</a></dd>
<dt class="sub1">Nudge Playhead Backward</dt><dd>Same thing, to the left</dd>
<dt class="sub1">Move to Next Transient</dt><dd>When transient have been set, moves the playhead to the next one to the right</dd>
<dt class="sub1">Move to Previous Transient</dt><dd>Same, to the left</dd>
- <dt class="sub1">Playhead to Next Grid</dt><dd>Regardless of the state of the Grid Mode, goes to the next grid to the right, as set by the <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">Snap/Grid unit</a></dd>
+ <dt class="sub1">Playhead to Next Grid</dt><dd>Regardless of the state of the Grid Mode, goes to the next grid to the right, as set by the <a href="/ardours-interface/the-grid-controls/">Snap/Grid unit</a></dd>
<dt class="sub1">Playhead to Previous Grid</dt><dd>Same, to the left</dd>
<dt class="sub1">Playhead to Next Region Boundary</dt><dd>Moves the playhead to the right to the next beginning or end of region on the selected track or, if no track is selected, on all tracks</dd>
<dt class="sub1">Playhead to Previous Region Boundary</dt><dd>Same, to the left</dd>
<dt class="sub1">Playhead to Next Region Boundary (No Track Selection)</dt><dd>Moves the playhead to next beginning or end of region, be it on the selected track or any other</dd>
<dt class="sub1">Playhead to Previous Region Boundary (No Track Selection)</dt><dd>Same, to the left</dd>
- <dt class="sub1">Playhead to Next Region Sync</dt><dd>Moves the playhead to next Region Sync Point, that is by default the beginning of a region but <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">can be moved</a></dd>
+ <dt class="sub1">Playhead to Next Region Sync</dt><dd>Moves the playhead to next Region Sync Point, that is by default the beginning of a region but <a href="/ardours-interface/the-grid-controls/">can be moved</a></dd>
<dt class="sub1">Playhead to Previous Region Sync</dt><dd>Same, to the left</dd>
<dt class="sub1">Jump to Next Mark</dt><dd>moves the playhead to the next <a href="/working-with-markers/creating-location-markers/">marker</a> on the Ruler</dd>
<dt>Cut</dt><dd>Deletes the current selection, but puts it in memory ready to be pasted</dd>
<dt>Copy</dt><dd>Copies the current selection to memory</dd>
- <dt>Paste</dt><dd>Pastes the memory at the <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">edit point</a>, after a Cut or Copy operation</dd>
+ <dt>Paste</dt><dd>Pastes the memory at the <a href="/ardours-interface/the-edit-point-control/">edit point</a>, after a Cut or Copy operation</dd>
<dt>Select</dt>
<dt class="sub1">Select All Objects</dt><dd>Selects all the regions and automation pints in the session</dd>
<dt class="sub1">Deselect All</dt><dd>Deselects all objects or tracks, nothing is selected</dd>
<dt class="sub1">Invert Selection</dt><dd>Select the previously unselected regions, and deselect the previously selected ones</dd>
- <dt class="sub1">Set Range to Loop Range</dt><dd>Creates a range selection on the selected tracks, based on the selected loop markers, and switches to <a href="/ardours-interface/the-editor/the-toolbar/the-toolbox/">Range Mode tool</a></dd>
+ <dt class="sub1">Set Range to Loop Range</dt><dd>Creates a range selection on the selected tracks, based on the selected loop markers, and switches to <a href="/ardours-interface/the-toolbox/">Range Mode tool</a></dd>
<dt class="sub1">Set Range to Punch Range</dt><dd>Same as above, based on the selected punch markers</dd>
<dt class="sub1">Set Range to Selected Regions</dt><dd>Same as above, based on the selected regions (i.e. from the start of the earliest region to the end of the latest one)</dd>
<dt class="sub1">Change Edit Point</dt><dd>Toggles between the mouse and the playhead as the Edit point</dd>
<dt class="sub1">Change Edit Point Including Marker</dt><dd>Toggles between the mouse, the playhead and marker as the Edit point</dd>
<dt>Snap Mode</dt>
- <dt class="sub1">() No Grid</dt><dd>Disables <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">snapping</a>, i.e. allows free movement of regions and boundaries</dd>
+ <dt class="sub1">() No Grid</dt><dd>Disables <a href="/ardours-interface/the-grid-controls/">snapping</a>, i.e. allows free movement of regions and boundaries</dd>
<dt class="sub1">() Grid</dt><dd>Forces snapping, so any move of region boundary will be lined to the grid as chosen</dd>
<dt class="sub1">() Magnetic</dt><dd>If the movement of the region or boundary happens near a grid line, snaps, otherwise, allow free movement</dd>
<dt class="sub1">[] Lock to Video</dt><dd>Same as above, relative to the position in the video</dd>
<dt class="sub1">Set Sync Position</dt><dd>Creates or move the Sync position, i.e. the point of the region that will be aligned or snapped to the grid, and that is (by default) the beggining of the region.</dd>
<dt class="sub1">Remove Sync</dt><dd>Removes any user defined Sync point, and resets the sync position to the beginning of the region</dd>
- <dt class="sub1">Nudge Later</dt><dd>Moves the region to the right by the amount shown in the <a href="/ardours-interface/the-editor/the-toolbar/the-nudge-controls/">nudge timer</a></dd>
+ <dt class="sub1">Nudge Later</dt><dd>Moves the region to the right by the amount shown in the <a href="/ardours-interface/the-nudge-controls/">nudge timer</a></dd>
<dt class="sub1">Nudge Earlier</dt><dd>Same as above, to the left</dd>
<dt class="sub1">Nudge Later by Capture Offset</dt><dd>Moves the region to the right by the capture latency computed by ardour based on the user's settings regarding latency</dd>
<dt class="sub1">Nudge Earlier by Capture Offset</dt><dd>Same as above, to the left</dd>
<dt class="sub1">Normal</dt><dd>Sets the height of the track to its default value which is a trade-off between readability and number of tracks displayed</dd>
<dt class="sub1">Small</dt><dd>Reduces the size of the tracks to a low value, increasing the number of on screen tracks</dd>
- <dt>Toggle Active</dt><dd>Toggles the active state of a track. An inactive track will be grayed and wont play any sound. That can be seen in the <kbd class="menu">A</kbd> colomn of the <a href="/ardours-interface/the-editor/the-editor_s-lists/tracks-and-busses-list/">Tracks and Busses List</a></dd>
+ <dt>Toggle Active</dt><dd>Toggles the active state of a track. An inactive track will be grayed and wont play any sound. That can be seen in the <kbd class="menu">A</kbd> colomn of the <a href="/ardours-interface/editor-lists/tracks-and-busses-list/">Tracks and Busses List</a></dd>
<dt>Remove</dt><dd>Deletes this track and its playlist (no file is harmed in the process, and the regions from the playlist stay in the Editor for later use)</dd>
</dl>
<dt>[] Maximize Mixer Space</dt><dd>Puts the Mixer window in full screen mode</dd>
<dt>Primary Clock</dt>
- <dt class="sub1">Focus On Clock</dt><dd>Sets the focus on the <a href="/ardours-interface/transport-bar-and-times/times/">main clock</a>, allowing to type in numbers directly to change the playhead position</dd>
+ <dt class="sub1">Focus On Clock</dt><dd>Sets the focus on the <a href="/ardours-interface/transport-clocks/">main clock</a>, allowing to type in numbers directly to change the playhead position</dd>
<dt class="sub1">Timecode</dt><dd>Sets the main clock in timecode mode, so it displays time in the Hours:Minutes:Seconds:Frames format</dd>
<dt class="sub1">Bars & Beats</dt><dd>Sets the main clock in musical time mode, so it displays time in the Bars:Beats:Ticks format</dd>
<dt class="sub1">Minutes & Seconds</dt><dd>Sets the main clock in absolute time mode, so it displays time in the Hours:Minutes:Seconds.Milliseconds format</dd>
<dt class="sub1">Zoom Focus Edit Point</dt><dd>Same as above, with the Edit Point</dd>
<dt class="sub1">Next Zoom Focus</dt><dd>Circles between the previous modes</dd>
<dt>Rulers</dt>
- <dt class="sub1">[] Min:Sec</dt><dd>Showss (when checked) or hides a line in <a href="/ardours-interface/the-editor/the-ruler/">the Ruler</a> with the time formatted as Hours:Minutes:Seconds.Milliseconds</dd>
+ <dt class="sub1">[] Min:Sec</dt><dd>Showss (when checked) or hides a line in <a href="/ardours-interface/the-ruler/">the Ruler</a> with the time formatted as Hours:Minutes:Seconds.Milliseconds</dd>
<dt class="sub1">[] Timecode</dt><dd>Same as above, with the time formatted as Hours:Minutes:Seconds:Frames</dd>
<dt class="sub1">[] Samples</dt><dd>Same as the above, with the time displayed in samples from the absolute start</dd>
<dt class="sub1">[] Bars & Beats</dt><dd>Same as the above, with the time formatted as Bars:Beats:Ticks</dd>
<dt class="sub1">Go to View <em>n</em></dt><dd>Loads and displays a saved position (see above)</dd>
<dt>[] Show Editor Mixer</dt><dd>When checked, the selected tracks' mixer strip is displayed on the left of the editor window, allowing for a quick access to e.g. efffects and routing</dd>
- <dt>[] Show Editor List</dt><dd>In the Editor window, shows the <a href="/ardours-interface/the-editor/the-editor_s-lists/">Editor List</a>, giving access to a number of handy lists (regions, tracks, ...)</dd>
- <dt>[] Toggle Mixer List</dt><dd>In the Mixer view, shows the Mixer list, giving access to some handy lists (<a href="/ardours-interface/the-mixer/favorite-plugins-window/">Favorite plugins</a>, <a href="/ardours-interface/the-mixer/the-strips-list/">The Strip list</a>,...)</dd>
+ <dt>[] Show Editor List</dt><dd>In the Editor window, shows the <a href="/ardours-interface/editor-lists/">Editor List</a>, giving access to a number of handy lists (regions, tracks, ...)</dd>
+ <dt>[] Toggle Mixer List</dt><dd>In the Mixer view, shows the Mixer list, giving access to some handy lists (<a href="/ardours-interface/favorite-plugins-window/">Favorite plugins</a>, <a href="/ardours-interface/the-strips-list/">The Strip list</a>,...)</dd>
<dt>[] Toggle Monitor Section Visibility</dt><dd>If the <kbd class="option">Use monitoring section on this session</kbd> has been checked in the <a href="/preferences-and-session-properties/session-properties-dialog/monitoring/">Session Properties window</a>, shows pr hide the Monitor Section in the Mixer</dd>
<dt>[] Show Measure Lines</dt><dd>If checked, in the Editor, shows a vertical white lines at each measure start</dd>
- <dt>[] Show Summary</dt><dd>If checked, in the Editor, shows the <a href="/ardours-interface/the-editor/the-summary/">Summary</a>, allowing a faste navigation in the session</dd>
+ <dt>[] Show Summary</dt><dd>If checked, in the Editor, shows the <a href="/ardours-interface/the-summary/">Summary</a>, allowing a faste navigation in the session</dd>
<dt>[] Show Group Tabs</dt><dd>If checked, makes the groups visible as tabs on the left in the Editor, and on the top in the mixer</dd>
<dt>[] Show Marker Lines</dt><dd>If checked, each marker is extended across all the tracks in the editor with a line of the same color</dd>
</dl>
<dt>Scripting</dt><dd>Opens the <a href="/lua-scripting/"><kbd class="menu">Lua Scripting</kbd> window</a>, allowing to edit and run Lua scripts</dd>
<dt>[] Tracks and Busses</dt><dd>Opens the <kbd class="menu">Tracks and Busses</kbd> window, which is a shortcut to many tracks/busses operations (routing, effects, ...)</dd>
- <dt>[] Locations</dt><dd><dd>Opens the <a href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/"><kbd class="menu">Ranges and Marks</kbd> window</a>, a single point of control for all range and location markers</dd>
+ <dt>[] Locations</dt><dd><dd>Opens the <a href="/ardours-interface/editor-lists/ranges-and-marks-list/"><kbd class="menu">Ranges and Marks</kbd> window</a>, a single point of control for all range and location markers</dd>
<dt>[] Binding Editor</dt><dd>Opens the <a href="/default-keyboard-bindings/"><kbd class="menu">Key Bindings</kbd> window</a>, which allows for easy creation or modification of any keyboard shortcut</dd>
<dt>[] Bundle Manager</dt><dd>Opens the <kbd class="menu">Bundle Manager</kbd> window, allowing to create and manage <em>Bundles</em>, which are a way to simplify connection management, by defining groups of ports</dd>
- <dt>[] Big Clock</dt><dd>Opens the <a href="/ardours-interface/transport-bar-and-times/times/">Main Clock</a> as its own separate (and huge) window, which is helpfull when recording</dd>
+ <dt>[] Big Clock</dt><dd>Opens the <a href="/ardours-interface/transport-clocks/">Main Clock</a> as its own separate (and huge) window, which is helpfull when recording</dd>
<dt>[] Video Monitor</dt><dd>If a <a href="/video-timeline/">video</a> has been imported in the session, opens a video window (namely, <em>Xjadeo</em>), synced to the timeline</dd>
title: Status Bar
---
-
-
-<img src="/images/status-bar.png" alt="The status bar">
+<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>
-
-
-
+<dl>
+ <dt>File:</dt><dd>the file format used in the session, including when recording</dd>
+ <dt>TC:</dt><dd>is the timecode, i.e. the number of frames per second used by the session (for videos)</dd>
+ <dt>Audio:</dt><dd>gives the sample rate used in the session, and the latency computed from the buffer size</dd>
+ <dt>Buffers:</dt><dd>decribe how much data is buffered, see below</dd>
+ <dt>DSP:</dt><dd>for Digital Sound Processing, shows how much of the CPU is used by Ardour and its plugins</dd>
+ <dt>PkBld:</dt><dd><em>(only shows up while creating peaks)</em> displays the number of peak files left to create</dd>
+ <dt>X:</dt><dd>shows the number of xruns since Ardour's launch, see below</dd>
+ <dt>Disk:</dt><dd>reports the remaining hard disk space as the time that can be recorded with the current session setting</dd>
+ <dt>Wall Clock</dt><dd>showing the system time (especially usefull in full screen mode)</dd>
+ <dt>Log button</dt><dd>that indicates if Ardour has encountered any warning or error.</dd>
+</dl>
+
+<p>
+ Right clicking anywhere on the Status Bar allows to choose which of this informations we want displayed, through a checkbox menu.
+</p>
+<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 shown, and red when an error occurs. Clicking the log button gives acces to the log.
+</p>
--- /dev/null
+---
+title: Transport Bar
+---
+
+
+<p>
+ The <dfn>Transport Bar</dfn> groups all the actions regarding the control of playback and recording.
+</p>
+
+<p><img src="/images/transport.png" alt="The transport controls" /></p>
+
+<p>
+ This bar is made of (from left to right):
+</p>
+
+<dl>
+ <dt>Midi Panic</dt><dd>Immediately stops all midi output.</dd>
+ <dt>Enable/disable Audio Click</dt><dd>Toggles (on/off) a click track (metronome) along the <a href="/tempo-meter/tempo-and-meter/">tempo</a>. Right clicking brings up the <kbd class="menu">Click</kbd> submenu from the Preferences.</dd>
+ <dt>Go to Start of the Session</dt><dd>Jumps back at the beginning of the session, as defined by the <a href="/working-with-markers/">start marker</a>.</dd>
+ <dt>Go to End of the Session</dt><dd>Jumps forward to the end of the session, as defined by the <a href="/working-with-markers/">end marker</a>.</dd>
+ <dt>Play Loop Range</dt><dd>Repeats the defined <a href="/controlling-playback/">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.</dd>
+ <dt>Play Range/Selection</dt><dd>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.</dd>
+ <dt>Play from playhead</dt><dd>Starts the playback and optionally record (more below).</dd>
+ <dt>Stop</dt><dd>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.</dd>
+ <dt>Toggle Record</dt><dd>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>.</dd>
+</dl>
+
+<p class="note">
+ All these actions are bound to keyboard shortcuts, which allows for speedier use and more focused work.
+</p>
+
+<p class="note">
+ If you synchronize Ardour with other devices then some or all of these control methods may be unavailable—depending on the synchronization protocol, Ardour may respond only to commands sent from its master device(s).
+</p>
+
+<p>
+ Under these buttons is the <dfn>Shuttle Speed Control</dfn> that allows to scrub through the audio quickly.
+</p>
+
+<p>
+ The Shuttle Speed Control supports 2 operating modes, that can be chosen with right click > Mode:
+</p>
+
+<ul>
+ <li><dfn>Sprung mode</dfn> that allows for a temporary scrub: it only scubs while the mouse is left clicked on the control.</li>
+ <li><dfn>Wheel mode</dfn> that allows to set a playback speed until the "Stop" button is pressed, which stops the playback and resets its speed.</li>
+</ul>
+
+<p>
+ The mode is displayed on the right of the control. The current playback speed is shown by a green slider, that is square and centered when the playback speed is normal (1X) and becomes a circle when its changed. The further from the center the slider is set, the faster the playback will scrub in both directions, as displayed on the left of the control.
+<p>
+
+<p>
+ The 3 vertical buttons on the right of the transport bar control the behaviour of the playhead:
+</p>
+
+<ul>
+ <li>The positional sync button (which might show <dfn>Internal</dfn>, or <dfn>MTC</dfn> or several other values) can be used to control whether or not the transport position and start is controlled by Ardour, or by an external positional synchronization source, such as MIDI Time Code (MTC), Linear Time Code (LTC) or JACK. (see <a href="/synchronization/timecode-generators-and-slaves/">Timecode Generators and Slaves</a>).</li>
+ <li><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 hearing the same piece of audio before and after tweaking it, without having to set a loop range on it.</li>
+</ul>
+
+<h2>Using Key Bindings</h2>
+<p>
+ Ardour has many available commands for playback control that can be bound
+ to keys. Many of them have default bindings, some do not, so the list below
+ shows both the default bindings and internal command names for some of them.
+</p>
+
+<dl class="wide-table">
+ <dt><kbd>Space</kbd></dt><dd>switch between playback and stop.</dd>
+ <dt><kbd>Home</kbd></dt><dd>Move playhead to session start marker</dd>
+ <dt><kbd>End</kbd></dt><dd>Move playhead to session end marker</dd>
+ <dt><kbd>→</kbd></dt><dd>Playhead to next region boundary</dd>
+ <dt><kbd>←</kbd></dt><dd>Playhead to previous region boundary</dd>
+ <dt><kbd>0</kbd></dt><dd>Move playhead to start of the timeline</dd>
+</dl>
+
+Go to the <kdb class="menu">Transport</kbd> and <kdb class="menu">Transport > Playhead</kbd> to find more.
+++ /dev/null
----
-title: Transport bar and times
----
-
-
-<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>
-
-<img src="/images/transport-bar.png" alt="Ardour's transport bar" />
-
-<p class="note">
- If you synchronize Ardour with other devices then some or all of these control methods may be unavailable—depending on the synchronization protocol, Ardour may respond only to commands sent from its master device(s).
-</p>
-
-<p>
- The <dfn>Transport and Times Bar</dfn> at the top of the window is made of:
-</p>
-
-<ul>
- <li>the Transport Controls</li>
- <li>the Clocks</li>
- <li>3 status indicators:
- <ul>
- <li><dfn>Solo</dfn>: Blinks when one or more tracks are being soloed, see <a href="/mixing/muting-and-soloing/">Muting and Soloing</a>. Clicking this button disables any active explicit and implicit solo on all tracks and busses.</li>
- <li><dfn>Audition</dfn>: Blinks when some audio is auditionned, e.g. by using the import dialog, or using the <kbd class="menu">Audition</kbd> context menu in the <a href="/ardours-interface/the-editor/the-editor_s-lists/region-list/">Regions List</a>.</li>
- <li><dfn>Feedback</dfn>: Blinks when Ardour detects a <dfn>feedback loop</dfn>, which happens when the output of an audio signal chain is plugged back to its input. This is probably not wanted and can be dangerous for the hardware and the listener.</li>
- </ul></li>
- <li>A global Meter, showing the level of the Master Output, see <a href="/meters/">Metering in Ardour</a></li>
- <li>the Mode Selector, allowing to switch between Editor and Mixer views, or edit the Preferences.</li>
-</ul>
-
-
-{% children %}
+++ /dev/null
----
-title: The Transport Bar
----
-
-
-<p>
- The <dfn>Transport Bar</dfn> groups all the actions regarding the control of playback and recording.
-</p>
-
-<p><img src="/images/transport.png" alt="The transport controls" /></p>
-
-<p>
- This bar is made of (from left to right):
-</p>
-
-<ul>
- <li>
- <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>.
- </li>
- <li>
- <dfn>Go to Start of the Session</dfn>: Jumps back at the beginning of the session, as defined by the <a href="/working-with-markers/">start marker</a>.
- </li>
- <li>
- <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/">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 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 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="note">
- All these actions are bound to keyboard shortcuts, which allows for speedier use and more focused work.
-</p>
-
-<p>
- Under these buttons is the <dfn>Shuttle Speed Control</dfn> that allows to scrub through the audio quickly.
-</p>
-
-<p>
- The Shuttle Speed Control supports 2 operating modes, that can be chosen with right click > Mode:
-</p>
-
-<ul>
- <li><dfn>Sprung mode</dfn> that allows for a temporary scrub: it only scubs while the mouse is left clicked on the control.</li>
- <li><dfn>Wheel mode</dfn> that allows to set a playback speed until the "Stop" button is pressed, which stops the playback and resets its speed.
-</ul>
-
-<p>
- The mode is displayed on the right of the control. The current playback speed is shown by a green slider, that is square and centered when the playback speed is normal (1X) and becomes a circle when its changed. The further from the center the slider is set, the faster the playback will scrub in both directions, as displayed on the left of the control.
-<p>
-
-<p>
- The 3 vertical buttons on the right of the transport bar control the behaviour of the playhead:
-</p>
-
-<ul>
- <li>
- The positional sync button (which might show <dfn>Internal</dfn>, or <dfn>MTC</dfn> or several other values) can be used to control whether or not the transport position and start is controlled by Ardour, or by an external positional synchronization source, such as MIDI Time Code (MTC), Linear Time Code (LTC) or JACK. (see <a href="/synchronization/timecode-generators-and-slaves/">Timecode Generators and Slaves</a>).
- </li>
- <li>
- <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 hearing the same piece of audio before and after tweaking it, without having to set a loop range on it.
- </li>
-</ul>
-
-<h2>Using Key Bindings</h2>
-<p>
- Ardour has many available commands for playback control that can be bound
- to keys. Many of them have default bindings, some do not, so the list below
- shows both the default bindings and internal command names for some of them.
-</p>
-
-<dl class="wide-table">
- <dt><kbd>Space</kbd></dt>
- <dd>switch between playback and stop.</dd>
- <dt><kbd>Home</kbd></dt>
- <dd>Move playhead to session start marker</dd>
- <dt><kbd>End</kbd></dt>
- <dd>Move playhead to session end marker</dd>
- <dt><kbd>→</kbd></dt>
- <dd>Playhead to next region boundary</dd>
- <dt><kbd>←</kbd></dt>
- <dd>Playhead to previous region boundary</dd>
- <dt><kbd>0</kbd></dt>
- <dd>Move playhead to start of the timeline</dd>
-</dl>
-
-Go to the <kdb class="menu">Transport</kbd> and <kdb class="menu">Transport >> Playhead</kbd> to find more.
+++ /dev/null
----
-title: The Editor
----
-
-<figure>
- <img src="/images/detailed-editor-window.png" alt="Ardour's editor window">
- <figcaption>
- <ol class="multicol4">
- <li>Toolbar</li>
- <li>Rulers</li>
-</ol><ol class="multicol4" start="3">
- <li>Editor's List</li>
- <li>a Mixer strip</li>
-</ol><ol class="multicol4" start="5">
- <li>Summary</li>
- <li>an audio track</li>
- </ol>
-</ol><ol class="multicol4" start="7">
- <li>a MIDI track</li>
- <li>automation</li>
- </ol>
-
- </figcaption>
-</figure>
-
-<p>
- The <dfn>Editor</dfn> window includes the editor track <dfn>canvas</dfn>
- where you can arrange audio and MIDI data along a timeline. This is the
- window you will be in while editing and arranging a project. The window
- has a general "horizontal" sense to it: the timeline flows from left to
- right, the playhead showing the current position in the session moves
- from left to right — the window really represents <dfn>time</dfn>
- in a fairly literal way.
-</p>
-
-<p>
- It is possible to show a single channel strip in the editor window, and
- some people find this enough to work on mixing without actually opening
- the mixer window. Most of the time though, you will want both of these
- windows at various stages of a session's lifetime — sometimes
- you'll be focused on editing, sometimes on mixing and possibly some of
- the time on both.
-</p>
-
-<p>
- This section is a description of the different sections of the Editor window.
- To learn more about the editing workflow, see <a href="/editing-and-arranging/">Editing and Arranging</a>.
-</p>
-
-
-{% children %}
-
-
+++ /dev/null
----
-title: The Toolbar
----
-
-
-<figure>
- <img src="/images/toolbar_split.png" alt="Ardour's editor toolbar">
- <figcaption>
- <ol class="multicol5">
- <li>Toolbox</li>
- </ol><ol class="multicol5" start="2">
- <li>Zoom Control</li>
- </ol><ol class="multicol5" start="3">
- <li>Grid Control</li>
- </ol><ol class="multicol5" start="4">
- <li>Edit Point</li>
- </ol><ol class="multicol5" start="5">
- <li>Nudge</li>
- </ol>
- </figcaption>
-</figure>
-
-<p>
- The Toolbar is made of 5 parts, described in this part.
-</p>
-
-
-{% children %}
-
--- /dev/null
+---
+title: Transport Clocks
+---
+
+<img src="/images/new_main_clocks.png" alt="An image of the transport clocks in Ardour" />
+
+<p>
+ <dfn>Clocks</dfn> in Ardour are used to display <dfn>time values</dfn> precisely.
+ In many cases, they are also one way to edit (change) time values, and in a few
+ cases, the only way. All clocks share the same basic appearance and functionality,
+ which is described below, but a few clocks serve particularly important roles.
+</p>
+<p>
+ In the transport bar of the editor window there are two clocks (unless you
+ are on a very small screen), that display the current position of the playhead
+ and additional information related to transport control and the timeline. These
+ are called the <dfn>transport clocks</dfn>; the left one is the primary
+ transport clock and the right one is the secondary transport clock.
+</p>
+<p>
+ All the clocks in Ardour share the same powerfull way of editing time. Refer to
+ <a href="/introducing-ardour/basic-gui-operations/editing-clocks/">Editing Clocks</a> to learn how.
+</p>
+<p>
+ Editing the time in the transport clocks will reposition the playhead in the same
+ way that various other editing operations will.
+</p>
+
+<h2>The Special Role of the Secondary Transport Clock</h2>
+
+<p>
+ On a few occasions Ardour needs to display time values to the user, but there
+ is no obvious way to specify what units to use. The most common case is the big
+ cursor that appears when dragging regions. For this and other similar cases,
+ Ardour will display time using the same units as the secondary clock.
+</p>
+
+<h2>Why are there two transport clocks?</h2>
+
+<p>
+ Having two transport clocks lets you see the playhead position in two different
+ time units without having to change any settings. For example, you can see the
+ playhead position in both timecode units and BBT time.
+</p>
+
+<h2>Special Modes for the Transport Clocks</h2>
+
+<p>
+ In addition to the time-unit modes, each of the two transport
+ clocks (if you work on a small screen, you may only have one) can be
+ independently set to display <dfn>Delta to Edit Point</dfn> in whatever time
+ units its current mode indicates. This setting means that the clock shows the
+ distance between the playhead and the current edit point, and it may show a
+ positive or negative value depending on the temporal order of these two points.
+ The clocks will use a different color when in this mode to avoid confusion.
+</p>
+
+<p>
+ To switch either (or both!) of the transport clocks into this mode, use
+ <kbd class="menu"> Edit > Preferences > Transport</kbd> and select
+ the relevant checkboxes.
+</p>
+
+<p>
+ Note that when in <samp>Delta to Edit Point</samp> mode, the transport clocks
+ cannot be edited.
+</p>
+
+
+<h2>The Big Clock</h2>
+
+<p>
+ To show the current playhead position in a big, resizable window, activate
+ <kbd class="menu">Window > Big Clock</kbd>. The big clock is very useful
+ when you need to work away from the screen but still want to see the playhead
+ position clearly (such as when working with a remote control device across
+ a room). The big clock will change its visual appearance to indicate when active
+ recording is taking place. Below on the left is a screenshot showing a fairly
+ large big clock window filling a good part of the display, and on the right,
+ the same clock during active recording.
+</p>
+
+<a href="/images/bigclock.png"><img src="/images/bigclock.png" height="100" alt="an image of the big clock filling a screen"></a>
+<a href="/images/bigclock-recording.png"><img src="/images/bigclock-recording.png" height="100" alt="an image of the big clock while recording"></a>
--- /dev/null
+---
+title: Selection and Punch Clocks
+---
+
+<img src="/images/selectionpunchclocks.png" alt="An image of the the selection and punch clocks in Ardour" />
+
+<p>
+ The transport bar contains a set of 5 clocks that show the current
+ <dfn>selection range</dfn> and <dfn>punch ranges</dfn>.
+</p>
+<p>
+ Clicking on the punch range clocks will locate to either the beginning or end of the punch range.
+ Similarly, clicking on the range clocks will locate to either the beginning
+ or end of the current selection. In this screen shot there is no current
+ selection range, so the selection clocks show an "off" state.
+</p>
+<p>
+ The <kbd class="menu">In</kbd> and <kbd class="menu">Out</kbd> buttons relate
+ to the Punch range, and allow to use only one of the two punch boundaries, or both:
+</p>
+<dl>
+ <dt>In only</dt><dd>Records from the In marker on, without a end boundary</dd>
+ <dt>Out only</dt><dd>Records untils the Out marker, without a beginning boundary</dd>
+ <dt>In only</dt><dd>Records only between the In and Out markers</dd>
+</dl>
+<p>
+ <kbd class="mouse">Right</kbd> clicking on any of the 5 clocks brings up a context menu
+ allowing to change the type of time display between the <a href="/introducing-ardour/basic-gui-operations/editing-clocks/">
+ 4 clock modes</a>, and to copy the selected clock's time to the clipboard.
+</p>
+++ /dev/null
----
-title: The Mixer
----
-
-<figure>
- <img src="/images/detailed-mixer-window.png" alt="Ardour's mixer window">
- <figcaption>
- <ol class="multicol3">
- <li>Favorite Plugins</li>
- <li>Strip List</li>
-</ol><ol class="multicol3" start="3">
- <li>Group list</li>
- <li>a track's strip</li>
-</ol><ol class="multicol3" start="5">
- <li>Master strip</li>
- <li>Monitor section</li>
- </ol>
- </figcaption>
-</figure>
-
-<p>
- The <dfn>Mixer</dfn> window represents signal flow and
- is the window you will probably be using most when mixing a session. It
- includes <dfn>channel strips</dfn> for each track and bus in your session.
- It has a general "vertical" sense to it: signals flow from the top of each
- channel strip through the processing elements in the strip to reach the
- output listed at the bottom.
-</p>
-
-<p>This section describes the Mixer. To learn more about the process of mixing, see
-<a href="/mixing/">Mixing<a>.</p>
-
-
-
-
-
-
-
-{% children %}
-
+++ /dev/null
----
-title: The Monitor section
----
-
-<img class="right" src="/images/monitoring-strip.png" alt="The Monitoring strip">
-
-<p>
- The <dfn>Monitoring section</dfn> can be activated for the session by using the
- <a href="/preferences-and-session-properties/session-properties-dialog/monitoring/">
- <kbd class="menu">Session > Properties</kbd> window</a> and checking the
- <kbd class="option">Use monitor section in this session</kbd> in the
- <kbd class="menu">Monitoring</kbd> tab.
-</p>
-<p>
- The Monitoring section appears on the right of the Mixer, and comprises:
-</p>
-<ol>
- <li>A detach/attach button, to make it its own window or include it into the Mixer</li>
- <li>Three status indicators for the current session state</li>
- <li>Current solo behaviour</li>
- <li>The Processors button and optional processor box</li>
- <li>Three volume knobs controlling the playback</li>
- <li>The channels On/Off switches controlling options on each channels independantly</li>
- <li>Controls for solo/mute levels: Gain increase for solo, gain reduction non-soloed, gain reduction for dimming</li>
- <li>The global monitoring gain knob</li>
- <li>Output connection selector</li>
-</ol>
-
-<p class="note">
- Different settings in Ardour will result in different monitoring results. Refer to the
- <a href="/appendix/monitor-modes/">Monitor Modes Appendix</a> to learn more.
-</p>
-
-<h2>The Status buttons</h2>
-
-<p>
- The Status buttons, two of which appears in <a href="/ardours-interface/transport-bar-and-times/">the Transport Bar</a>, blink to inform the user if something special is happening:
-</p>
-<ul>
- <li><dfn>Solo</dfn>: Blinks when one or more tracks are being soloed, see <a href="/mixing/muting-and-soloing/">Muting and Soloing</a>. Clicking this button disables any active explicit and implicit solo on all tracks and busses.</li>
- <li><dfn>Audition</dfn>: Blinks when some audio is auditionned, e.g. by using the import dialog, or using the <kbd class="menu">Audition</kbd> context menu in the <a href="/ardours-interface/the-editor/the-editor_s-lists/region-list/">Regions List</a>. Clicking this button will stop the audition</li>
- <li><dfn>Isolated</dfn>: Blinks when one or more tracks are being solo isolated, i.e. when tracks or busses are soloed the isolated ones will not mute. Clicking this button disables any active isolated solo(s).</li>
-</ul>
-
-<h2>The Current solo behavior switches</h2>
-
-<p>
- All the following buttons are switches, that can be ON or OFF (as shown by their yellow led):
-</p>
-<dl>
- <dt>SiP</dt><dd><em>Solo In Place</em> is the default solo mode of Ardour. It routes the tracks/busses through their actual audio path and through the master, so its panning and effects are audible</dd>
- <dt>PFL</dt><dd><em>Pre Fader Listen</em> is a solo routed from the point just before the fader of the soloed tracks/busses, bypassing the fader, the post-fader effects, the panner and the master</dd>
- <dt>AFL</dt><dd><em>After Fade Listen</em> is a solo routed from the point just before the panner of the tracks/busses, bypassing the panner and the master</dd>
- <dt>Excl. Solo</dt><dd><em>Exclusive Solo</em> only one track or bus will ever be soloed at once; soloing track B while track A is currently soloed will un-solo track A before soloing track B</dd>
- <dt>Solo » Mute</dt><dd>If a track is both soloed and muted, determines if Solo preempts mute. When activated, a muted and soloed track will be audible.</dd>
-</dl>
-
-<p>
- Changing the solo mode (SiP, PFL or AFL) will update the labels on the mixer strips' labels accordingly.
-</p>
-
-<h2>The Processors button</h2>
-
-<p>
- The <dfn>Processors</dfn> button makes the processor box visible for the monitoring section. This processor box works exactly as the one
- present in the <a href="/ardours-interface/the-mixer/audio-midi-mixer-strips/">tracks</a> and
- <a href="/ardours-interface/the-mixer/busses-mixer-strips/">busses</a> strips, and any effects can be added.
-</p>
-<p>
- This only affects auditionning, so it won't be present in e.g. an audio export of the session.
- It is in particular very usefull to put some meters, like <a href="https://github.com/x42/meters.lv2/">needle-style</a>
- ones, or any mesurement ones, like a frequency analysis.
-</p>
-
-
-<h2>The Volume Knobs</h2>
-
-<p>
- These 3 buttons affect the volume of the monitoring. They are made of a knob, and a
- dropdown menu showing some commonly used presets.
-</p>
-<dl>
- <dt>Solo Boost</dt><dd>If some track(s)/bus(ses) are soloed, increases their volume by that amount</dd>
- <dt>SiP Cut</dt><dd>When is Solo in Place mode, affects the volume of the rest of the audio (the non-soloed audio). The default is -&infinity; dB, i.e. the non soloed tracks are totally inaudible. It can be raised to make the other tracks audible, though dimmed ("<em>Solo in Front</em>").</dd>
- <dt>Dim</dt><dd>When the monitoring is dimmed (see bellow the Dim buttons), determines how intense the dimming is, i.e. from how much the signal is diminished</dd>
-</dl>
-
-<h2>The Channels Switches</h2>
-
-<p>
- For each of the channels, (e.g. <kbd class="menu">L</kbd> and <kbd class="menu">R</kbd> for stereo), 4 switches are available:
-</p>
-<dl>
- <dt>Mute</dt><dd>Mutes the selected channel(s)</dd>
- <dt>Dim</dt><dd>Reduces the selected channel(s)' volume, as per the <kbd class="menu">Dim</kbd> knob above</dd>
- <dt>Solo</dt><dd>Soloes the selected channel(s)</dd>
- <dt>Inv</dt><dd>Inverts the selected channel(s)' polarity</dd>
-</dl>
-
-<h2>The Global Monitoring Options buttons</h2>
-
-<p>
- Those buttons directly affect the output of the monitoring section:
-</p>
-<ul>
- <li><dfn>Mono</dfn>: Reduces the monitoring signal to mono.</li>
- <li><dfn>Dim</dfn>: Reduces the selected monitoring volume, as per the <kbd class="menu">Dim</kbd> knob above</li>
- <li><dfn>Mute</dfn>: Mutes all monitoring.</li>
-</ul>
-
-<h2>The Global Monitoring Gain Knob</h2>
-
-<p>
- This knob is the gain knob for all the monitoring section. The dropdown menu below
- presents the user with a choice of current presets for monitoring volumes.
-</p>
-
-<h2>The Monitoring Output connection selector</h2>
-
-<p>
- As for all the strips in the mixer, the outputs of the monitoring, by default
- connected to the system's outputs, can be plugged to any combination of tracks,
- busses, or output the user wants, with the <a href="/signal-routing/Patchbay/">Routing Grid</a>.
- It is particularly helpfull here, because the monitoring signal is often fed to
- the control room speakers without interrupting the normal flow of the mix.
-</p>
--- /dev/null
+---
+title: Status indicators and Mode buttons
+---
+
+<img src="/images/status-and-mode-buttons.png" alt="The Status buttons, the Mode buttons and " />
+
+<p>
+ The <dfn>Status</dfn> buttons show the current session state:
+</p>
+
+<dl>
+ <dt>Solo</dt><dd>Blinks when one or more tracks are being soloed, see <a href="/mixing/muting-and-soloing/">Muting and Soloing</a>. Clicking this button disables any active explicit and implicit solo on all tracks and busses. Clicking this button desactivates the solo on every track/bus.</dd>
+ <dt>Audition</dt><dd>Blinks when some audio is auditionned, e.g. by using the import dialog, or using the <kbd class="menu">Audition</kbd> context menu in the <a href="/ardours-interface/editor-lists/region-list/">Regions List</a>. Clicking this button stops the auditionning.</dd>
+ <dt>Feedback</dt><dd>Blinks when Ardour detects a <dfn>feedback loop</dfn>, which happens when the output of an audio signal chain is plugged back to its input. This is probably not wanted and can be dangerous for the hardware and the listener.</dd>
+</dl>
+
+<p>
+ The Mode Selector allows switching between Editor, Mixer and the Preferences window.
+ If a window is detached, the corresponding button is lit in blue. Clicking the botton
+ switches the detached window visibility.
+</p>
+
+<p>
+ The global meter shows the levels of the master's output. Its the same meter that sits
+ in the <a href="/ardours-interface/the-master-bus-strip/">Master's Mixer strip</a>,
+ and also shows a peak indicator, that turns red when any level exceeds 0dB. It can
+ be reset by a <kbd class="mouse">Left</kbd> click.
+</p>
---
-title: The Toolbox
+title: Toolbox
---
<img src="/images/toolbar-tools.png" alt="Editor toolbar's tools, aka toolbox">
If <kbd class="menu">Snap To Grid</kbd> is enabled, then regions can
only move so that they align with locations determined by the current
snap settings (beats, or seconds, or other region boundaries, etc).
- See <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">Snap To the Grid</a>
+ See <a href="/ardours-interface/the-grid-controls/">Snap To the Grid</a>
for details.
</p>
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>
</dl>
-
-
---
-title: The Zoom Controls
+title: Zoom Controls
---
<li><dfn>Mouse</dfn></li>
- <li><dfn>Edit Point</dfn> as set in the <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">Edit point</a> control.</li>
+ <li><dfn>Edit Point</dfn> as set in the <a href="/ardours-interface/the-edit-point-control/">Edit point</a> control.</li>
</ul>
tracks are not contiguous, the unselected tracks inbetween will be hidden, see
- the <a href="/ardours-interface/the-editor/the-editor_s-lists/tracks-and-busses-list/">Track and Bus list</a>.</li>
+ the <a href="/ardours-interface/editor-lists/tracks-and-busses-list/">Track and Bus list</a>.</li>
<li><dfn>All</dfn> that fits all the tracks of the sessions vertically (provided
---
-title: The Grid Controls
+title: Grid Controls
---
you are going to use any of the Region grid units.
</p>
-
-
-
-
-
---
-title: The Edit Point Control
+title: Edit Point Control
---
unit selector.
</p>
-
-
-
-
-
---
-title: The Nudge Controls
+title: Nudge Controls
---
used to move the playhead backward or forward by the amount shown on the clock.
</p>
-
-
-
-
-
-
-
---
-title: The Ruler
+title: Ruler
---
<img src="/images/ruler.png" alt="Ardour's Ruler">
</dl>
<p>Most of the operations on the markers are described in <a href="/working-with-markers/">Working with Markers</a>, while the Meter, Tempo, Bars:Beats and Timecode use are described in <a href="/tempo-meter/tempo-and-meter/">Tempo and Meter</a>.</p>
-
-
-
-
-
-
-
---
-title: The Summary
+title: Summary
---
---
-title: The Editor's Lists
+title: Editor Lists
---
-
-
<p>
-
- At the right of the editor window is an optional area which provides one of a
-
+ At the right hand side 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
-
right-hand side of the list gives a selection of tabs which are used to
-
choose the list to view. The left-hand border of the list can be dragged to
-
vary the width of the list.
-
</p>
-
-
-
-
-
{% children %}
-
---
-title: Region List
+title: The Region List
---
A handy feature of the region list is that its regions can be dragged and dropped into a suitable track in the session.
</p>
-
-
-
---
-title: Tracks and Busses List
+title: The Tracks and Busses List
---
As with the region list, hovering the mouse pointer over a column heading shows a tool-tip which can be handy to remember what the columns are for.
</p>
-
-
-
---
-title: Snapshot List
+title: The Snapshot List
---
information on snapshots.
</p>
-
-
-
---
-title: Track and Bus Group List
+title: The Track and Bus Group List
---
<dd>whether the constituents share active status. </dd>
</dl>
-
-
-
---
-title: Ranges and Marks List
+title: The Ranges and Marks List
---
-
-
<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/transport-bar-and-times/times/">clock widgets</a></dfn>
-
- which display
-
- the location of a marker, or the start, end, and duration times of a range,
-
- respectively.<br />
-
+ href="/introducing-ardour/basic-gui-operations/editing-clocks/">clock widgets</a></dfn>
+ which display the location of a marker, or the start, end, and duration times of a range,
+ respectively.
+</p>
+<p>
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 />
-
+ clock context menus.
+</p>
+<p>
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 />
-
+ and Samples.
</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 />
-
+ active however, and can be used normally.
+</p>
+<p>
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>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
<p class="note">
When favorites are added with the <a href="/working-with-plugins/plugin-manager">Plugin Manager</a>, they are appended to the bottom of the list.
</p>
-
-
-
-
-
-
-
---
-title: The Strips List
+title: Strips List
---
<p>
It is a list of all the tracks, busses and VCA in the session, with a tick to allow
for hiding or showing them. This visibility status also affects the Editor view, and is exactly the same as
toggling the <kbd class="option">V</kbd> checkbox in the
- <a href="/ardours-interface/the-editor/the-editor_s-lists/tracks-and-busses-list/">Tracks and Busses</a>
+ <a href="/ardours-interface/editor-lists/tracks-and-busses-list/">Tracks and Busses</a>
panel of the Editor List.
</p>
---
-title: The Groups list
+title: Groups list
---
<p>
</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="/ardours-interface/the-editor/the-editor_s-lists/tracks-and-busses-list/">Tracks and Busses list</a>
+ one can either go to the <a href="/ardours-interface/editor-lists/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="/ardours-interface/the-mixer/the-strips-list/">Strips list</a>.
+ <a href="/ardours-interface/the-strips-list/">Strips list</a>.
</li>
</ul>
<p>
<h2>Description</h2>
<p>
- Busses look and behave exactly like tracks, so they share nearly <a href="/ardours-interface/the-mixer/audio-midi-mixer-strips/">all of their controls</a>.
+ Busses look and behave exactly like tracks, so they share nearly <a href="/ardours-interface/audio-midi-mixer-strips/">all of their controls</a>.
The differences are :
</p>
<ul>
---
-title: The Master Bus Strip
+title: Master Bus Strip
---
<img class="right" src="/images/master-strip.png" alt="The Master strip in the mixer">
--- /dev/null
+---
+title: Monitor section
+---
+
+<img class="right" src="/images/monitoring-strip.png" alt="The Monitoring strip">
+
+<p>
+ The <dfn>Monitor section</dfn> is an optional feature that provides Control Room/Monitor Speaker outputs. It can be activated for the current session in the
+ <a href="/preferences-and-session-properties/session-properties-dialog/monitoring/">
+ <kbd class="menu">Session > Properties</kbd> window</a> by enabling the
+ <kbd class="option">Use monitor section in this session</kbd> option in the
+ <kbd class="menu">Monitoring</kbd> tab. By default the Monitor Section is fed with audio from the Master Buss, but depending on solo mode and other functions such as Auditioning, other audio sources may be temporarily heard instead.
+</p>
+<p>
+ The Monitor section appears on the right hand side of the Mixer, and comprises:
+</p>
+<ol>
+ <li>Detach/attach control. This separates the Monitor section into its own floating window</li>
+ <li>Status indicators for important functions</li>
+ <li>Solo behaviour selection</li>
+ <li>Show, hide and status of the Monitor Sections inline processors</li>
+ <li>Level controls for solo functionality</li>
+ <li>Level control for Monitor Dim</li>
+ <li>Individual monitor path controls</li>
+ <li>Mute, Dim and Mono functions for the monitor outputs</li>
+ <li>Monitor level control</li>
+ <li>Monitor output routing</li>
+</ol>
+
+<h2>Status Indicators</h2>
+
+<p>
+ The Status indicators, two of which also appear in <a href="/ardours-interface/">the Transport tool bar</a>, flash to indicate when that function is in operation:
+</p>
+<ul>
+ <li><dfn>Soloing</dfn>: This indicates when one or more tracks or busses are currently being soloed. See <a href="/mixing/muting-and-soloing/">Muting and Soloing</a>. Clicking on this indicator cancels all currently soloed channels or busses</li>
+ <li><dfn>Auditioning</dfn>: This indicates when an audio file is being listened to directly, e.g. when using the import dialogue, or using the <kbd class="menu">Audition</kbd> context menu in the <a href="/ardours-interface/editor-lists/region-list/">Regions List</a>. Clicking this indicator cancels the current audition</li>
+ <li><dfn>Isolated</dfn>: This indicates when one or more tracks or busses are solo isolated. See <a href="/mixing/muting-and-soloing/">Muting and Soloing</a>. Clicking on this indicator cancels any current isolation.</li>
+</ul>
+
+<h2>Solo behaviour selection</h2>
+
+<p>
+ The SiP, PFL and AFL controls inter-cancel with each other and select the desired Solo mode. Excl. Solo and Solo Mute then modify the modes behaviour. See <a href="/mixing/muting-and-soloing/">Muting and Soloing</a>. The current mode is indicated by the illuminated 'LED' on the button.
+</p>
+<dl>
+ <dt>SiP</dt><dd>This selects <em>Solo In Place</em> as the current solo mode and cancells the previous mode.</dd>
+ <dt>PFL</dt><dd>This selects <em>Pre Fade Listen</em> as the current solo mode and cancells the previous mode.</dd>
+ <dt>AFL</dt><dd>This selects <em>After Fade Listen</em> as the current solo mode and cancells the previous mode.</dd>
+ <dt>Excl. Solo</dt><dd>This enables or disables the <em>Exclusive Solo</em> option.</dd>
+ <dt>Solo » Mute</dt><dd>This enables or disables the <em>Solo Mute</em> option.</dd>
+</dl>
+
+<p>
+ Note : Changing the solo mode (SiP, PFL or AFL) will update the labels on the mixer strips' solo controls accordingly.
+</p>
+
+<h2>The Processors button</h2>
+
+<p>
+ Clicking the <dfn>Processors</dfn> button show or hides the Monitor Sections processor box. This is used in the same way as processor boxes present in <a href="/ardours-interface/audio-midi-mixer-strips/">tracks</a> and
+ <a href="/ardours-interface/busses-mixer-strips/">busses</a>. It can be used to insert pugins, e.g. a room correction EQ or a specific metering type.
+</p>
+<p>
+ As this processing is local to the Monitor Section it is only applied to audio that is ultimately available at the monitor outputs.
+</p>
+
+
+<h2>Solo level controls</h2>
+
+<p>
+ These controls set the level of the audio when a channel or bus solo is engaged.
+</p>
+<dl>
+ <dt>Solo Boost</dt><dd>This is the level that will be added to the current main monitor level when a track or bus is soloed, providing a conveniant boost in level for the isolated signal. The rotary control has a range of 0dB to +10dB and can be set at any point between these two values. A drop down menu with pre-defined values is also provided for convenience.</dd>
+ <dt>SiP Cut</dt><dd>Only relevant to Solo in Place mode. This sets the level that all muted tracks or busses will be muted by. By default it is -&infinity; i.e. the non soloed tracks are totally inaudible. The level can be raised to make the other tracks audible, though dimmed. This is also sometimes referred to <em>Solo in Front</em>. The rotary control has a range of -inf to +0dB and can be set at any point between these two values. A drop down menu with pre-defined values is also provided for convenience.</dd>
+</dl>
+
+<h2>Dim level control</h2>
+
+<p>
+ The Dim level control sets the amount by which the monitoring will be reduced when a Dim button is engaged. The rotary control has a range of -20dB to 0dB and can be set at any point between these two values. A drop down menu with pre-defined values is also provided for convenience.
+</p>
+
+<h2>Monitor path controls</h2>
+
+<p>
+ Each of the individual paths through the Monitor Section, (e.g. <kbd class="menu">L</kbd> and <kbd class="menu">R</kbd> for stereo), can be controlled individually. Four functions are available:
+</p>
+<dl>
+ <dt>Mute</dt><dd>Mutes the selected path(s)</dd>
+ <dt>Dim</dt><dd>Reduces the selected path(s) level by the amount set with the Dim level control</dd>
+ <dt>Solo</dt><dd>Soloes the selected channel(s)</dd>
+ <dt>Inv</dt><dd>Inverts the selected channel(s) polarity</dd>
+</dl>
+
+<h2>Global Monitor controls</h2>
+
+<p>
+ Those buttons directly affect the output of the monitoring section:
+</p>
+<ul>
+ <li><dfn>Mono</dfn>: sums all of the paths to a single mono signal and applies it to all Monitor Section outputs.</li>
+ <li><dfn>Dim</dfn>: Reduces overall monitor level by the amount set with the Dim level control.</li>
+ <li><dfn>Mute</dfn>: Mutes all monitoring.</li>
+</ul>
+
+<h2>Global Monitor level</h2>
+
+<p>
+ This control sets the level for Monitor Section output. The rotary control has a range of -inf to +6dB and can be set at any point between these two values. A drop down menu with pre-defined values is also provided for convenience.
+</p>
+
+<h2>Monitoring Output routing</h2>
+
+<p>
+ Clicking on this button shows a menu that allows quick and convenient routing of the Monitor Section's outputs to audio hardware outputs, e.g. to feed control room monitors.
+ It also has an option to open Ardours routing matrix, where more detailed connectivity is available if routing to something other than hardware is required.
+</p>
<h3>Positioning the playhead with the transport clocks</h3>
<p>
Click on either the primary or secondary transport clock and
- <a href="/ardours-interface/transport-bar-and-times/times/">edit their value</a>
+ <a href="/introducing-ardour/basic-gui-operations/editing-clocks/">edit their value</a>
to move the playhead to a specific position.
</p>
</p>
<p>
For details see
- <a href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/">Ranges & Marks
- List</a>
- and <a href="/ardours-interface/transport-bar-and-times/times/"> Using
- Ardour Clock Displays</a>.
+ <a href="/ardours-interface/editor-lists/ranges-and-marks-list/">Ranges & Marks List</a>
+ and <a href="/introducing-ardour/basic-gui-operations/editing-clocks/">Editing Clocks</a>.
</p>
</p>
<p>
It can be defined via the timeline or the <a
- href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/">Ranges & Marks
+ href="/ardours-interface/editor-lists/ranges-and-marks-list/">Ranges & Marks
list</a>.
</p>
<dt>Hide</dt>
<dd>Hide this marker from the view. It can be made visible again from the
<kbd class="menu">Window > Locations</kbd> window or the <a
- href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/">Ranges & Marks
+ href="/ardours-interface/editor-lists/ranges-and-marks-list/">Ranges & Marks
list</a>.</dd>
<dt>Rename</dt>
<dd>Change the name of the marker.</dd>
</p>
<p>
It can be defined on the timeline or in the
- <a href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/">Ranges & Marks</a>
+ <a href="/ardours-interface/editor-lists/ranges-and-marks-list/">Ranges & Marks</a>
list.
</p>
<h2>Switching to a Snapshot</h2>
<p>
If you are already working on a session and want to to switch to an
- existing snapshot, navigate the <a href="/ardours-interface/the-editor/the-editor_s-lists/snapshot-list/">Snapshot List</a>.
+ existing snapshot, navigate the <a href="/ardours-interface/editor-lists/snapshot-list/">Snapshot List</a>.
Find the name of the snapshot in the list and click it. Ardour will switch
to the snapshot. If there are unsaved changes in the current session, Ardour will
ask what you want to do.
(shortcut: <kbd class="mod1">↓</kbd>).
</p>
<p>
- Alternatively, you can use the <a href="/ardours-interface/the-editor/the-editor_s-lists/tracks-and-busses-list/"><kbd class="menu">Tracks & Busses</kbd>
+ Alternatively, you can use the <a href="/ardours-interface/editor-lists/tracks-and-busses-list/"><kbd class="menu">Tracks & Busses</kbd>
panel of the Editor Lists</a>, if visible.
Here, you can freely drag-and-drop tracks and busses into any order you prefer.
</p>
Group menu. The menu lists the available groups. Selecting one of these
groups will add the track or bus to that group. The menu also lets you
create a new group.</li>
- <li>Finally, the <a href="/ardours-interface/the-mixer/the-groups-list/">Groups list</a>
+ <li>Finally, the <a href="/ardours-interface/the-groups-list/">Groups list</a>
has a <kbd class="menu">plus (+)</kbd> button at the
bottom of the list. Click on the plus sign to create a new group.</li>
</ul>
the members of a group.
</p>
<p>
- You can also remove groups by selecting them in the <a href="/ardours-interface/the-mixer/the-groups-list/">Groups list</a>
+ You can also remove groups by selecting them in the <a href="/ardours-interface/the-groups-list/">Groups list</a>
and then pressing the <kbd class="menu">minus (-)</kbd> button at the bottom of the list.
</p>
<a href="/working-with-tracks/bus-controls/#mute"><kbd class="option">Muting</kbd></a>,
<a href="/working-with-tracks/bus-controls/#solo"><kbd class="option">Soloing</kbd></a>,
<a href="/working-with-tracks/audio-track-controls/#record"><kbd class="option">record enable</kbd></a>,
- <a href="/ardours-interface/the-editor/the-editor_s-lists/tracks-and-busses-list/"><kbd class="option">active state</kbd></a>,
+ <a href="/ardours-interface/editor-lists/tracks-and-busses-list/"><kbd class="option">active state</kbd></a>,
<a href="/working-with-tracks/controlling-track-appearance/track-coloring/"><kbd class="option">colour</kbd></a> and
<a href="/recording/monitoring/"><kbd class="option">monitoring</kbd></a>
are all straightforward. They simply mean that all member tracks or busses will
<dd>
<dl class="narrower-table">
<dt>Play from Edit Point</dt>
- <dd>Play from the location of the current <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">edit point</a>.</dd>
+ <dd>Play from the location of the current <a href="/ardours-interface/the-edit-point-control/">edit point</a>.</dd>
<dt>Play from Start </dt>
<dd>Play from the start of the session</dd>
<dt>Play Region(s)</dt>
</p>
<p>
New files will be inserted at either the file timestamp (if available,
- zero by default), at the <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">edit point</a>, at the
+ zero by default), at the <a href="/ardours-interface/the-edit-point-control/">edit point</a>, at the
playhead, or at the start of the session, as specified in <kbd
class="menu">Insert at...</kbd>.
</p>
<h2>Select a Region</h2>
<p>
Confirm that you are using the
- <a href="/ardours-interface/the-editor/the-toolbar/the-toolbox/">Grab Mode tool</a>,
+ <a href="/ardours-interface/the-toolbox/">Grab Mode tool</a>,
then click on a region to select it. If
- <a href="/ardours-interface/the-editor/the-toolbar/the-toolbox/">Smart mode</a>
+ <a href="/ardours-interface/the-toolbox/">Smart mode</a>
is enabled, click in the lower half of the region.
</p>
<h2>Deselect a Region</h2>
<p>
Confirm you are using the
- <a href="/ardours-interface/the-editor/the-toolbar/the-toolbox/">Grab Mode tool</a>,
+ <a href="/ardours-interface/the-toolbox/">Grab Mode tool</a>,
then <kbd class="mouse mod1">Left</kbd>-click the region. If
- <a href="/ardours-interface/the-editor/the-toolbar/the-toolbox/">Smart mode</a>
+ <a href="/ardours-interface/the-toolbox/">Smart mode</a>
is enabled, click in the lower half of the region.
</p>
<p>
<h2>Select a Region From the Region List</h2>
<p>
Click the name of the region in the
- <a href="/ardours-interface/the-editor/the-editor_s-lists/region-list/">Region List</a>.
+ <a href="/ardours-interface/editor-lists/region-list/">Region List</a>.
Note that this will do nothing for whole-file regions, since they do not exist
anywhere in a playlist or track.
</p>
</p>
<p>
You may want to review your understanding of
- <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">the edit point/range</a> and
+ <a href="/ardours-interface/the-edit-point-control/">the edit point/range</a> and
<a href="/editing-and-arranging/which-regions-are-affected/">which regions will be affected by region operations</a>.
</p>
<dl class="wide-table">
<kbd class="mouse">Left</kbd>-drag the edge of the region.
</p>
<p>
- Trimming will obey <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">Snap settings</a>.
+ Trimming will obey <a href="/ardours-interface/the-grid-controls/">Snap settings</a>.
</p>
<h2>Click Trimming With the Mouse</h2>
<h2>Keyboard Shortcuts for Trimming</h2>
<p>
There are several commands for region trimming. Some use the
- <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">edit point</a> to determine where
+ <a href="/ardours-interface/the-edit-point-control/">edit point</a> to determine where
to trim to. Some are not bound to any keys by default (but could be via the
Keybindings Editor).
</p>
If <kbd class="menu">Snap To Grid</kbd> is enabled, then regions can
only move so that they align with locations determined by the current
snap settings (beats, or seconds, or other region boundaries, etc).
- See <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">Snap To the Grid</a>
+ See <a href="/ardours-interface/the-grid-controls/">Snap To the Grid</a>
for details.
</p>
<p>
Aligning regions (sometimes called "spotting") means moving one or more
regions based on a defined location, which in Ardour is always the
- <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">edit point</a>. An
+ <a href="/ardours-interface/the-edit-point-control/">edit point</a>. An
alignment operation moves the region(s) so that some part of the region
is positioned at the edit point. Available alignment commands include:
</p>
<h2>Inserting Patch Changes</h2>
<p>
Ensure that the
- <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">edit point</a> is
+ <a href="/ardours-interface/the-edit-point-control/">edit point</a> is
located where you want the patch change to be (within an existing
MIDI region). Context click, and from the MIDI region's context menu,
select <kbd class="menu">MIDI > Insert Patch Change</kbd>. A
<p>
As well as exporting an audio file, create a file (in CUE or TOC format
respectively) containg CD track information, as defined in the
-<a href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/">Ranges & Marks List</a>.
+<a href="/ardours-interface/editor-lists/ranges-and-marks-list/">Ranges & Marks List</a>.
<h4>Tag with session's metadata</h4>
<p>
<strong>Click audio file:</strong> sets a user defined sound to be
played when Ardour's metronome is enabled in the
- <a href="/ardours-interface/transport-bar-and-times/the-transport-bar/">
+ <a href="/ardours-interface/the-transport-bar/">
Transport Bar</a>
</p>
</li>
<p>
This tab contains settings that relate to the behavior of the
- <a href="/ardours-interface/transport-bar-and-times/the-transport-bar/">Transport Bar</a>
+ <a href="/ardours-interface/the-transport-bar/">Transport Bar</a>
and <a href="/synchronization/">Synchronization</a>.
</p>
<p>
<strong>Ignore snap using:</strong> This mouse and keyboard combination
temporarily changes the
- <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">snap mode</a> to
+ <a href="/ardours-interface/the-grid-controls/">snap mode</a> to
<strong>No Grid</strong>.
</p>
</li>
--- /dev/null
+---
+layout: default
+title: Generic Midi Surface Control
+---
+
+<p>
+ Generic Midi allows synthesizers and other devices communicate with
+ Ardour. MIDI devices can send commands relating to playback (such as
+ play or stop), performance (such as volume, play, stop, and almost any
+ other function (such as Edit, or Undo).
+</p>
+<p>
+ Many MIDI control surfaces use predefined MIDI protocols such as the
+ "Mackie Control Protocol". In such cases it is best to use Ardour's
+ implementation of that protocol as it is likely more feature complete.
+</p>
+
+{% children %}
---
layout: default
-title: MIDI Binding Maps
----
+title: Generic MIDI Binding Maps
+---
<p>
- Ardour 2.X supported
- <a href="/using-control-surfaces/midi-learn/"><dfn>MIDI learning</dfn></a>
+ Ardour 2.X supported
+ <a href="/using-control-surfaces/generic-midi/midi-learn/"><dfn>MIDI learning</dfn></a>
for more or less any control. This was a nice feature that quite a few other
DAWs are providing by now, but it didn't allow Ardour to work "out of the
box" with sensible defaults for existing commercial MIDI
controllers. In Ardour 3 and later versions, we have augmented the
- MIDI learn feature with the ability to load a <dfn>MIDI binding map</dfn>
+ MIDI learn feature with the ability to load a <dfn>MIDI binding map</dfn>
for a given controller, which can set up an arbitrary number of physical
- controls with anything inside Ardour that can be controlled.
+ controls with anything inside Ardour that can be controlled.
</p>
<p>
Currently (August 2016), we have presets for the following devices/modes:
At this time, new binding maps need to be created with a text editor.
<p>
MIDI binding maps are accessible by double-clicking <kbd class="menu">Edit
- > Preferences > Control Surfaces > Generic MIDI</kbd>. Ardour will
+ > Preferences > Control Surfaces > Generic MIDI</kbd>. Ardour will
retain your selection after you choose one.
</p>
<h2>Creating new MIDI maps</h2>
<h3>The Basic Concept</h3>
<p>
- Since the beginning of time (well, sometime early in the 2.X series),
- Ardour has had the concept of identifying each track and bus with a
- <dfn>remote control ID</dfn>. This ID uniquely identifies a track or bus
- so that when messages arrive from elsewhere via MIDI or OSC , we can determine
- which track or bus they are intended to control. Ardour has a
+ Since the beginning of time (well, sometime early in the 2.X series),
+ Ardour has had the concept of identifying each track and bus with a
+ <dfn>remote control ID</dfn>. This ID uniquely identifies a track or bus
+ so that when messages arrive from elsewhere via MIDI or OSC , we can determine
+ which track or bus they are intended to control. See
<a
- href="/working-with-tracks/controlling-track-ordering/track-ordering-and-remote-control-ids/">number
- of ways of assigning remote control IDs</a>, but they don't really matter
- very much when creating MIDI binding maps, so we won't discuss that here.
- You just need to know that there is a "first track" and its remote control
+ href="/working-with-tracks/controlling-track-ordering/track-ordering-and-remote-control-ids/">
+ remote control IDs</a> for more information.
+ You just need to know that there is a "first track" and its remote control
ID is 1, and so on.
</p>
<h3>Getting Started</h3>
<p>
- MIDI bindings are stored in files with the suffix ".map" attached to their
+ MIDI bindings are stored in files with the suffix ".map" attached to their
name. The minimal content looks like this:
</p>
<pre>
So, to start, create a file with that as the initial contents.
</p>
<p>
- On OS X, Ardour loads midi maps from its binary-bundle folder in
- <code>Ardour-<version>/midi_maps/</code> and checks
- various other locations as well (defined by the ARDOUR_MIDIMAPS_PATH
- environment variable). On GNU/Linux the easiest is to save the file to
+ On OS X, Ardour loads midi maps from its binary-bundle folder in
+ <code>Ardour-<version>/midi_maps/</code> and checks
+ various other locations as well (defined by the ARDOUR_MIDIMAPS_PATH
+ environment variable). On GNU/Linux the easiest is to save the file to
<code>~/.config/ardour3/midi_maps/</code>.
</p>
<h3>Finding out what your MIDI control surface sends</h3>
<p>
- This is the most complex part of the job, but its still not very hard.
- You need to connect the control surface to an application that will show
- you the information that the device sends each time you modify a knob,
- slider, button etc. There are a variety of such applications (notably
- <code>gmidimon</code> and <code>kmidimon</code>, but you can actually use
- Ardour for this if you want. Start Ardour in a terminal window, connect
- MIDI ports up, and in the Preferences window, enable "Trace Input" on the
- relevant MIDI port. A full trace of the MIDI data received will show up in
- the terminal window. (Note: in Ardour3, you get a dedicated, custom dialog
+ This is the most complex part of the job, but its still not very hard.
+ You need to connect the control surface to an application that will show
+ you the information that the device sends each time you modify a knob,
+ slider, button etc. There are a variety of such applications (notably
+ <code>gmidimon</code> and <code>kmidimon</code>, but you can actually use
+ Ardour for this if you want. Start Ardour in a terminal window, connect
+ MIDI ports up, and in the Preferences window, enable "Trace Input" on the
+ relevant MIDI port. A full trace of the MIDI data received will show up in
+ the terminal window. (Note: in Ardour3, you get a dedicated, custom dialog
for this kind of tracing.)
</p>
<h3>Types of Bindings</h3>
<p>
- There are two basic kinds of bindings you can make between a MIDI message
- and something inside Ardour. The first is a binding to a specific parameter
- of a track or bus. The second is a binding to a function that will change
+ There are two basic kinds of bindings you can make between a MIDI message
+ and something inside Ardour. The first is a binding to a specific parameter
+ of a track or bus. The second is a binding to a function that will change
Ardour's state in some way.
</p>
<h4>Binding to Track/Bus controls</h4>
<h4>Message specifications</h4>
<p>
You can create a binding for either 3 types of channel messages, or for a
- system exclusive ("sysex") message. A channel message specification looks
+ system exclusive ("sysex") message. A channel message specification looks
like this:
</p>
<code>
<Binding channel="1" ctl="13" ....
</code>
<p>
- This defines a binding for a MIDI Continuous Controller message involving
- controller 13, arriving on channel 1. There are 16 MIDI channels, numbered
- 1 to 16. Where the example above says <code>ctl</code>, you can alternatively
- use <code>note</code> (to create binding for a Note On message) or
+ This defines a binding for a MIDI Continuous Controller message involving
+ controller 13, arriving on channel 1. There are 16 MIDI channels, numbered
+ 1 to 16. Where the example above says <code>ctl</code>, you can alternatively
+ use <code>note</code> (to create binding for a Note On message) or
<code>pgm</code> (to create a binding for a Program Change message).
</p>
<p>
offsets rather than values. These accept Continuous Controller messages
but treat them as offsets. These are good for banked controls as they are
always at the right spot to start adjusting. (
- <a href="/using-control-surfaces/midi-binding-maps/working-with-encoders/">
+ <a href="/using-control-surfaces/generic-midi/working-with-encoders/">
Learn more about working with encoders
</a>)
</p>
<Binding sysex="f0 7f 0 6 7 f7" ....
</code>
<p>
- The string after the <code>sysex=</code> part is the sequence of MIDI bytes,
+ The string after the <code>sysex=</code> part is the sequence of MIDI bytes,
as hexadecimal values, that make up the sysex message.
</p>
<p>
<Binding msg="80 60 40" ....
</code>
<p>
- The string after the <code>msg=</code> part is the sequence of MIDI bytes, as
- hexadecimal values, that make up the message you want to bind. Using this is
- slightly less efficient than the other variants shown above, but is useful for
+ The string after the <code>msg=</code> part is the sequence of MIDI bytes, as
+ hexadecimal values, that make up the message you want to bind. Using this is
+ slightly less efficient than the other variants shown above, but is useful for
some oddly designed control devices.
</p>
<h4>Control address</h4>
<p>
- A <dfn>control address</dfn> defines what the binding will actually control.
+ A <dfn>control address</dfn> defines what the binding will actually control.
There are quite a few different things that can be specified here:
</p>
<dl class="wide-table">
</dt>
<dd>identifies a track or bus by its remote control ID within the current bank (see below for more on banks)
</dd>
+<dt>S, followed by a number
+</dt>
+<dd>identifies a selected track in order they have been selected, S1 should be the same track as the Editor Mixer
+</dd>
<dt>one or more words
</dt>
<dd>identifies a track or bus by its name
</dd>
</dl>
<p>
- For send/insert/plugin controls, the address consists of a track/bus
- address (as just described) followed by a number identifying the plugin/send
- (starting from 1). For plugin parameters, there is an additional third
+ For send/insert/plugin controls, the address consists of a track/bus
+ address (as just described) followed by a number identifying the plugin/send
+ (starting from 1). For plugin parameters, there is an additional third
component: a number identifying the plugin parameter number (starting from
1).
</p>
<p>
- One additional feature: for solo and mute bindings, you can also add
- <code>momentary="yes"</code> after the control address. This is useful
- primarily for NoteOn bindings — when Ardour gets the NoteOn it
- will solo or mute the targetted track or bus, but then when a NoteOff
+ One additional feature: for solo and mute bindings, you can also add
+ <code>momentary="yes"</code> after the control address. This is useful
+ primarily for NoteOn bindings — when Ardour gets the NoteOn it
+ will solo or mute the targetted track or bus, but then when a NoteOff
arrives, it will un-solo or un-mute it.
</p>
<h4>Bindings to Ardour "functions"</h4>
<p>
- Rather than binding to a specific track/bus control, it may be useful to
- have a MIDI controller able to alter some part of Ardour's state. A
+ Rather than binding to a specific track/bus control, it may be useful to
+ have a MIDI controller able to alter some part of Ardour's state. A
binding definition that does this looks like this:
</p>
<code>
<Binding channel="1" note="13" function="transport-roll"/>
</code>
<p>
- In this case, a NoteOn message for note number 13 (on channel 1) will
+ In this case, a NoteOn message for note number 13 (on channel 1) will
start the transport rolling. The following function names are available:
</p>
<dl class="narrower-table">
<h4>Binding to Ardour "actions"</h4>
<p>
You can also bind a sysex or arbitrary message to any of the items
- that occur in Ardour's main menu (and its submenus). The best place
- to look for the (long) list of how to address each item is in your
- keybindings file, which will contain lines that look like this:
-</p>
-<code>
-(gtk_accel_path "<Actions>/Editor/temporal-zoom-in" "equal")
-</code>
+ that occur in Ardour's main menu (and its submenus). The <a
+ href="/appendix/menu-actions-list/">
+ list of actions</a> shows all available values of <em>action-name</em>.
<p>
- To create a binding between an arbitrary MIDI message (we'll use a
- note-off on channel 1 of MIDI note 60 (hex) with release velocity
+ To create a binding between an arbitrary MIDI message (we'll use a
+ note-off on channel 1 of MIDI note 60 (hex) with release velocity
40 (hex)), the binding file would contain:
</p>
<code>
<Binding msg="80 60 40" action="Editor/temporal-zoom-in"/>
</code>
<p>
- The general rule, when taken an item from the keybindings file and
- using it in a MIDI binding is to simply strip the
- <code><Action></code> prefix of the second field in the
+ The general rule, when taken an item from the keybindings file and
+ using it in a MIDI binding is to simply strip the
+ <code><Action></code> prefix of the second field in the
keybinding definition.
</p>
<h3>Banks and Banking</h3>
<p>
- Because many modern control surfaces offer per-track/bus controls
- for far fewer tracks & busses than many users want to control,
- Ardour offers the relatively common place concept of <dfn>banks</dfn>. Banks
- allow you to control any number of tracks and/or busses easily,
- regardless of how many faders/knobs etc. your control surface has.<br />
- To use banking, the control addresses must be specified using the
- <dfn>bank relative</dfn> format mentioned above ("B1" to identify
- the first track of a bank of tracks, rather than "1" to identify
+ Because many modern control surfaces offer per-track/bus controls
+ for far fewer tracks & busses than many users want to control,
+ Ardour offers the relatively common place concept of <dfn>banks</dfn>. Banks
+ allow you to control any number of tracks and/or busses easily,
+ regardless of how many faders/knobs etc. your control surface has.<br />
+ To use banking, the control addresses must be specified using the
+ <dfn>bank relative</dfn> format mentioned above ("B1" to identify
+ the first track of a bank of tracks, rather than "1" to identify
the first track).
</p>
<p>
- One very important extra piece of information is required to use
- banking: an extra line near the start of the list of bindings
- that specifies how many tracks/busses to use per bank. If the
- device has 8 faders, then 8 would be a sensible value to use for
+ One very important extra piece of information is required to use
+ banking: an extra line near the start of the list of bindings
+ that specifies how many tracks/busses to use per bank. If the
+ device has 8 faders, then 8 would be a sensible value to use for
this. The line looks like this:</p>
<code>
<DeviceInfo bank-size="8"/>
</code>
<p>
In addition, you probably want to ensure that you bind something
- on the control surface to the <code>next-bank</code> and
- <code>prev-bank</code> functions, otherwise you and other users
- will have to use the mouse and the GUI to change banks, which
+ on the control surface to the <code>next-bank</code> and
+ <code>prev-bank</code> functions, otherwise you and other users
+ will have to use the mouse and the GUI to change banks, which
rather defeats the purpose of the bindings.
</p>
+<h3>The Selected Strip</h3>
+<p>
+ Often times one wants to just deal with the strip currently
+ selected by the GUI (or the control surface). In the same way as with
+ banks above the selected strip can be designated with <em>S1</em>.
+</p>
<h2>A Complete (though muddled) Example</h2>
<pre>
<?xml version="1.0" encoding="UTF-8"?>
</ArdourMIDIBindings>
</pre>
<p>
- Please note that channel, controller and note numbers are specified as
- decimal numbers in the ranges 1-16, 0-127 and 0-127 respectively
+ Please note that channel, controller and note numbers are specified as
+ decimal numbers in the ranges 1-16, 0-127 and 0-127 respectively
(the channel range may change at some point).
</p>
-
+
{% children %}
---
layout: default
-title: MIDI Learn
----
+title: Generic MIDI Learn
+---
<h2>Philosophy</h2>
<p>
There are no "best" ways to map an arbitrary MIDI controller for
controlling Ardour. There may be very legitimate reasons for different
-users to prefer quite different mappings.
+users to prefer quite different mappings.
</p>
<p>
On every platform that Ardour runs on, there are excellent
having users rely on them to actually connect Ardour to other MIDI
devices and software. On OS X, we recommend Pete Yandell's MIDI
Patchbay. On Linux, a wide variety of tools are available including
-QJackctl, aconnect, Patchage, and more.
+QJackctl, aconnect, Patchage, and more.
</p>
<h2>Basics</h2>
<ol>
<li>Enable Generic MIDI control: <kbd class="menu">Edit > Preferences
> Control Surfaces > Generic MIDI</kbd></li>
- <li>Connect Ardour's MIDI port named <samp>control</samp> to whatever
+ <li>Connect Ardour's MIDI port named <samp>control</samp> to whatever
hardware or software you want (using a MIDI patchbay app)</li>
- <li><kbd class="mod1 mouse">Middle</kbd>-click on whatever on-screen
+ <li><kbd class="mod1 mouse">Middle</kbd>-click on whatever on-screen
fader, plugin parameter control, button etc. you want to control</li>
<li>A small window appears that says "Operate Controller now"</li>
<li>Move the hardware knob or fader, or press the note/key.</li>
---
layout: default
-title: Working With Encoders in Ardour
-menu_title: Working With Encoders
+title: Generic MIDI and Encoders
---
<p>
--- /dev/null
+---
+title: Clocks
+---
+
+
--- /dev/null
+---
+title: Controls
+---
+
+
+++ /dev/null
----
-title: Generic MIDI
----
-
-
--- /dev/null
+---
+title: Mixer Strips
+---
+
+
---
---
-title: Transport bar and times
-include: _manual/05_ardours-interface/03_transport-bar-and-times.html
+title: Transport Bar
+include: _manual/05_ardours-interface/03_the-transport-bar.html
part: chapter
---
---
-title: The Transport Bar
-include: _manual/05_ardours-interface/03_transport-bar-and-times/01_the-transport-bar.html
+title: Clocks
+include: clocks.html
+part: chapter
+---
+
+---
+title: Transport Clocks
+include: _manual/05_ardours-interface/04_transport-clocks.html
part: subchapter
---
---
-title: Times
-include: _manual/05_ardours-interface/03_transport-bar-and-times/02_times.html
+title: Selection and Punch Clocks
+include: _manual/05_ardours-interface/05_selection-and-punch-clocks.html
part: subchapter
---
---
-title: The Editor
-include: _manual/05_ardours-interface/04_the-editor.html
+title: Status Indicators and Mode Buttons
+include: _manual/05_ardours-interface/06_status-indicators.html
part: chapter
---
---
-title: The Editor - The Toolbar
-include: _manual/05_ardours-interface/04_the-editor/01_the-toolbar.html
+title: Toolbox
+include: _manual/05_ardours-interface/07_the-toolbox.html
part: chapter
---
---
-title: The Toolbox
-include: _manual/05_ardours-interface/04_the-editor/01_the-toolbar/01_the-toolbox.html
-part: subchapter
+title: Controls
+include: controls.html
+part: chapter
---
---
-title: the Zoom Controls
-include: _manual/05_ardours-interface/04_the-editor/01_the-toolbar/02_the-zoom-controls.html
+title: Zoom Controls
+include: _manual/05_ardours-interface/08_the-zoom-controls.html
part: subchapter
---
---
-title: the Grid Controls
-include: _manual/05_ardours-interface/04_the-editor/01_the-toolbar/03_the-grid-controls.html
+title: Grid Controls
+include: _manual/05_ardours-interface/09_the-grid-controls.html
part: subchapter
---
---
-title: the Edit Point Control
-include: _manual/05_ardours-interface/04_the-editor/01_the-toolbar/04_the-edit-point-control.html
+title: Edit Point Control
+include: _manual/05_ardours-interface/10_the-edit-point-control.html
part: subchapter
---
---
-title: The Nudge Controls
-include: _manual/05_ardours-interface/04_the-editor/01_the-toolbar/05_the-nudge-controls.html
+title: Nudge Controls
+include: _manual/05_ardours-interface/11_the-nudge-controls.html
part: subchapter
---
---
-title: The Ruler
-include: _manual/05_ardours-interface/04_the-editor/02_the-ruler.html
-part: subchapter
+title: Ruler
+include: _manual/05_ardours-interface/12_the-ruler.html
+part: chapter
---
---
-title: The Editor - The Editor's Lists
-include: _manual/05_ardours-interface/04_the-editor/03_the-editor_s-lists.html
+title: Summary
+include: _manual/05_ardours-interface/13_the-summary.html
part: chapter
---
---
-title: Region List
-include: _manual/05_ardours-interface/04_the-editor/03_the-editor_s-lists/01_region-list.html
-part: subchapter
+title: Editor Lists
+include: _manual/05_ardours-interface/14_editor-lists.html
+part: chapter
---
---
-title: Tracks and Busses List
-include: _manual/05_ardours-interface/04_the-editor/03_the-editor_s-lists/02_tracks-and-busses-list.html
+title: The Region List
+include: _manual/05_ardours-interface/14_editor-lists/01_region-list.html
part: subchapter
---
---
-title: Snapshot List
-include: _manual/05_ardours-interface/04_the-editor/03_the-editor_s-lists/03_snapshot-list.html
+title: The Tracks and Busses List
+include: _manual/05_ardours-interface/14_editor-lists/02_tracks-and-busses-list.html
part: subchapter
---
---
-title: Track and Bus Group List
-include: _manual/05_ardours-interface/04_the-editor/03_the-editor_s-lists/04_track-and-bus-group-list.html
+title: The Snapshot List
+include: _manual/05_ardours-interface/14_editor-lists/03_snapshot-list.html
part: subchapter
---
---
-title: Ranges and Marks List
-include: _manual/05_ardours-interface/04_the-editor/03_the-editor_s-lists/05_ranges-and-marks-list.html
+title: The Track and Bus Group List
+include: _manual/05_ardours-interface/14_editor-lists/04_track-and-bus-group-list.html
part: subchapter
---
---
-title: The Summary
-include: _manual/05_ardours-interface/04_the-editor/05_the-summary.html
+title: The Ranges and Marks Lists
+include: _manual/05_ardours-interface/14_editor-lists/05_ranges-and-marks-list.html
part: subchapter
---
---
-title: The Mixer
-include: _manual/05_ardours-interface/05_the-mixer.html
+title: Favorite Plugins Window
+include: _manual/05_ardours-interface/15_favorite-plugins-window.html
part: chapter
---
---
-title: The Mixer - Favorite Plugins Window
-include: _manual/05_ardours-interface/05_the-mixer/01_favorite-plugins-window.html
-part: subchapter
+title: Strips list
+include: _manual/05_ardours-interface/16_the-strips-list.html
+part: chapter
---
---
-title: The Mixer - The Strips list
-include: _manual/05_ardours-interface/05_the-mixer/02_the-strips-list.html
-part: subchapter
+title: Groups list
+include: _manual/05_ardours-interface/17_the-groups-list.html
+part: chapter
---
---
-title: The Mixer - The Groups list
-include: _manual/05_ardours-interface/05_the-mixer/03_the-groups-list.html
-part: subchapter
+title: Mixer Strips
+include: mixer-strips.html
+part: chapter
---
---
-title: The Mixer - Audio/MIDI Mixer Strips
-include: _manual/05_ardours-interface/05_the-mixer/04_audio-midi-mixer-strips.html
+title: Audio/MIDI Mixer Strips
+include: _manual/05_ardours-interface/18_audio-midi-mixer-strips.html
part: subchapter
---
---
-title: The Mixer - Audio/MIDI Busses Mixer Strips
-include: _manual/05_ardours-interface/05_the-mixer/05_busses-mixer-strips.html
+title: Audio/MIDI Busses Mixer Strips
+include: _manual/05_ardours-interface/19_busses-mixer-strips.html
part: subchapter
---
---
-title: The Mixer - Control Masters Mixer Strips
-include: _manual/05_ardours-interface/05_the-mixer/06_control-masters.html
+title: Control Masters Mixer Strips
+include: _manual/05_ardours-interface/20_control-masters.html
part: subchapter
---
---
-title: The Mixer - The Master Bus Strip
-include: _manual/05_ardours-interface/05_the-mixer/07_the-master-bus-strip.html
+title: Master Bus Strip
+include: _manual/05_ardours-interface/21_the-master-bus-strip.html
part: subchapter
---
---
-title: The Mixer - Monitoring
-include: _manual/05_ardours-interface/05_the-mixer/08_monitoring.html
-part: subchapter
+title: Monitor Section
+include: _manual/05_ardours-interface/22_the-monitor-section.html
+part: chapter
---
part: chapter
---
+---
+title: Editing Clocks
+include: _manual/02_introducing-ardour/03_basic-gui-operations/08_editing-clocks.html
+part: subchapter
+---
+
---
title: Which Regions Are Affected?
menu_title: Affected Regions
---
title: Generic MIDI
-include: generic-midi.html
+include: _manual/23_using-control-surfaces/03_generic-midi.html
part: chapter
---
---
-title: MIDI Binding Maps
-include: _manual/23_using-control-surfaces/03_midi-binding-maps.html
+title: Generic MIDI Binding Maps
+include: _manual/23_using-control-surfaces/03_generic-midi/01_midi-binding-maps.html
exclude: yes
part: subchapter
---
---
-title: MIDI Learn
-include: _manual/23_using-control-surfaces/04_midi-learn.html
+title: Generic MIDI Learn
+include: _manual/23_using-control-surfaces/03_generic-midi/02_midi-learn.html
exclude: yes
part: subchapter
---
---
-title: Working With Encoders in Ardour
+title: Generic MIDI and Encoders
menu_title: Working With Encoders
-include: _manual/23_using-control-surfaces/03_midi-binding-maps/01_working-with-encoders.html
+include: _manual/23_using-control-surfaces/03_generic-midi/03_working-with-encoders.html
exclude: yes
part: subchapter
---
---
title: Using the Presonus Faderport
menu_title: Presonus Faderport
-include: _manual/23_using-control-surfaces/05_Presonus_FaderPort.html
+include: _manual/23_using-control-surfaces/04_Presonus_FaderPort.html
exclude: yes
part: chapter
---
---
title: Using the Ableton Push 2
menu_title: Ableton Push 2
-include: _manual/23_using-control-surfaces/06_Ableton_Push2.html
+include: _manual/23_using-control-surfaces/05_Ableton_Push2.html
exclude: yes
part: chapter
---
projects / ardour-manual-diverged / commitdiff
