+++ /dev/null
----
-layout: default
-title: Key Bindings
----
-
-<p>
- Almost every available function in Ardour can be executed via a
- <dfn>key binding</dfn> or <dfn><abbr title="Open Sound
- Control">OSC</abbr></dfn> command. There are many more functions
- available than there are keys on even the largest current computer
- keyboards, so only a subset of them are bound to keys by default.
-</p>
-<h2>Key bindings for menu items</h2>
-<p>
- Existing key bindings in menus are listed on the right side of the
- menu items.
-</p>
-<p>
- To create a custom key binding for a menu item quickly, navigate to
- the relevant (sub-) menu, hover over the item with the mouse and press
- the desired combination of modifiers and key.
-</p>
-<p class="warning">
- Ardour will silently re-assign the binding if you use a key
- combination that is already in use, possibly removing a standard
- keyboard shortcut without warning you. That might lead to confusion
- when you ask other users for help, and they explain something in terms
- of a standard key binding, which will then have a completely
- different effect on your system.
-</p>
-<h2>Key binding editor</h2>
-<p>
- For a complete overview of all existing keyboard bindings, go to
- <kbd class="menu">Window > Key Bindings</kbd>. This widget will let
- you view and edit even those functions that are not available in the menu,
- and even remove key bindings altogether.
-</p>
\ No newline at end of file
---
layout: default
-title: Undo/Redo for Editing
----
+title: Undo/Redo for Editing
+---
<p>
While editing, it happens that you apply an unintended change, or make
a choice one that you later decide was wrong. All changes to the
- arrangement of session components (regions, control points) along the
- timeline can be <dfn>undone</dfn> (and <dfn>redone</dfn> if necessary).
+ arrangement of session components (regions, control points) along the
+ timeline can be <dfn>undone</dfn> (and <dfn>redone</dfn> if necessary).
</p>
<p>
The default keybindings are <kbd class="mod1">Z</kbd> for Undo and
</p>
<p>
The maximum number of changes that can be undone can be configured under
- <kbd class="menu">Edit > Preferences > Misc > Undo</kbd>.
+ <kbd class="menu">Edit > Preferences > Misc > Undo</kbd>.
The maximum number of changes stored in the history file is a separate
parameter, and can also be set in the same place.
</p>
command that affects the display of the editor window. Its shortcut is
<kbd class="mod3">Z</kbd>.
There is also an undo for selection. See
- <a href="/ardours-interface/basic-gui-operations/selection-techniques/">Selection Techniques</a> for more information.
-</p>
+ <a href="/introducing-ardour/basic-gui-operations/selection-techniques/">Selection Techniques</a> for more information.
+</p>
---
layout: default
title: Mouse
----
-
+---
+
<p>
- Ardour is designed to work best with a <dfn>three button mouse</dfn>
+ Ardour is designed to work best with a <dfn>three button mouse</dfn>
equipped with a <dfn>scroll wheel</dfn>.
</p>
<p>
find that a good quality mouse (especially one with a weighted,
latchable scroll wheel) will make your use of Ardour vastly more
efficient. They are cheap, and time is not.
-</p>
+</p>
<p>
- For more detailed instructions, see
- <a href="/ardours-interface/basic-gui-operations/using-the-mouse/">Using the mouse</a>.
+ For more detailed instructions, see
+ <a href="/introducing-ardour/basic-gui-operations/using-the-mouse//">Using the mouse</a>.
</p>
---
layout: default
title: Starting Ardour
----
-
+---
+
<p>
There are several ways of <dfn>starting Ardour</dfn>, which may vary
depending on which platform you are using it.
</p>
<ul>
- <li>double-click the Ardour icon in your platform's file manager (e.g.
+ <li>double-click the Ardour icon in your platform's file manager (e.g.
Nautilus on Linux, Finder on OS X)</li>
<li>double click on an Ardour session file in your platform's file manager</li>
- <li>on Linux, you can also start Ardour <a
- href="/ardours-interface/starting-ardour/starting-ardour-from-the-command-line/">on
- the command line</a></li>
+ <li>on Linux, you can also start Ardour on the command line (see below)</li>
</ul>
<p>
- When Ardour is run for the very first time, a special dialog is displayed
+ When Ardour is run for the very first time, a special dialog is displayed
that will ask you several questions about your setup. You will not be asked
these questions again, but you can always modify your choices via the
<kbd class="menu">Edit > Preferences</kbd> dialog.
program, like <a href="https://qjackctl.sourceforge.io/">QjackCtl</a> or <a href="http://kxstudio.linuxaudio.org/Applications:Cadence">Cadence</a>.
</p>
<p>
- If you open Ardour without specifying an existing session it will display
+ If you open Ardour without specifying an existing session it will display
the <kbd class="menu">Session > New...</kbd> dialog and the <kbd class="menu">Audio/MIDI Setup</kbd> dialog.
- See <a href="/working-with-sessions/new-session-dialog/">New/Open Session Dialog</a> for a description of those dialogs.
+ See <a href="/working-with-sessions/new-session-dialog/">New/Open Session Dialog</a> for a description of those dialogs.
</p>
-
+
<h2>Starting Ardour From the Command Line (Linux)</h2>
<p>
To start Ardour with a new, named session:
</p>
<kbd class="cmd lin">Ardour5 -N <em>/path/to/session</em></kbd>
-
-
<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, and when stopped, goes back to the orginial location</a></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 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">To Next Region Sync</dt><dd>Moves the currently selected to the next region sync point (by default : beginning or end of the region)</dd>
<dt class="sub1">To Previous Region Sync</dt><dd>Same, to the left</dd>
<dt>Markers</dt><dd></dd>
- <dt class="sub1">Add Mark from Playhead</dt><dd>Creates a Marker at he position of the playhead</dd>
+ <dt class="sub1">Add Mark from Playhead</dt><dd>Creates a Marker at the position of the playhead</dd>
<dt class="sub1">Remove Mark at Playhead</dt><dd>Removes any marker at the position of the playhead</dd>
<dt class="sub1">Toggle Mark at Playhead</dt><dd>Combine the 2 previous : if a marker exists, deletes it, otherwise create it</dd>
<dt>Scripted Actions</dt><dd></dd>
<dt class="sub1">[] Script Manager</dt><dd>Shows the <a href="/lua-scripting/">Script manager</a>, allowing to use and manage the Lua scripts in the session</dd>
- <dt class="sub1">Unset #<em>n</em></dt><dd>Desactivate the <em>n</em>th script</dd>
+ <dt class="sub1">Unset #<em>n</em></dt><dd>Deactivate the <em>n</em>th script</dd>
<dt>Preferences</dt><dd>Displays the <a href="/preferences-and-session-properties/preferences-dialog/">Preferences</a> panels, allowing to change Ardour's behaviour</dd>
</dl>
<li><dfn>Audition</dfn>: Blinks when using the import dialog to audition material.</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="/introducing-ardour/meters/">Metering in Ardour</a></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 %}
-
-<img src="/images/a3_new_main_clocks.png" alt="An image of the transport clocks in Ardour 3" />
+<img src="/images/new_main_clocks.png" alt="An image of the transport clocks in Ardour" />
began the drag on.
</p>
-
-
-
-
-
<li><dfn>Mouse</dfn></li>
- <li><dfn>Edit Point</dfn> as set in the <a href="/editing-and-arranging/edit-point/">Edit point</a> control.</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>
</ul>
selected tracks. If no track is selected, all the tracks will be shrunk or
expanded each time the button is pushed.
-
-
-
<p>
Dragging and dropping tracks inside the Strips List allows to reorganise the tracks in the session,
- both in the Mixer and the Editor.
+ both in the Mixer and the Editor. Clicking a track scrolls the Mixer to show this track.
</p>
<p>
--- /dev/null
+---
+title: Audio/MIDI Mixer Strips
+---
+
+<img class="right" src="/images/mixer-1-strip-numbered.png" alt="A mixer strip">
+
+<p>
+ A <dfn>mixer strip</dfn> in Ardour is a vertical view of the track, from a mixing point of view.
+ This view is convenient to deal with I/O, effects, panning/muting, gain, etc... It has a general
+ "top to bottom" flow.
+</p>
+<p>
+ The mixer strips breaks down into :
+</p>
+<ol>
+ <li>Header</li>
+ <li>Track name</li>
+ <li>Input(s)</li>
+ <li>Polarity <em>only for audio tracks</em></li>
+ <li>Processor box</li>
+ <li>Panner</li>
+ <li>Recording options</li>
+ <li>Mute/Solo</li>
+ <li>Gain & Meter</li>
+ <li>Control master</li>
+ <li>Fader automation/mix group/metering point</li>
+ <li>Output(s)</li>
+ <li>Comments</li>
+</ol>
+
+
+<h2>Headers</h2>
+
+<p>
+ At the top of the window, is the <a href="/working-with-tracks/track-and-bus-groups/">group tabs</a> (here, <em>recm...</em>).
+ This allows to group tracks together for common controls.
+</p>
+<p>
+ Bellow are 3 buttons :
+</p>
+<ul>
+ <li>
+ The double arrow button allows to shrink/expand the width of the strip. <kbd
+ class="mod1"></kbd><kbd class="mod3"></kbd><kbd class="mouse">Click</kbd> the button will shrink/expand all
+ the tracks at once
+ </li>
+ <li>
+ The color bar shows the color of the track in the editor
+ </li>
+ <li>
+ The <kbd class="menu">X</kbd> button toggles the visibility of the track OFF. To turn it back ON,
+ one can either go to the <a href="/ardours-interface/the-editor/the-editor_s-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>.
+ </li>
+</ul>
+<p>
+ <kbd class="mouse">Right</kbd> clicking on the color bar will bring up a context menu, which is exactly the same as clicking on the Track name button.
+</p>
+
+<h2>Track Name</h2>
+
+<p>
+ Clicking the Track name button will bring up a menu :
+</p>
+<dl>
+ <dt>Color...</dt><dd>Changes the strip/track color</dd>
+ <dt>Comments...</dt><dd>Shows an editor to put comments about the track, see bellow the Comments button</dd>
+ <dt>Inputs...</dt><dd>Shows the Routing grid for the inputs of the track</dd>
+ <dt>Outputs...</dt><dd>Shows the Routing grid for the outputs of the track</dd>
+ <dt>Save As Template...</dt><dd>Allows to save the track without its media content (I/O, effects,...) for later reuse</dd>
+ <dt>Rename...</dt><dd>Changes the name of the track (effective both in the Mixer and the Editor)</dd>
+ <dt><kbd class="option"></kbd>Active</dt><dd>Select the active status of the track. An inactive track won't output any sound</dd>
+ <dt><kbd class="option"></kbd>Strict I/O</dt><dd>While in <a href="/signal-routing/signal-flow/">Strict I/O</a> mode, a track <em>always</em> has as many output as it has inputs, regardless of the effects. When disabled, a stereo effect put on a mono track will result in a stereo output for the strip.</dd>
+ <dt>Pin Connections...</dt><dd>Shows the <kbd class="menu">Pin Configuration</kbd> window, that shows (and allows to modify) all the signal flows inside the track</dd>
+ <dt>Adjust Latency...</dt><dd>Shows the <kbd class="menu">Track Latency</kbd> dialog, that allows fine-tune the latency to the track, in samples, msec or period</dd>
+ <dt><kbd class="option"></kbd>Protect Against Denormals</dt><dd>Uses a trick to get rid of <em>denormals</em>, which are very small numbers the CPU can have a hard time dealing with. To be used if the CPU consumption for plugins is noticeably higher than expected</dd>
+ <dt>Duplicate...</dt><dd>Copies the track to a new one, optionnaly with its playlist</dd>
+ <dt>Remove</dt><dd>Deletes the track and its playlist</dd>
+</dl>
+
+<h2>Inputs</h2>
+
+<p>
+ The dropdown button shows the current input port(s), i.e. what's plugged to the "in" of the track.
+ By default, each audio track is connected to the system inputs, ready for recording,
+ as shown by the number(s).
+ Clicking the dropdown Inputs button will allow to change the inputs, through a menu:
+</p>
+<dl>
+ <dt>Disconnect</dt><dd>Disconnects everything, i.e. the track has no input</dd>
+ <dt>In <em>n</em></dt><dd>Those are the system inputs, e.g. to record from the soundcard. A mono track will have <em>In 1</em> and <em>In 2</em> separated, while a stereo track can have <em>In 1+2</em></dd>
+ <dt><em>Track n output</em></dt><dd>All the outputs of compatible tracks, e.g., a mono track can only receive a mono signal, a MIDI track can only receive MIDI signal, ...</dd>
+ <dt>Add Audio Port</dt><dd>Adds an audio input to the track, i.e. a mono audio track becomes a stero one</dd>
+ <dt>Add MIDI Port</dt><dd>Adds a MIDI input to the track. Adding it to an audio track makes it a mixed Audio/MIDI track. This can be usefull e.g. to feed some plugins with a MIDI signal to control the audio, like a vocoder</dd>
+ <dt>Routing Grid</dt><dd>Shows the <a href="/signal-routing/Patchbay/"><kbd class="menu">Routing Grid</kbd> window</a>, which allows for more complex input configuration</dd>
+</dl>
+<p>
+ The <kbd class="menu">Routing Grid</kbd> can also be shown by right clicking the dropdown Inputs button.
+ It allows to make the connections through a matrix, and connect things that are not listed in the menu above,
+ or connect to multiple sources at once, reduce the number of inputs, etc...
+</p>
+<p>
+ On audio tracks, is a Trim knob, as on traditional consoles.
+ It set the base input level for the track, avoiding any clipping. Notice that it
+ trims both any input, but (when playing back), also the level of the playlist as
+ displayed in the Editor. It makes sense as while playing, the input of the track is
+ the playlist, on which the mixer strip acts.
+</p>
+<p>
+ On midi tracks, it is replaced by a MIDI Input button, that allows/disallows
+ MIDI input on the track.
+</p>
+
+
+<h2>Polarity</h2>
+
+<p>
+ On audio tracks only, the Polarity button(s), 1 per input, allow to reverse
+ the signal, i.e. a negative value will be positive and vice-versa. This can
+ help deal with phasing issues.
+</p>
+
+<h2>Processor box</h2>
+
+<p>
+ The processor box is where the effects are added. By default, one effect is always
+ present : the Fader (see bellow). The effects can be added <em>pre</em>-fader and appear in brown,
+ or <em>post</em>-fader, where they will appear in dark green. The signal flow is represented by lines,
+ red for the MIDI and green for the audio.
+</p>
+<p>
+ It is also where the <a href="/signal-routing/aux-sends/">Sends</a> come from, wether external or auxiliary.
+</p>
+<p>
+ To learn more about the processor box, see <a href="/working-with-plugins/processor-box/">The Processor Box</a>.
+</p>
+
+<h2>Panner</h2>
+
+<p>
+ The <dfn>Panner</dfn> visually displays how the sound will be distributed between the different outputs.
+ They'll look and behave differently if the track is mono, stereo, or has multiple channels.
+</p>
+<p>
+ Right clicking the Panner will show a menu:
+</p>
+<dl>
+ <dt><kbd class="option"></kbd>Bypass</dt><dd>When checked, the panner is grayed, and the signal is not affected by it</dd>
+ <dt>Reset</dt><dd>Resets the panner to its default settings, e.g. for a mono signal, it is centered</dd>
+ <dt>Edit...</dt><dd>Shows a <kbd class="menu">Panner</kbd> dialog, which allows for fine tuning of the panner</dd>
+</dl>
+<p>
+ See <a href="/mixing/panning/">Panning</a> to learn more about how to control the panner,
+ and what kind of panners are available inside Ardour.
+</p>
+
+<h2>Recording options</h2>
+
+<p>
+ The most noticeable button here is the Record Enable one, with a red circle. When
+ enabled, next time the Global record will be armed and playback started, everything that
+ comes from the input of the track will be recorded. Right clicking a disabled record
+ button allows to enable <kbd class="menu">Rec-Safe</kbd>, thus protecting the track
+ against accidental recording.
+</p>
+<p>
+ The buttons on the right, <kbd class="menu">In</kbd> and <kbd class="menu">Disk</kbd>,
+ show what the user is listening to by lighting up, between the <em>In</em>put and the
+ actual content of the playlist on <em>Disk</em>.
+</p>
+<p>
+ They also allow to override the automatic switching by pressing them to lock one
+ source or the other to be what the user is hearing.
+</p>
+
+<h2>Mute/Solo</h2>
+
+<p>
+ These buttons allow to Mute (or silence) the track, or Solo them, shutting down the
+ gain of the other tracks (totally by default, can be set to partially in the options).
+ See <a href="/mixing/muting-and-soloing/">Muting and Soloing</a>
+ for more information.
+</p>
+<p>
+ Notice that by default, Solo overrides Mute, i.e. if a track is both Soloed and Muted, it will
+ play. That can be changed in the preferences.
+</p>
+<p>
+ The two led button above are related to solo :
+</p>
+<ul>
+ <li>Solo Isolate, as the name suggests, isolates tracks or busses from the solo system. When tracks or busses are soloed the isolated ones will not mute.</li>
+ <li>Solo Lock locks the solo into its current state (ie solo on or solo off). It will not allow the solo state to be changed until the lock is released.</li>
+</ul>
+
+<h2>Gain & Meter</h2>
+
+<p>
+ On the right of this part is a <a href="/meters/">Meter</a>, displaying the level of the track's
+ output after the fader. In can be set to display the signal at any point, see below <em>Metering Point</em>.
+ Right clicking this meter shows a menu allowing to switch the meter type.
+</p>
+<p>
+ The big Gain slider on the left allows to change the gain of the track. Its default O dB
+ value is reminded with a white horizontal line, and its precise value is shown
+ in a text field above it, that doubles as a way to type in a numeric value.
+</p>
+<p>
+ The text field above the meter shows the "Peak", i.e. the mawimum value that has been
+ reached during playback. To avoid distortion, the value should stay bellow O dB, and
+ if it goes above this value, the text field will turn red. Clicking on this field
+ will reset the Peak value (for a new measurement or a new part of the track).
+</p>
+
+<p class="note">
+ Notice that if any gain automation has been set and the automation state is set on "Play"
+ (see below), then the Gain fader is driven by the automation, and not by the user. The Gain fader will
+ turn grey to show it's inactive.
+</p>
+
+<h2>Control master</h2>
+
+<p>
+ If at least one control master exists, this button will show up, allowing the user
+ to link this track to any control master.
+</p>
+<p>
+ Clicking the button lists all the available control masters, and a menu option to
+ <kbd class="menu">Unassign all</kbd>. Notice that a track can have be a slave to as many
+ control masters as they are in the session, hence multiplying the number of C.M. buttons.
+ The displayed number is the number of the Control Master, not the count of C.M. linked
+ to the track. A track with no control master assigned will show a unique button with a
+ "<kbd class="menu">-vca-</kbd>" label instead of this number.
+</p>
+
+<h2>Fader automation/mix group/metering point</h2>
+
+<h3>Fader automation mode</h3>
+<p>
+ This button allows to choose the mode used regarding automation:
+</p>
+<dl>
+ <dt>Manual</dt><dd><em>(default)</em> The playback won't use the fader automation data</dd>
+ <dt>Play</dt><dd>Enables playback/use of fader automation data</dd>
+ <dt>Write</dt><dd>While the transport is rolling, all fader changes will be recorded to the fader automation lane</dd>
+ <dt>Touch</dt><dd>While the transport is rolling, touching the fader will initiate recording all fader changes until the fader is released. When the fader is not being touched, existing automation data will be played/used to control the gain level.</dd>
+</dl>
+
+<h3>Mix group</h3>
+<p>
+ This button displays the mix group information as does the tab in the header (see above).
+ It is convenient though, as it allows to quickly switch the track from one
+ group to another with a drop down menu, also allowing to affect the track to
+ a non-adjascent group (which the tab won't easily allow).
+</p>
+
+<h3>Metering Point</h3>
+<p>
+ The metering displayed in the meter is by default is 'Post', i.e. Post fader.
+ It can be changed with this button to Any point of the signal flow :
+</p>
+<dl>
+ <dt>In</dt><dd>The input of the track</dd>
+ <dt>Pre</dt><dd>Pre-fader</dd>
+ <dt>Post</dt><dd>Post-fader</dd>
+ <dt>Out</dt><dd>The output of the track</dd>
+ <dt>Custom</dt><dd>A <em>Meter</em> processor is added to the processor box an can be set anywhere (by dragging and dropping) to probe the signal flow at that pointat the point</dd>
+</dl>
+
+<h2>Output(s)</h2>
+
+<p>
+ This button is exactly the same as the <em>Input</em> button, but applies to the <em>output</em>
+ of the track.
+</p>
+
+
+<h2>Comments</h2>
+
+<p>
+ This buttons open up a little text editor, that can be used to add some written notes to the track,
+ as e.g. a particular setting. The button's caption is replaced by the beginning of the text, so
+ it can be used as a "sub"name for the track.
+</p>
+++ /dev/null
----
-title: The Master Strip
----
-
-
-
-<p class="fixme">add content</p>
-
-
-
-
-
--- /dev/null
+---
+title: Audio/MIDI Busses Mixer Strips
+---
+
+<img class="right" src="/images/bus-mixer-strip.png" alt="A bus mixer strip">
+
+<p>
+ An Ardour bus can be considered a virtual track, as in a track that doesn't have a playlist (so, no regions).
+ Its use is to "group" some audio signals to be treated the same way. One simple use case is to group all the audio tracks containing the different drums of a drumkit. Routing all the drums tracks outputs to a bus allows, once the different levels amongst the drums have been set, to adjust the global level of the drumkit in the mix.
+</p>
+<p>
+ Bus usage goes way beyond this simple example though : busses, as tracks, can receive plugins for common audio treatment, and be routed themselves as needed. This makes for a very useful tool that is very commonly used both for musical purposes and computing ones : instead of using e.g. 10 discrete delay plugins on 10 different tracks, busses are often used as receivers of <a href="/signal-routing/aux-sends/">sends</a>, and only 1 delay plugin is used on this bus, reducing the processing power needed.
+</p>
+
+<h2>Audio Busses vs MIDI Busses</h3>
+
+<p>
+ Ardour supports 2 types of busses : Audio and MIDI. A MIDI bus differs from an audio bus just by:
+<p>
+<ul>
+ <li>its input (which is midi, as shown by the red signal lines in the processor box) instead of <em>n</em> audio</li>
+ <li>the fact that you can put an instrument on it at creation time, whereas you can't easily add an instrument to an audio bus</li>
+ <li>as for tracks, the MIDI bus doesn't have a trim knob or invert phase button(s).</li>
+</ul>
+<p>
+ MIDI busses provide a particularly efficient workflow for virtual drumkits where the arrangement uses different MIDI tracks.
+ Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins,
+ where a MIDI signal controls an audio one.
+</p>
+<p class="note">
+ Adding any audio input to a MIDI bus transforms it into an audio bus.
+</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>.
+ The differences are :
+</p>
+<ul>
+ <li>as the busses dont have a playlist (and cannot host any media), they can't be recorded on. The recording controls are not present</li>
+ <li>an <kbd class="menu">Aux</kbd> button replaces these controls.</li>
+</ul>
+<p>
+ Clicking the <kbd class="menu">Aux</kbd> button makes every track that sends a signal to this bus through <a href="/signal-routing/aux-sends/">Aux sends</a> blink in turquoise.
+ Right clicking this button brings up a menu:
+</p>
+<dl>
+ <dt>Assign all tracks (prefader)</dt><dd>Creates an Aux Send in every track, to this bus. The send is placed just before the fader</dd>
+ <dt>Assign all tracks and busses (prefader)</dt><dd>Creates an Aux Send in every track and every bus, to this bus. The send is placed just before the fader</dd>
+ <dt>Assign all tracks (postfader)</dt><dd>Same as above, but the send is placed just after the fader</dd>
+ <dt>Assign all tracks and busses (postfader)</dt><dd>Same as above, with tracks and busses</dd>
+ <dt>Assign selected tracks (prefader)</dt><dd>Same as for all tracks, but only applies to the selected tracks</dd>
+ <dt>Assign selected tracks and busses (prefader)</dt><dd>Same as for all tracks and busses, but only applies to the selected tracks and busses</dd>
+ <dt>Assign selected tracks (postfader)</dt><dd>Same as above, but the send is placed just after the fader</dd>
+ <dt>Assign selected tracks and busses (postfader)</dt><dd>Same as above, with tracks and busses</dd>
+ <dt>Set sends gain to -inf</dt><dd>For all the sends to this bus, put the send fader to −∞ so no signal is sent</dd>
+ <dt>Set sends gain to 0dB</dt><dd>For all the sends to this bus, put the send fader at the default position, 0dB (100% of th signal is sent)</dd>
+</dl>
+
+<h2>Connecting a track to a bus</h2>
+<p>
+ Depending on the user's workflow and the way busses are used, 2 possibilities exists :
+</p>
+
+<h3>Connecting a track to a bus via its outputs</h3>
+
+<img class="left" src="/images/connecting_bus_output.png" alt="Connecting a bus through a track's outputs">
+<p>
+ Connecting the output(s) of a track to the input(s) of the bus sends <em>all</em> the audio/MIDI to the bus. In the mixer strip, select (at the bottom) the OUTPUT button (often, by default, "Master"), and in the list, choose the input of a bus. Note that only the bus able to receive this output will show up, e.g. a mono bus wont be able to be connected to the output of a stereo track).
+</p>
+<p>
+ Obviously, doing so will (by default) disconnect the output from the Master's input, which means all the audio/MIDI will be routed to the bus. For more complex routing, the OUTPUT button allows to show the <kbd class="menu">Routing Grid</kbd> that allows to plug the output of the track to multiple outputs at once, be it busses, tracks, Master... The button will then reflect these multiple connections by showing a <em>*number*</em>, number being the number of connections made in the routing grid.
+</p>
+
+<h3>Connecting a track to a bus via Sends</h3>
+
+<img class="left" src="/images/connecting_bus_send.png" alt="Connecting a bus through a send">
+<p>
+ This allows not to interrupt the natural flow of the signal, i.e. the track will still output to what its connected to (e.g. Master). The signal is "tapped" at the point of insertion of the send, to be sent to the bus. Right click where in the signal flow you want the send to happen, and select <kdb class="menu">New Aux Send... > name_of_the_bus</kbd>.
+</p>
+<p>
+ By <kbd class="mouse">left-clicking</kbd> the send meter, it is possible to adjust the amount of signal sent to the bus. This is often the way tracks are connected to an effect bus, like a Delay bus.
+</p>
+
+<p class="note">
+ Busses can be plugged to other busses, through outputs or sends. Both example workflows discussed previously, i.e. busses for grouping tracks and busses for effects, can both coexist, as e.g. a "grouping" drum bus can have a send to a reverb bus, and be connected to a compressor bus.
+</p>
--- /dev/null
+---
+title: Control Masters Mixer Strips
+---
+
+<img class="right" src="/images/vca-numbered.png" alt="A Control Master mixer strip">
+
+<p>
+ Although track/bus <a href="/working-with-tracks/track-and-bus-groups/">groups</a> offer a certain
+ kind of grouped-control over gain, solo, mute and more, traditional mixing consoles have long had
+ group master channels ("<abbr title="Voltage-Controlled Amplifier">VCA</abbr>s") which allows to combine
+ both a single fader to control the group level while also allowing you to easily adjust the relative
+ levels inside the group. For large projects, this can make mixing much easier to control.
+</p>
+<p>
+ Ardour implements those VCAs as <dfn>Control Masters</dfn>, in a way that allows to use either or both
+ of the conventions used on different traditionnal consoles for combining multiple masters:
+</p>
+<ul>
+ <li>Nest VCAs (VCA 2 controls VCA 1 etc.)</li>
+ <li>Chain VCAs (VCA 1 and VCA 2 both control track or bus <em>N</em>)</li>
+</ul>
+
+<h2>Description of the Control Masters</h2>
+
+<p>
+A Control Master strip is made of (from top to bottom in the screenshot) :
+</p>
+
+<ol>
+ <li>Number of the Control Master</li>
+ <li><kbd class="menu">X</kbd> button: Allows to hide the VCA strip. Left clicking this button toggles the exclusive visibility of the tracks connected to this VCA</li>
+ <li>Name button</li>
+ <li><kbd class="menu">M</kbd>: mutes the VCA, <kbd class="menu">S</kbd>: solos the VCA</li>
+ <li>Level meter: allows to adjust the level of the VCA</li>
+ <li><kbd class="menu">~vca~</kbd>: a VCA button to optionally connect to another VCA</li>
+</ol>
+
+<p>Right-clicking the name button shows a context menus comprised of :</p>
+<dl>
+ <dt>Rename</dt><dd>Renames the VCA</dd>
+ <dt>Color...</dt><dd>Changes the color of the VCA button in the tracks connected to this one</dd>
+ <dt>Drop All Slaves</dt><dd>Deletes all connections to this VCA, i.e. no tracks are controlled by this VCA anymore</dd>
+ <dt>Remove</dt><dd>Deletes this VCA</dd>
+</dl>
+
+<h2>Connecting to a VCA strip</h2>
+
+<img class="left" src="/images/connecting_to_vca.png" alt="Connecting to VCA">
+
+<p>
+ Connecting a track/bus/VCA to a VCA is as simple as clicking the VCA button that appears on any mixer strip
+ under the main fader and choosing the VCA to connect to.
+</p>
+
+<p class="note">The VCA button only shows up in mixer strips when at least one Control Master exists, i.e., a
+ Control Master must be created <em>before</em> connecting tracks to it.</p>
+
+<p>
+ Clicking the VCA button shows all the Control Masters in the session, and any or all of this vca can be checked
+ to link them to the track, making this track controlled by multiple Control Masters. The track will then show
+ multiple VCA buttons. Disconnecting a Control MAste from a track is done by unchecking this Control Master in
+ the list that pops up, or clicking <kbd class="menu">Unassign All</kbd> to disconnect from all Control Masters at once.
+</p>
--- /dev/null
+---
+title: The Master Bus Strip
+---
+
+<img class="right" src="/images/master-strip.png" alt="The Master strip in the mixer">
+
+<p>
+ The <dfn>Master strip</dfn> in Ardour is very similar to the other busses mixer strips.
+ The list of differences is (from top to bottom):
+</p>
+
+<ul>
+ <li>There is no color affected to the master strip</li>
+ <li>The master strip cannot be hidden, so there is not <kbd class="menu">X</kbd> in the top right</li>
+ <li>It is by definition always solo, so no <kbd class="menu">Solo</kbd>, <kbd class="menu">Iso</kbd> or <kbd class="menu">Lock</kbd> buttons. It is replaced by a button to show the Monitoring section if <a href="/preferences-and-session-properties/session-properties-dialog/monitoring/">the session has one</a></li>
+ <li>It cannot belong to a mix group, so the button is removed.</li>
+</ul>
+
+<p class="note">
+ The Master bus strip is <em>allways</em> fixed, at the right end of the mixer, regardless of the scrolling position.
+</p>
---
layout: default
title: Controlling Playback
----
+---
<h2>Positioning the Playhead</h2>
-
+
<p>
- The <dfn>playhead</dfn> is a vertical line with two arrows at each end
+ The <dfn>playhead</dfn> is a vertical line with two arrows at each end
that indicates the current position of playback.
</p>
<h3>Positioning the playhead at the current pointer position</h3>
<p>
- Pressing <kbd>P</kbd> will set the playhead to the current position of
+ Pressing <kbd>P</kbd> will set the playhead to the current position of
the pointer, if it is within the editor track area.
</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/using-ardour-clock-displays/">edit their value</a>
+ Click on either the primary or secondary transport clock and
+ <a href="/ardours-interface/transport-bar-and-times/times/">edit their value</a>
to move the playhead to a specific position.
</p>
<h3>Positioning the playhead at a marker</h3>
<p>
- Click <kbd class="mouse">Right</kbd> on the marker and select either
+ Click <kbd class="mouse">Right</kbd> on the marker and select either
<kbd class="menu">Locate to here</kbd> or <kbd class="menu">Play from
- here</kbd>.
+ here</kbd>.
</p>
<p>
- Alternatively, place the pointer on the marker and press
+ Alternatively, place the pointer on the marker and press
<kbd>P</kbd> to set the playhead.
</p>
-
+
<h2>Looping the Transport</h2>
-
+
<p>
- When the <dfn>loop transport</dfn> button is pressed, the playhead will
- jump the start of the loop range, and continue to the end of that range
+ When the <dfn>loop transport</dfn> button is pressed, the playhead will
+ jump the start of the loop range, and continue to the end of that range
before returning to the start and repeating.
- While looping, a light green area is displayed in the time ruler over
+ While looping, a light green area is displayed in the time ruler over
the tracks to show the loop range.
</p>
<p>
By default, looping is bound to the <kbd>l</kbd> key.
</p>
<p>
- For more information on defining and altering the loop range see
+ For more information on defining and altering the loop range see
<a href="/working-with-markers/loop-range/">Loop Range Markers</a>.
</p>
---
layout: default
title: Creating Location Markers
----
+---
<p>
<dfn>Location Markers</dfn> appear in the <dfn>Locations ruler</dfn> at the top
- of the timeline. The <dfn>begin</dfn> and <dfn>end</dfn> markers appear
- automatically, but you can create custom markers at any position in a
+ of the timeline. The <dfn>begin</dfn> and <dfn>end</dfn> markers appear
+ automatically, but you can create custom markers at any position in a
session.
</p>
<p>
To add a marker at the <strong>current playhead position</strong>, press
<kbd>Num-↵</kbd> (the Enter key on the numeric keypad).
- Alternatively, use <kbd class="menu">Transport > Markers > Add
+ Alternatively, use <kbd class="menu">Transport > Markers > Add
Mark from Playhead</kbd>.
</p>
<p>
Marker</kbd> and use the clock widget to set its position.
</p>
<p>
- For details see
- <a href="/working-with-markers/rangesmarks-list/">Ranges & Marks
+ 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/using-ardour-clock-displays/"> Using
+ and <a href="/ardours-interface/transport-bar-and-times/times/"> Using
Ardour Clock Displays</a>.
</p>
---
layout: default
title: The Loop Range
----
-
+---
+
<p>
The <dfn>loop range</dfn> is a special range that defines the start and end points
for loop play, which can be enabled in the transport bar.
</p>
<p>
It can be defined via the timeline or the <a
- href="/working-with-markers/rangesmarks-list/">Ranges & Marks
+ href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/">Ranges & Marks
list</a>.
</p>
-
-
---
layout: default
title: Marker Context Menu
----
+---
<p>
- <kbd class="mouse">Right</kbd>-clicking a marker in the timeline opens the
+ <kbd class="mouse">Right</kbd>-clicking a marker in the timeline opens the
marker context menu. From this menu, you can:
</p>
<dl>
<dt>Move Mark to Playhead</dt>
<dd>Move this marker to the current playhead position.</dd>
<dt>Create Range to Next Marker</dt>
- <dd>Create a range marker between this location and the next one along on
+ <dd>Create a range marker between this location and the next one along on
the timeline.</dd>
<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="/working-with-markers/rangesmarks-list/">Ranges & Marks
+ href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/">Ranges & Marks
list</a>.</dd>
<dt>Rename</dt>
<dd>Change the name of the marker.</dd>
<dt>Lock</dt>
- <dd>If this is ticked, it will be impossible to drag the marker's
+ <dd>If this is ticked, it will be impossible to drag the marker's
position; useful if you want to prevent accidental movements.</dd>
<dt>Glue to Bars and Beats</dt>
- <dd>If this is ticked, the marker will maintain its position in bars and
+ <dd>If this is ticked, the marker will maintain its position in bars and
beats even if there are changes in tempo and meter.</dd>
<dt>Remove</dt>
<dd>Removes the marker. </dd>
</dl>
<p>
There are also a few options in <kbd class="menu">Transport > Active
- Mark</kbd>. These options apply to the currently selected location marker,
- and move it to a nearby region boundary, region sync point, or to the
+ Mark</kbd>. These options apply to the currently selected location marker,
+ and move it to a nearby region boundary, region sync point, or to the
playhead or mouse.
</p>
-
---
layout: default
title: Punch Range
----
-
+---
+
<p>
- The <dfn>punch range</dfn> is a special range used to define where
+ The <dfn>punch range</dfn> is a special range used to define where
recording will start and/or stop during a <dfn>punch</dfn>.
</p>
<p>
- It can be defined on the timeline or in the
- <a href="/working-with-markers/rangesmarks-list/">Ranges & Marks</a>
+ 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>
list.
</p>
-
-
---
layout: default
title: Snapshots
----
-
+---
+
<p>
- Sometimes you will want to save a <dfn>snapshot</dfn> of the current state of a session for possible
+ Sometimes you will want to save a <dfn>snapshot</dfn> of the current state of a session for possible
use in the future. For example, you may be about to change the entire
- arrangement of a piece, or drastically alter the signal processing, and
+ arrangement of a piece, or drastically alter the signal processing, and
want a reference to come back to, should that not work out.
</p>
<p>
This is easily accomplished using <kbd class="menu">Session >
- Snapshot</kbd>.
- A small dialog will appear, allowing you to enter a name for the snapshot.
+ Snapshot</kbd>.
+ A small dialog will appear, allowing you to enter a name for the snapshot.
The default name is based on the current date and time.<br />
You can create any number of snapshots.
</p>
<p class="warning">
- Creating a snapshot does <strong>not</strong> modify your session,
- nor does it save your session. Instead, it saves an alternate version
- of the session, within the session folder. The snapshot shares all data
- present in the session.
-</p>
+ Creating a snapshot does <strong>not</strong> modify your session,
+ nor does it save your session. Instead, it saves an alternate version
+ of the session, within the session folder. The snapshot shares all data
+ present in the session.
+</p>
<p>
- After creating a snapshot, you can continue working on the session and
- save it normally using <kbd class="menu">Session > Save</kbd> and any
+ After creating a snapshot, you can continue working on the session and
+ save it normally using <kbd class="menu">Session > Save</kbd> and any
existing snapshots will remain unchanged.
</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 Snapshots tab of the
- <a href="/ardours-interface/introducing-the-editor-window/editor-lists/">Editor List</a>.
- Find the name of the snapshot in the list and click it. Ardour will switch
+ existing snapshot, navigate the <a href="/ardours-interface/the-editor/the-editor_s-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.
</p>
<h2>Starting Ardour With a Snapshot</h2>
<p>
Since a snapshot is just another session file stored within the session
- folder, you can specify that "version" when loading an existing session.
- The browser in the "Open Session" dialog will show an expander arrow for
+ folder, you can specify that "version" when loading an existing session.
+ The browser in the "Open Session" dialog will show an expander arrow for
sessions that have more than 1 session file (i.e. snapshots) present
- — click on it to see the list, and then click on the name of the
+ — click on it to see the list, and then click on the name of the
snapshot you want to load.
</p>
<h2>Saving and Switching to a Snapshot</h2>
<p>
- Sometimes you may want to create a snapshot and then have all future
- edits and modifications saved to that snapshot rather than the main
+ Sometimes you may want to create a snapshot and then have all future
+ edits and modifications saved to that snapshot rather than the main
session. This is easily done using <kbd class="menu">Session > Save
- As</kbd>. This does not create a new session folder, but saves your
- session as a new snapshot and then switches the "current snapshot"
- to the newly created one. All subsequent saves of the session will
- be stored in this new snapshot, and existing snapshots (and the main
- session) will be left unaffected.
+ As</kbd>. This does not create a new session folder, but saves your
+ session as a new snapshot and then switches the "current snapshot"
+ to the newly created one. All subsequent saves of the session will
+ be stored in this new snapshot, and existing snapshots (and the main
+ session) will be left unaffected.
</p>
-
+++ /dev/null
----
-layout: default
-title: Busses and VCAs
----
-
-<p>
- In order to ease the process of mixing, Ardour offers two tools traditionally found on hardware mixing consoles : <dfn>Busses</dfn> and <dfn><abbr title="Voltage-Controlled Amplifier">VCA</abbr></dfn>s.
-</p>
-
-<h2>Busses</h2>
-
-<p>
- An Ardour bus can be considered a virtual track, as in a track that doesn't have a playlist (so, no regions).
-</p>
-
-<p>
- Its use is to "group" some audio signals to be treated the same way. One simple use case is to group all the audio tracks containing the different drums of a drumkit. Routing all the drums tracks outputs to a bus allows, once the different levels amongst the drums have been set, to adjust the global level of the drumkit in the mix.
-</p>
-
-<p>
- Bus usage goes way beyond this simple example though : busses, as tracks, can receive plugins for common audio treatment, and be routed themselves as needed. This makes for a very useful tool that is very commonly used both for musical purposes and computing ones : instead of using e.g. 10 discrete delay plugins on 10 different tracks, busses are often used as receivers of <a href="/signal-routing/aux-sends/">sends</a>, and only 1 delay plugin is used on this bus, reducing the processing power needed.
-</p>
-
-<p class="note">Note that the Master strip, which by default receives the output from all tracks, <em>is</em> a bus itself.</p>
-
-<h3>Audio Busses vs MIDI Busses</h3>
-
-<p>
- Ardour supports 2 types of busses : Audio and MIDI. A MIDI bus differs from an audio bus just by its input (which is 1 midi input instead of <em>n</em> audio), the fact that you can put an instrument on it at creation time, whereas you can't easily add an instrument to an audio bus.
-</p>
-
-<p>
- MIDI busses provide a particularly efficient workflow for virtual drumkits where the arrangement uses different MIDI tracks. Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins.
-</p>
-
-<p>
- Depending on the user's workflow and the way busses are used, 2 possibilities exists :
-</p>
-
-<h3>Connecting a track to a bus via outputs</h3>
-
-<img class="right" src="/images/connecting_bus_output.png" alt="Connecting a bus through a track's outputs">
-
-<p>
- Connecting the output(s) of a track to the input(s) of the bus sends <em>all</em> the audio/MIDI to the bus. In the mixer strip, select (at the bottom) the OUTPUT button (often, by default, "Master"), and in the list, choose the input of a bus. Note that only the bus able to receive this output will show up, e.g. a mono bus wont be able to be connected to the output of a stereo track).
-</p>
-
-<p>
- Obviously, doing so will (by default) disconnect the output from the Master's input, which means all the audio/MIDI will be routed to the bus. For more complex routing, the OUTPUT button allows to show the <kbd class="menu">Routing Grid</kbd> that allows to plug the output of the track to multiple outputs at once, be it busses, tracks, Master... The button will then reflect these multiple connections by showing a <em>*number*</em>, number being the number of connections made in the routing grid.
-</p>
-
-<h3>Connecting a track to a bus via Sends</h3>
-
-<img class="left" src="/images/connecting_bus_send.png" alt="Connecting a bus through a send">
-
-<p>
- This allows not to interrupt the natural flow of the signal, i.e. the track will still output to what its connected to (e.g. Master). The signal is "tapped" at the point of insertion of the send, to be sent to the bus. Right click where in the signal flow you want the send to happen, and select <kdb class="menu">New Aux Send... > name_of_the_bus</kbd>.
-</p>
-
-<p>By <kbd class="mouse">left-clicking</kbd> the send meter, it is possible to adjust the amount of signal sent to the bus. This is often the way tracks are connected to an effect bus, like a Delay bus.
-</p>
-
-<p class="note">Busses can be plugged to other busses, through outputs or sends. Both example workflows discussed previously, i.e. busses for grouping tracks and busses for effects, can both coexist, as e.g. a "grouping" drum bus can have a send to a reverb bus, and be connected to a compressor bus.
-</p>
-
-
-<h2>VCAs</h2>
-
-<p class="fixme">
- Reword this section to Control MAster, separate from Busses, Detail the fact a track can have multiple VCA attached
-</p>
-
-<img class="left" src="/images/vcas.png" alt="VCAs strips">
-
-<p>
- Although track/bus <a href="/working-with-tracks/track-and-bus-groups/">groups</a> offer a certain kind of grouped-control over gain, solo, mute and more, traditional mixing consoles have long had group master channels ("VCAs") which allows to combine both a single fader to control the group level while also allowing you to easily adjust the relative levels inside the group. For large projects, this can make mixing much easier to control.
-</p>
-
-<p>
- It allows to use either or both of the conventions for combining multiple masters:
-</p>
-
-<ul>
- <li>Nest VCAs (VCA 2 controls VCA 1 etc.)</li>
- <li>Chain VCAs (VCA 1 and VCA2 both control track or bus N)</li>
-</ul>
-
-<h3>Using a VCA strip</h3>
-
-<p>
-A VCA strip is made of (from top to bottom in the screenshot) :
-</p>
-
-<ul>
- <li><dfn>1</dfn>: number of the VCA</li>
- <li><dfn>X</dfn>: allows to hide the VCA strip. Left clicking this button toggles the exclusive visibility of the tracks connected to this VCA</li>
- <li><dfn>M</dfn>: mutes the VCA</li>
- <li><dfn>S</dfn>: solos the VCA</li>
- <li><dfn>A level meter</dfn>: allows to adjust the level of the VCA</li>
- <li><dfn>~vca~</dfn>: a VCA button to optionally connect to another VCA</li>
-</ul>
-
-<p>Right-clicking the name button shows a context menus comprised of :</p>
-
-<ul>
- <li><kbd class="menu">Rename</kbd>: Renames the VCA</li>
- <li><kbd class="menu">Color...</kbd>: Changes the color of the VCA button in the tracks connected to this one</li>
- <li><kbd class="menu">Drop All Slaves</kbd>: Deletes all connections to this VCA, i.e. no tracks are controlled by this VCA anymore</li>
- <li><kbd class="menu">Remove</kbd>: Deletes this VCA</li>
-</ul>
-
-<h3>Connecting to a VCA strip</h3>
-
-<img class="left" src="/images/connecting_to_vca.png" alt="Connecting to VCA">
-
-<p>
- Connecting a track/bus/VCA to a VCA is as simple as clicking the VCA button on any mixer strip and choosing the VCA to connect to.
-</p>
-
-<p class="note">The VCA button only shows up in mixer strips when at least 1 VCA exists, i.e., you have to first create a VCA before connecting it.
-</p>
---
layout: default
title: Reordering Tracks
----
+---
<p>
- The <dfn>track ordering</dfn> of the Editor and Mixer is <dfn>synchronized</dfn>: if you
+ The <dfn>track ordering</dfn> of the Editor and Mixer is <dfn>synchronized</dfn>: if you
reorder in one window, the ordering in the other window will follow.
</p>
(shortcut: <kbd class="mod1">↓</kbd>).
</p>
<p>
- Alternatively, you can use the <kbd class="menu">Tracks & Busses</kbd>
- panel of the
- <a href="/ardours-interface/introducing-the-editor-window/editor-lists/">Editor
- Lists</a>, if visible.
+ 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>
+ panel of the Editor Lists</a>, if visible.
Here, you can freely drag-and-drop tracks and busses into any order you prefer.
</p>
<h2>"Collecting" Group Members</h2>
<p>
- Tracks and Busses that are members of a group can be reordered so that they
- display contiguously within the Editor and Mixer windows. Context-click on
+ Tracks and Busses that are members of a group can be reordered so that they
+ display contiguously within the Editor and Mixer windows. Context-click on
the group tab and choose <kbd class="menu">Collect</kbd>.
</p>
<h2>Ordering of New Tracks</h2>
<p>
- When <dfn>adding new tracks</dfn>, the current selection determines their
- placement. New tracks will be placed after the rightmost (in the mixer) or
- bottom-most (in the editor) selected track. If no tracks are selected, new
+ When <dfn>adding new tracks</dfn>, the current selection determines their
+ placement. New tracks will be placed after the rightmost (in the mixer) or
+ bottom-most (in the editor) selected track. If no tracks are selected, new
tracks will be added at the end.
</p>
<p class="note">
- Because new tracks are automatically selected, you can quickly reorder them
+ Because new tracks are automatically selected, you can quickly reorder them
in the editor window via the keyboard shortcuts after adding them (see above).
</p>
-
---
layout: default
title: Track and Bus Groups
----
+---
<p>
- Tracks and busses can be put into <dfn>groups</dfn>. Members of a group
- can share various settings — useful for managing tracks that are closely
- related to each other. Examples might include tracks that contain
- multiple-microphone recordings of a single source (an acoustic guitar,
+ Tracks and busses can be put into <dfn>groups</dfn>. Members of a group
+ can share various settings — useful for managing tracks that are closely
+ related to each other. Examples might include tracks that contain
+ multiple-microphone recordings of a single source (an acoustic guitar,
perhaps, or a drum-kit).
</p>
<p>
- You can group tracks and busses in various ways. In the editor window,
+ You can group tracks and busses in various ways. In the editor window,
a track's controls might look like these:
</p>
<img class="left" src="/images/track-in-group.png" alt="track headers for a group" />
-<p>
- The green tab to the left of the track header indicates that this track
- is in a group called <samp>Fred</samp>. You can drag these tabs to add
+<p>
+ The green tab to the left of the track header indicates that this track
+ is in a group called <samp>Fred</samp>. You can drag these tabs to add
adjacent tracks to a group.
</p>
</p>
<ul>
<li>Context-click on the group tab and use one of the <kbd
- class="menu">Create...</kbd> options there. You can create a group with
- no members, or one that starts with the currently selected tracks, or
+ class="menu">Create...</kbd> options there. You can create a group with
+ no members, or one that starts with the currently selected tracks, or
record-enabled tracks, or soloed tracks.</li>
- <li>Alternatively, click the ‘g’ button on a track header to open the
- Group menu. The menu lists the available groups. Selecting one of these
- groups will add the track or bus to that group. The menu also lets you
+ <li>Alternatively, click the ‘g’ button on a track header to open the
+ Group menu. The menu lists the available groups. Selecting one of these
+ groups will add the track or bus to that group. The menu also lets you
create a new group.</li>
- <li>Finally, the Groups tab of the
- <a href="/ardours-interface/introducing-the-editor-window/editor-lists/">Editor Lists</a>
- or the Mixer Window has a <kbd class="menu">plus (+)</kbd> button at the
+ <li>Finally, the <a href="/ardours-interface/the-mixer/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>
<h2>Remove Groups</h2>
<p>
Context-click on a <dfn>group tab</dfn> and select <kbd class="menu">Remove
- Group</kbd> from the menu. Removing a group does <em>not</em> remove
+ Group</kbd> from the menu. Removing a group does <em>not</em> remove
the members of a group.
</p>
<p>
- You can also remove groups by selecting them in the Groups tab of the
- <a href="/ardours-interface/introducing-the-editor-window/editor-lists/">Editor Lists</a>
- or Mixer Window and then pressing the <kbd class="menu">minus (-)</kbd>
- button at the bottom of the list.
+ You can also remove groups by selecting them in the <a href="/ardours-interface/the-mixer/the-groups-list/">Groups list</a>
+ and then pressing the <kbd class="menu">minus (-)</kbd> button at the bottom of the list.
</p>
<h2>Add/Remove Tracks and Busses From a Group</h2>
<p>
- Click the <kbd class="menu">g</kbd> button to display a menu with a list
- of the available groups. Select one of these groups to add the track or bus
+ Click the <kbd class="menu">g</kbd> button to display a menu with a list
+ of the available groups. Select one of these groups to add the track or bus
to that group. Select <kbd class="menu">No Group</kbd> to remove it.
</p>
<p>
- Alternatively, you can also drag a group tab to add or remove tracks from
+ Alternatively, you can also drag a group tab to add or remove tracks from
the group.
</p>
<h2>Activate/Deactivate Groups via the Group Tab</h2>
<p>
- Clicking on a group tab toggles the group between being active and inactive.
- An inactive group has no effect when editing its members. An active group
- will share its configured properties across its members. Tabs for disabled
+ Clicking on a group tab toggles the group between being active and inactive.
+ An inactive group has no effect when editing its members. An active group
+ will share its configured properties across its members. Tabs for disabled
groups are coloured grey.</p>
<h2>Modify Group Properties</h2>
<p>
- To edit the properties of a group, context-click on its tab and choose
- <kbd class="menu">Edit Group…</kbd>. This opens the track/bus group dialog,
+ To edit the properties of a group, context-click on its tab and choose
+ <kbd class="menu">Edit Group…</kbd>. This opens the track/bus group dialog,
which is also used when creating new groups:
</p>
<h3>Group Color</h3>
<p>
- Click on the color selector button to change a group's colour. This affects
- the colour of the group's tab in the editor and mixer windows. The color does
- <em>not</em> affect the color of the group members unless you also enable the
- shared <kbd class="menu">Color</kbd> property.
+ Click on the color selector button to change a group's colour. This affects
+ the colour of the group's tab in the editor and mixer windows. The color does
+ <em>not</em> affect the color of the group members unless you also enable the
+ shared <kbd class="menu">Color</kbd> property.
</p>
<h3>Shared Properties</h3>
<p>
- <kbd class="option">Gain</kbd> means that the track faders will be synced to
- always have the same value; <kbd class="option">Relative</kbd> means that the
- gain changes are applied relative to each member's current value. If, for
- example, there are two tracks in a group with relative gain sharing, and their
- faders are set to -3 dB and -1 dB, a change of the first track to a
+ <kbd class="option">Gain</kbd> means that the track faders will be synced to
+ always have the same value; <kbd class="option">Relative</kbd> means that the
+ gain changes are applied relative to each member's current value. If, for
+ example, there are two tracks in a group with relative gain sharing, and their
+ faders are set to -3 dB and -1 dB, a change of the first track to a
gain of -6 dB will result in the second track having a gain of
-4 dB (the <em>difference</em> of the gains remains the same).
</p>
<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/introducing-the-editor-window/editor-lists/tracks--busses-list/#active"><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
+ <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="/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
share the same settings in these respects.
</p>
<p>
- <kbd class="option">Selection</kbd> means that if a region is selected or
+ <kbd class="option">Selection</kbd> means that if a region is selected or
deselected on one member track, <a
href="/working-with-regions/corresponding-regions-selection/">corresponding
- regions</a> on other member tracks
- will be similarly selected. Since region editing operations are applied to all
- currently selected regions, this is the way to make edits apply across all tracks
+ regions</a> on other member tracks
+ will be similarly selected. Since region editing operations are applied to all
+ currently selected regions, this is the way to make edits apply across all tracks
in the group.
</p>
<dt>Remove Group</dt>
<dd>removes the group (and only the group, not its members).</dd>
<dt>Add New Subgroup Bus</dt>
-<dd> creates a bus (giving it the name of the group) and connects the output of each member to the new bus.
+<dd> creates a bus (giving it the name of the group) and connects the output of each member to the new bus.
</dd>
<dt>Add New Aux Bus</dt>
<dd>adds a bus and gives each member a send to that bus. There are two options for this, specifying whether the sends should be placed pre- or post-fader.</dd>
---
layout: default
title: Track Context Menu
----
-
+---
+
<p>
- Within the editor window, context-click (right-click) on either a region
- or empty space within a track to display the <dfn>track context menu</dfn>.
+ Within the editor window, context-click (right-click) on either a region
+ or empty space within a track to display the <dfn>track context menu</dfn>.
The context menu provides easy access to many track-level operations.
</p>
<p>
- If you click on a <dfn>region</dfn>, the first item in the menu is the name of the
- region. If you click on a
- <a href="/working-with-tracks/controlling-track-appearance/layering-display/">layered region</a>,
- the next item in the menu is <kbd class="menu">Choose Top</kbd>. If selected,
- you will see a dialog that allows you to change the vertical order of layers
+ If you click on a <dfn>region</dfn>, the first item in the menu is the name of the
+ region. If you click on a
+ <a href="/working-with-tracks/controlling-track-appearance/layering-display/">layered region</a>,
+ the next item in the menu is <kbd class="menu">Choose Top</kbd>. If selected,
+ you will see a dialog that allows you to change the vertical order of layers
at that point. See <a href="/working-with-tracks/controlling-track-appearance/layering-display/">Layering Display</a> for more details.
</p>
<p>
<dd>
<dl class="narrower-table">
<dt>Play from Edit Point</dt>
- <dd>Play from the location of the current <a href="/editing-and-arranging/edit-point/">edit point</a>.</dd>
+ <dd>Play from the location of the current <a href="/ardours-interface/the-editor/the-toolbar/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>
---
layout: default
title: Import Dialog
----
+---
<p>
- Many sessions will require the use of <dfn>existing material</dfn>,
- whether it consists of audio and/or MIDI data. Using existing samples,
- loops and riffs from files stored on your system can be the basis for
- a new session, or a way to deepen and improve one that is already
- underway.
+ Many sessions will require the use of <dfn>existing material</dfn>,
+ whether it consists of audio and/or MIDI data. Using existing samples,
+ loops and riffs from files stored on your system can be the basis for
+ a new session, or a way to deepen and improve one that is already
+ underway.
</p>
<p>
- You can import audio and MIDI data into your session with the
+ You can import audio and MIDI data into your session with the
<dfn>Add Existing Media</dfn> dialog.
</p>
<img src="/images/209-ARDOUR_1_2_1.png" />
<h2>Importing options</h2>
<p>
You can import files into new, automatically created tracks, to the region
- list (from where you can manually drag them into a track), or as new
+ list (from where you can manually drag them into a track), or as new
<a href="/working-with-tracks/track-types/">Tape tracks</a> with the
- <kbd class="menu">Add new files as...</kbd> option.
+ <kbd class="menu">Add new files as...</kbd> option.
</p>
<p>
New files will be inserted at either the file timestamp (if available,
- zero by default), at the <a href="/editing-and-arranging/edit-point/">edit point</a>, at the
+ zero by default), at the <a href="/ardours-interface/the-editor/the-toolbar/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>
<p>
The <kbd class="menu">Conversion quality</kbd> drop-down controls the
quality of the resampling process, if the sampling rate of the source file
- differs from the session rate.
+ differs from the session rate.
</p>
<p>
Finally, and most importantly, you can decide whether to <kbd
---
layout: default
title: Select Regions
----
+---
<p>
- Many editing operations in Ardour require you to first <dfn>select one or more
- regions</dfn> that you want to change in some way. You can select a single region,
- or multiple regions, including regions in different tracks. When you select
+ Many editing operations in Ardour require you to first <dfn>select one or more
+ regions</dfn> that you want to change in some way. You can select a single region,
+ or multiple regions, including regions in different tracks. When you select
a region, it will appear in a darker color than unselected regions.
</p>
<p>
Note that if a track is a member of a group that is active and has the
- <kbd class="option">Select</kbd> property enabled, then Ardour will attempt to
- match whatever selections you make in one track across every other track of the
- group. See
+ <kbd class="option">Select</kbd> property enabled, then Ardour will attempt to
+ match whatever selections you make in one track across every other track of the
+ group. See
<a href="/working-with-regions/corresponding-regions-selection/">Corresponding
- Regions Selection</a> for more information on precisely how selections will be
+ Regions Selection</a> for more information on precisely how selections will be
propagated to other tracks.
</p>
<h2>Region Selection and Track Selection</h2>
<p>
- Please read
- <a href="/working-with-tracks/selecting-tracks/">Region & Track Selection</a>
+ Please read
+ <a href="/working-with-tracks/selecting-tracks/">Region & Track Selection</a>
for more information on how selecting regions and selecting tracks interact.
</p>
<h2>Select a Region</h2>
<p>
- Confirm that you are using the
- <a href="/ardours-interface/introducing-the-editor-window/the-editing-toolbar/#object">Object tool</a>,
- then click on a region to select it. If
- <a href="/ardours-interface/introducing-the-editor-window/the-editing-toolbar/#smartmode">smart mode</a>
+ Confirm that you are using the
+ <a href="/ardours-interface/the-editor/the-toolbar/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>
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/introducing-the-editor-window/the-editing-toolbar/#object">Object tool</a>,
- then <kbd class="mouse mod1">Left</kbd>-click the region. If
- <a href="/ardours-interface/introducing-the-editor-window/the-editing-toolbar/#smartmode">smart mode</a>
- is enabled, click in the lower half of the region.
+ Confirm you are using the
+ <a href="/ardours-interface/the-editor/the-toolbar/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>
+ is enabled, click in the lower half of the region.
</p>
<p>
- Note that a <kbd class="mouse mod1">left</kbd> click simply toggles the
+ Note that a <kbd class="mouse mod1">left</kbd> click simply toggles the
selected status of an object, so it can be used to select unselected regions
too.
</p>
<ul>
<li><kbd class="mouse mod1">Left</kbd>-click each region, or</li>
<li>
- drag a rubberband box from an empty point in a track before the first
- region you wish to select to a point within or after the last region
- you wish to select (you can <kbd class="mouse mod1">left</kbd>-drag to do this
+ drag a rubberband box from an empty point in a track before the first
+ region you wish to select to a point within or after the last region
+ you wish to select (you can <kbd class="mouse mod1">left</kbd>-drag to do this
multiple times), or,
</li>
<li>
- if the regions are all adjacent to one another, click the first region
- you wish to select, then <kbd class="mouse mod3">Left</kbd>-click the last
+ if the regions are all adjacent to one another, click the first region
+ you wish to select, then <kbd class="mouse mod3">Left</kbd>-click the last
region you wish to select.
</li>
</ul>
<h2>Select All Regions in a Track</h2>
<p>
- Context-click the track, and in the context menu, navigate to
+ Context-click the track, and in the context menu, navigate to
<kbd class="menu">Select > Select All In Track</menu>.
</p>
<p>
- See the <a href="/working-with-tracks/track-context-menu/">Track Context Menu</a>
+ See the <a href="/working-with-tracks/track-context-menu/">Track Context Menu</a>
for more information on other per-track selection operations that are available.
</p>
<h2>Select a Region From the Region List</h2>
<p>
- Click the name of the region in the
- <a href="/ardours-interface/introducing-the-editor-window/editor-lists/region-list/">Region List</a>.
- Note that this will do nothing for whole-file regions, since they do not exist
+ Click the name of the region in the
+ <a href="/ardours-interface/the-editor/the-editor_s-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>
-
layout: default
title: Common Region Edit Operations
menu_title: Region Editing
----
+---
<p>
This section covers a set of <dfn>region editing operations</dfn>
- that you are likely to use often while working on a session.
- Depending on your work habits (and experience of other
- <abbr title="Digital Audio Workstation">DAW</abbr>s) you will find
- some of these operations critical while others are used only rarely.
+ that you are likely to use often while working on a session.
+ Depending on your work habits (and experience of other
+ <abbr title="Digital Audio Workstation">DAW</abbr>s) you will find
+ some of these operations critical while others are used only rarely.
</p>
<p>
- You can carry out all of these operations from the keyboard (see
- <a href="/default-keyboard-bindings/">Default Keyboard Shortcuts</a>
- for a list). Equivalent operations can be performed with the mouse
- in most cases.
+ You can carry out all of these operations from the keyboard (see
+ <a href="/default-keyboard-bindings/">Default Keyboard Shortcuts</a>
+ for a list). Equivalent operations can be performed with the mouse
+ in most cases.
</p>
<p>
- You may want to review your understanding of
- <a href="/editing-and-arranging/edit-point/">the edit point/range</a> and
+ 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="/editing-and-arranging/which-regions-are-affected/">which regions will be affected by region operations</a>.
</p>
<dl class="wide-table">
---
layout: default
title: Trimming Regions
----
+---
<p>
- Changing the <dfn>length</dfn> of a region is a very common editing
- operation, often known as <dfn>trimming</dfn>. There are several ways
- to accomplish this with Ardour, and some very useful specialized trimming
+ Changing the <dfn>length</dfn> of a region is a very common editing
+ operation, often known as <dfn>trimming</dfn>. There are several ways
+ to accomplish this with Ardour, and some very useful specialized trimming
operations.
</p>
<h2>Drag-Trimming With the Mouse</h2>
<p>
- In object mode, move the pointer near the beginning or end of the region.
- The cursor will change to indicate that trimming is possible, and you then
- <kbd class="mouse">Left</kbd>-drag the edge of the region.
+ In object mode, move the pointer near the beginning or end of the region.
+ The cursor will change to indicate that trimming is possible, and you then
+ <kbd class="mouse">Left</kbd>-drag the edge of the region.
</p>
<p>
- Trimming will obey <a href="/editing-and-arranging/snap-to-the-grid/">Snap settings</a>.
+ Trimming will obey <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">Snap settings</a>.
</p>
<h2>Click Trimming With the Mouse</h2>
<p>
- <kbd class="mouse">Left</kbd>-click in the colored bar at the bottom of a region.
- If you are nearer to the start of a region, this will trim the start time to the
- position of the pointer. If you are nearer to the end of a region, it will trim the
+ <kbd class="mouse">Left</kbd>-click in the colored bar at the bottom of a region.
+ If you are nearer to the start of a region, this will trim the start time to the
+ position of the pointer. If you are nearer to the end of a region, it will trim the
end time.
</p>
<h2>Keyboard Shortcuts for Trimming</h2>
<p>
- There are several commands for region trimming. Some use the
- <a href="/editing-and-arranging/edit-point/">edit point</a> to determine where
- to trim to. Some are not bound to any keys by default (but could be via the
+ 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
+ to trim to. Some are not bound to any keys by default (but could be via the
Keybindings Editor).
</p>
<h2 id="trimtonextprevious">Trim to Next/Previous Region</h2>
<p>
- Sometimes you just want to extend the start or end of region so that it reaches
- the end or start of an adjacent region. There is now an operation accessible
+ Sometimes you just want to extend the start or end of region so that it reaches
+ the end or start of an adjacent region. There is now an operation accessible
from the region context menu, under <kbd class="menu">Edit >Trim > Trim to
- Next</kbd> or <kbd class="menu">Edit > Trim > Trim to Previous</kbd>. This
- will extend the selected regions so they directly adjoin their neighbours, unless
- their source files are not long enough, in which case they will be extended to the
- maximum possible. Trim to Next will extend the end of the selected regions to the
- start of the next region; Trim to Previous will extend the start of the selected
+ Next</kbd> or <kbd class="menu">Edit > Trim > Trim to Previous</kbd>. This
+ will extend the selected regions so they directly adjoin their neighbours, unless
+ their source files are not long enough, in which case they will be extended to the
+ maximum possible. Trim to Next will extend the end of the selected regions to the
+ start of the next region; Trim to Previous will extend the start of the selected
regions to the end of the previous region.
</p>
<dl class="wide-table">
<h2>Other Possible Commands for Trimming</h2>
<p>
- These are not bound to any keys by default, but could be via the Keybindings
+ These are not bound to any keys by default, but could be via the Keybindings
Editor. They can also be sent via OSC or other control protocols.
</p>
<dl class="wide-table">
---
layout: default
title: Move Regions
----
+---
<p>
Ardour has a global <dfn>edit mode</dfn> selector at the left of the
</ul>
</p>
<p class="note">
- 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="/editing-and-arranging/snap-to-the-grid/">Snap To the Grid</a>
+ 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>
for details.
</p>
-
+
{% children %}
---
layout: default
title: Align (Spot) Regions
----
+---
<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="/editing-and-arranging/edit-point/">edit point</a>. An
- alignment operation moves the region(s) so that some part of the region
+ 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
+ alignment operation moves the region(s) so that some part of the region
is positioned at the edit point. Available alignment commands include:
</p>
<dl class="wide-table">
---
layout: default
title: Patch Change
----
+---
<p>
- A <dfn>patch change</dfn> is Ardour's description for a combination
- of MIDI program change and bank select messages, that (typically)
- instruct a synthesizer or sampler to select a different sound to use
- on a particular channel.
+ A <dfn>patch change</dfn> is Ardour's description for a combination
+ of MIDI program change and bank select messages, that (typically)
+ instruct a synthesizer or sampler to select a different sound to use
+ on a particular channel.
</p>
<p>
- Patch changes are shown within MIDI regions as small rectangles or
+ Patch changes are shown within MIDI regions as small rectangles or
<dfn>flags</dfn>, as shown below:
</p>
<h2>Inserting Patch Changes</h2>
<p>
- Ensure that the
- <a href="/editing-and-arranging/edit-point/">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
- dialog will appear allowing you to set the bank and program values.
+ Ensure that the
+ <a href="/ardours-interface/the-editor/the-toolbar/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
+ dialog will appear allowing you to set the bank and program values.
</p>
<h2>Modifying Patch Changes</h2>
<p>
- Context-clicking on a patch change will bring up the same dialog that
- was used to create it, allowing you to modify the program and/or bank
+ Context-clicking on a patch change will bring up the same dialog that
+ was used to create it, allowing you to modify the program and/or bank
numbers.
</p>
<p>
You can also use the mouse wheel: <kbd class="mouse">⇑</kbd>/<kbd
- class="mouse">⇓</kbd> on the patch change will alter the program
- number, <kbd class="mouse mod1">⇑</kbd>/<kbd
+ class="mouse">⇓</kbd> on the patch change will alter the program
+ number, <kbd class="mouse mod1">⇑</kbd>/<kbd
class="mouse mod1">⇓</kbd> will modify the bank number.
</p>
<h2>Moving Patch Changes</h2>
<p>
- Just <kbd class="mouse">Left</kbd>-drag on the patch change to move it
+ Just <kbd class="mouse">Left</kbd>-drag on the patch change to move it
around.
</p>
<h2>Removing Patch Changes</h2>
<p>
- Put the mouse pointer into the rectangular area, and press <kbd>Del</kbd>
- or use the delete mouse button operation. This will remove the patch change
+ Put the mouse pointer into the rectangular area, and press <kbd>Del</kbd>
+ or use the delete mouse button operation. This will remove the patch change
(the operation can be undone).
</p>
---
layout: default
title: Export Format Profiles
----
+---
<h2>Export Format Profiles</h2>
<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="/working-with-markers/rangesmarks-list/">Ranges & Marks List</a>.
+<a href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/">Ranges & Marks List</a>.
<h4>Tag with session's metadata</h4>
<h3>Label</h3>
<p>
The 'Label' field lets you choose the name which will be shown for this format
-in the drop-down list of export formats in the 'File Formats' tab of the
+in the drop-down list of export formats in the 'File Formats' tab of the
<a href="/exporting/export-dialog/">Export dialog</a>.
<h3>Command to run post-export</h3>
Any part of the command-line enclosed in double-quotes (") will be used as-is.
{% children %}
-
-
layout: default
title: Default Keyboard Bindings
menu-title: Key Bindings
----
+---
<p>
Almost every available function in Ardour can be bound to a keyboard
shortcut (and those few that cannot will usually respond to an <a
href="/using-control-surfaces/controlling-ardour-with-osc/"><abbr
- title="Open Sound Control">OSC</abbr> command</a>). Ardour comes with a
+ title="Open Sound Control">OSC</abbr> command</a>). Ardour comes with a
rich set of default <dfn>key bindings</dfn> for the most commonly used
functions.
</p>
-<p>These bindings strive to be <dfn>mnemonic</dfn>, that is, easy and intuitive
- to remember, and follow widely accepted conventions. As a general rule,
- the first letter of an operation will be used for as a shortcut, if
- available. This does not necessarily lead to the best ergonomics for
- rapid editing — there are alternative binding sets for that —
- but it does make it simpler for newcomers to remember some of the most
+
+<p>These bindings strive to be <dfn>mnemonic</dfn>, that is, easy and intuitive
+ to remember, and follow widely accepted conventions. As a general rule,
+ the first letter of an operation will be used for as a shortcut, if
+ available. This does not necessarily lead to the best ergonomics for
+ rapid editing — there are alternative binding sets for that —
+ but it does make it simpler for newcomers to remember some of the most
useful ones, for example<br />
<kbd>S</kbd> for <kbd class="menu">Region > Edit > Split"</kbd>
or<br />
<kbd>P</kbd> for <kbd class="menu">Transport > Playhead > Playhead to Mouse</kbd>.
</p>
+
+<p>
+ Existing key bindings in menus are listed on the right side of the
+ menu items. To create a custom key binding for a menu item quickly, navigate to
+ the relevant (sub-) menu, hover over the item with the mouse and press
+ the desired combination of modifiers and key.
+</p>
+
+<p class="warning">
+ Ardour will silently re-assign the binding if you use a key
+ combination that is already in use, possibly removing a standard
+ keyboard shortcut without warning you. That might lead to confusion
+ when you ask other users for help, and they explain something in terms
+ of a standard key binding, which will then have a completely
+ different effect on your system.
+</p>
+
<p>
- Almost every key binding in Ardour can be changed in
+ Almost every key binding in Ardour can be looked for and/or changed in
<kbd class="menu">Window > Key Bindings</kbd>.
</p>
+
<p>
The conventions for using modifier keys (<kbd class="mod1"> </kbd>, <kbd
- class="mod2"> </kbd>, <kbd class="mod3"> </kbd> etc.) differ among platforms, so we
+ class="mod2"> </kbd>, <kbd class="mod3"> </kbd> etc.) differ among platforms, so we
provide different default bindings for each.
</p>
+
{% children %}
<p>
<strong>Click audio file:</strong> sets a user defined sound to be
played when Ardour's metronome is enabled in the
- <a href="/controlling-playback/using-the-transport-bar/">
+ <a href="/ardours-interface/transport-bar-and-times/the-transport-bar/">
Transport Bar</a>
</p>
</li>
<p>
This tab contains settings that relate to the behavior of the
- <a href="/controlling-playback/using-the-transport-bar/">Transport Bar</a>
+ <a href="/ardours-interface/transport-bar-and-times/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="/editing-and-arranging/snap-to-the-grid/">snap mode</a> to
+ <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">snap mode</a> to
<strong>No Grid</strong>.
</p>
</li>
---
<p>
- This tab contains settings that affect <a href="/ardours-interface/meters/">
+ This tab contains settings that affect <a href="/meters/">
Metering</a> in Ardour.
</p>
part: subchapter
---
----
-title: Key Bindings
-include: _manual/02_introducing-ardour/03_basic-gui-operations/02_key-bindings.html
-part: subchapter
----
-
---
title: Selection Techniques
-include: _manual/02_introducing-ardour/03_basic-gui-operations/03_selection-techniques.html
+include: _manual/02_introducing-ardour/03_basic-gui-operations/02_selection-techniques.html
part: subchapter
---
---
title: Tooltips
-include: _manual/02_introducing-ardour/03_basic-gui-operations/04_tooltips.html
+include: _manual/02_introducing-ardour/03_basic-gui-operations/03_tooltips.html
part: subchapter
---
---
title: Undo/Redo for Editing
-include: _manual/02_introducing-ardour/03_basic-gui-operations/05_undoredo-for-editing-.html
+include: _manual/02_introducing-ardour/03_basic-gui-operations/04_undoredo-for-editing-.html
part: subchapter
---
---
title: Using the Mouse
-include: _manual/02_introducing-ardour/03_basic-gui-operations/06_using-the-mouse.html
+include: _manual/02_introducing-ardour/03_basic-gui-operations/05_using-the-mouse.html
part: subchapter
---
---
title: Cut and Paste Operations
-include: _manual/02_introducing-ardour/03_basic-gui-operations/07_cut-and-paste-operations.html
+include: _manual/02_introducing-ardour/03_basic-gui-operations/06_cut-and-paste-operations.html
part: subchapter
---
---
title: Deleting Objects
-include: _manual/02_introducing-ardour/03_basic-gui-operations/08_deleting-objects.html
+include: _manual/02_introducing-ardour/03_basic-gui-operations/07_deleting-objects.html
part: subchapter
---
---
title: The Mixer - The Master Strip
-include: _manual/05_ardours-interface/05_the-mixer/04_the-master-strip.html
+include: _manual/05_ardours-interface/05_the-mixer/04_audio-midi-mixer-strips.htm
+part: subchapter
+---
+
+---
+title: The Mixer - The Master Strip
+include: _manual/05_ardours-interface/05_the-mixer/05_busses-mixer-strips.html
+part: subchapter
+---
+
+---
+title: The Mixer - The Master Strip
+include: _manual/05_ardours-interface/05_the-mixer/06_control-masters.html
+part: subchapter
+---
+
+---
+title: The Mixer - The Master Strip
+include: _manual/05_ardours-interface/05_the-mixer/07_the-master-bus-strip.html
part: subchapter
---
---
title: The Mixer - The Monitor Section
-include: _manual/05_ardours-interface/05_the-mixer/05_monitoring.html
+include: _manual/05_ardours-interface/05_the-mixer/08_monitoring.html
part: subchapter
---
---
title: Adding Tracks, Busses and VCAs
-include: _manual/11_working-with-tracks/03_adding-tracks-and-busses.html
+include: _manual/11_working-with-tracks/02_adding-tracks-and-busses.html
part: subchapter
---
---
title: Selecting Tracks
-include: _manual/11_working-with-tracks/04_selecting-tracks.html
+include: _manual/11_working-with-tracks/03_selecting-tracks.html
part: subchapter
---
---
title: Controlling Track Appearance
-include: _manual/11_working-with-tracks/05_controlling-track-appearance.html
+include: _manual/11_working-with-tracks/04_controlling-track-appearance.html
part: subchapter
---
---
title: Controlling Track Ordering
-include: _manual/11_working-with-tracks/06_controlling-track-ordering.html
+include: _manual/11_working-with-tracks/05_controlling-track-ordering.html
part: subchapter
---
---
title: Bus Controls
-include: _manual/11_working-with-tracks/07_bus-controls.html
+include: _manual/11_working-with-tracks/06_bus-controls.html
part: subchapter
---
---
title: Audio Track Controls
-include: _manual/11_working-with-tracks/08_audio-track-controls.html
+include: _manual/11_working-with-tracks/07_audio-track-controls.html
part: subchapter
---
---
title: MIDI Track Controls
-include: _manual/11_working-with-tracks/09_midi-track-controls.html
+include: _manual/11_working-with-tracks/08_midi-track-controls.html
part: subchapter
---
---
title: Track Context Menu
-include: _manual/11_working-with-tracks/11_track-context-menu.html
+include: _manual/11_working-with-tracks/10_track-context-menu.html
part: subchapter
---
---
title: Track and Bus Groups
-include: _manual/11_working-with-tracks/10_track-and-bus-groups.html
+include: _manual/11_working-with-tracks/9_track-and-bus-groups.html
part: subchapter
---
part: subchapter
---
----
-title: Busses and VCAs
-include: _manual/11_working-with-tracks/02_busses-and-vcas.html
-part: subchapter
----
-
---
title: Aux Sends
include: _manual/15_signal-routing/01_aux-sends.html
projects / ardour-manual-diverged / commitdiff
