<kbd class="menu">Edit > Preferences</kbd> dialog.
</p>
-<p class="fixme">This may have been true in the past, but now, considering that the startup dialog lets one tune JACK parameters up front, this is prety much bollocks. The rest is wrong as well</p>
<p>
- In general, it is sensible to start JACK before you run Ardour. This is not
- necessary, but will provide you with more control and options over JACK's
- operation.
+ If you want to use JACK, in general, it is sensible to start <em>before</em> you run Ardour. This is not necessary, but will provide you with more control and options over JACK's operation. You can start JACK through its <abbr title="Command Line Interface">CLI</abbr>, or using a <abbr title="Graphical User Interface">GUI</abbr> 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
- the <kbd class="menu">Session > New...</kbd> dialog. If JACK is not already
- running, there will be an extra <kbd class="menu">Audio Engine</kbd> tab in
- that dialog to configure JACK, which Ardour will then start automatically.
-</p>
-
-<p>
- If you did specify an existing session but JACK is not already running, the
- <kbd class="menu">New Session</kbd> dialog will contain just the Audio Engine tab.
+ 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.
</p>
---
<p>
<img alt="the Ableton Push 2 surface" src="/images/push2-main.jpg">
</p>
+
<p>
- Since version 5.4, Ardour has had full support for the Ableton
+ Since version 5.4, Ardour has had extensive support for the Ableton
Push2. This is an expensive but beautifully engineered control
surface primarily targetting the workflow found in Ableton's Live
- software and other similar tools such as Bitwig. As of 5.4, Ardour
- does not offer the same kind of workflow, so we have repurposed the
+ software and other similar tools such as Bitwig. As of version 5.4, Ardour
+ does not offer the same kind of workflow, so we have designed our support for the
Push 2 to be used for mixing and editing and musical performance,
without the clip/scene oriented approach in Live. This may change in
future versions of Ardour.
</p>
<h2>Connecting the Push 2</h2>
+
<p>
Plug the USB cable from the Push 2 into a USB2 or USB3 port on your
computer. For brighter backlighting, also plug in the power supply
(this is not necessary for use).
</p>
-<p>ft
-
+
+<p>
The Push 2 will be automatically recognized by your operating
system, and will appear in any of the lists of possible MIDI ports
in both Ardour and other similar software.
</p>
+
<p>
To connect the Push 2 to Ardour, open the Preferences dialog, and
then click on "Control Surfaces". Click on the "Enable" button
in the line that says "Ableton Push 2" in order to activate Ardour's
Push 2 support.
</p>
+
<p>
Once you select the input and output port, Ardour will initialize
the Push 2 and it will be ready to use. You only need do this
</p>
<h2>Push 2 Configuration</h2>
+
<p>
The only configuration option at this time is whether the pads send
aftertouch or polyphonic pressure messages. You can alter this
setting via the Push 2 GUI, accessed by double-clicking on the "Push
2" entry in the control surfaces list.
<p>
+
<img alt="the Push 2 configuration dialog"
src="/images/push2-gui.png">
</p>
<h2>Basic Concepts</h2>
+
<p>
With the Push 2 support in Ardour 5.4, you can do the following
things:
"in-key" and "chromatic" pad layouts.</dd>
</dl>
- ... plus a variety of tasks related to transport control, selection,
+ … plus a variety of tasks related to transport control, selection,
import, click track control and more.
</p>
<h2>Musical Performance</h2>
+
<p>
Messages sent from the 8x8 pad grid and the "pitch bend bar" are
routed to a special MIDI port within Ardour called "Push 2 Pads"
behaviour of Ardour's Push 2 support is to connect the pads to the
most recently selected MIDI track.
</p>
+
<p>
This means that to play a soft-synth/instrument plugin in a given
MIDI track with the Push 2, you just need to select that track.
</p>
+
<p>
If multiple MIDI tracks are selected at once, the first selected
track will be used. Note that messages originating from all other
</p>
<h2>Global Mix</h2>
+
<p>
This is the default mode that Ardour will start the Push 2 in. In
this mode, the 8 knobs at the top of the device, the 8 buttons below
them, the video display and the 8 buttons below that are combined to
provide a global view of the session mix.
</p>
+
<p>
<img alt="global mix mode on Push2 screen"
src="/images/push2-globalmix.png">
</p>
+
<p>
The upper buttons are labelled by text in the video display just
below them. Pressing one of the buttons changes the function of the
knobs, and the parameters that will shown for each track/bus in the
display.
</p>
+
<p>
As of Ardour 5.4, the possible parameters are:
<dl>
indicating the pan width setting for the corresponding
track/bus. The physical knob can be turned to adjust the
width.
- </p>
- <p>
+ </p>
+
+ <p>
Unlike many DAWs, Ardour's stereo panners have "width"
parameter that defaults to 100%. You cannot change the pan
direction/azimuth of a track with 100% width, but must first
</dd>
</dl>
</p>
+
<p>
To change which tracks are shown while in global mix mode, use the
left and right arrow/cursor keys just below and to the right of the
display. Tracks and busses that are hidden in Ardour's GUI will also
be hidden from display on the Push 2.
</p>
+
<p>
To select a track/bus directly from the Push 2, press the
corresponding button below the display. The track name will be
</p>
<h3>Soloing and Muting in Global Mix mode</h3>
+
<p>
The Solo and Mute buttons to the left of the video display can be
used to solo and mute tracks while in Global Mix mode. The operation
will be applied to the <em>first</em> currently selected
track(s).
</p>
+
<p>
There are two indications that one or more tracks are soloed:
<ol>
"-" if they are muted due to soloing.</li>
</ol>
</p>
+
<p>
To cancel solo, either:
<ul>
</dd>
<dt>Play</dt>
<dd>
- Starts and stops the transport.
+ Starts and stops the transport. Press Shift-Play to return to the session start.
</dd>
<dt>Add Track</dt>
<dd>
part: subchapter
---
-<p>The region list shows all the regions in the session. The left-hand column gives the region name, and there are a range of times given for information. At the right of the list are four columns of flags that can be altered:</p>
+<p>
+ The region list shows all the regions in the session. The left-hand column gives the region name, and there are a range of times given for information:
+</p>
+
+<dl>
+ <dt>Position</dt><dd>position of the start of the region on the global timeline</dd>
+ <dt>End</dt><dd>position of the region on the global timeline</dd>
+ <dt>Length</dt><dd>duration of the region</dd>
+ <dt>Sync</dt><dd>position of the sync point, relative to the start of region (can be negative)</dd>
+ <dt>Fade In</dt><dd>duration of the fade in. Can't be less than 1 ms, to avoid clipping.</dd>
+ <dt>Fade Out</dt><dd>duration of the fade out (positive value, ≥ 1 ms).</dd>
+</dl>
+
+<p>
+ The units used to display those times are those used for the clock, so changing the units on the clocks change the display of this values.
+</p>
+
+<p>
+ At the right of the list are four columns of flags that can be altered:
+</p>
+
<dl>
-<dt>L</dt>
-<dd>whether the region position is locked, so that it cannot be moved.</dd>
-<dt>G</dt>
-<dd>whether the region's position is ‘glued’ to bars and beats. If so, the region will stay at the same position in bars and beats even if the tempo and/or time signature change.</dd>
-<dt>M</dt>
-<dd>whether the region is muted, so that it will not be heard.</dd>
-<dt>O</dt>
-<dd>whether the region is opaque; opaque regions ‘block’ regions below them from being heard, whereas ‘transparent’ regions have their contents mixed with whatever is underneath. </dd>
+ <dt>L</dt>
+ <dd>whether the region position is locked, so that it cannot be moved.</dd>
+ <dt>G</dt>
+ <dd>whether the region's position is ‘glued’ to bars and beats. If so, the region will stay at the same position in bars and beats even if the tempo and/or time signature change.</dd>
+ <dt>M</dt>
+ <dd>whether the region is muted, so that it will not be heard.</dd>
+ <dt>O</dt>
+ <dd>whether the region is opaque; opaque regions ‘block’ regions below them from being heard, whereas ‘transparent’ regions have their contents mixed with whatever is underneath. </dd>
</dl>
-<p>Hovering the mouse pointer over a column heading shows a tool-tip which can be handy to remember what the columns are for.</p>
-<p>A handy feature of the region list is that its regions can be dragged and dropped into a suitable track in the session.</p>
+
+<p>
+ Hovering the mouse pointer over a column heading shows a tool-tip which can be handy to remember what the columns are for.
+</p>
+
+<p>
+ 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: Snapshot List
part: subchapter
---
-<p>This shows the track/bus groups that exist in the session. These groups allow related tracks to share various properties (such as mute or record enable state). For full details, see the section called
-<a href="/working-with-tracks/track-and-bus-groups/">Track and Bus Groups</a>.</p>
-<p>The columns in this list are as follows:</p>
+<p>
+ This shows the track/bus groups that exist in the session. These groups allow related tracks to share various properties (such as mute or record enable state). For full details, see the section called <a href="/working-with-tracks/track-and-bus-groups/">Track and Bus Groups</a>.
+</p>
+
+<p>
+ The columns in this list are as follows:
+</p>
+
<dl>
-<dt>Col</dt>
-<dd>the colour that the group uses for its tab in the editor.</dd>
-<dt>Name</dt>
-<dd>the group name.</dd>
-<dt>V</dt>
-<dd>whether the tracks and busses in the group are visible.</dd>
-<dt>On</dt>
-<dd>whether the group is enabled.</dd>
-<dt>G</dt>
-<dd>ticked if the constituents of the group are sharing gain settings.</dd>
-<dt>Rel</dt>
-<dd>ticked if shared gains are relative.</dd>
-<dt>M</dt>
-<dd>ticked if the constituents share mute status.</dd>
-<dt>S</dt>
-<dd>ticked if the constituents share solo status.</dd>
-<dt>Rec</dt>
-<dd>ticked if the constituents share record-enable status.</dd>
-<dt>Mon</dt>
-<dd>whether the constituents share monitor settings.</dd>
-<dt>Sel</dt>
-<dd>whether the constituents are selected together.</dd>
-<dt>E</dt>
-<dd>whether edits to the constituents are performed to all others.</dd>
-<dt>A</dt>
-<dd>whether the constituents share active status. </dd>
+ <dt>Col</dt>
+ <dd>the colour that the group uses for its tab in the editor.</dd>
+ <dt>Name</dt>
+ <dd>the group name.</dd>
+ <dt>V</dt>
+ <dd>whether the tracks and busses in the group are visible.</dd>
+ <dt>On</dt>
+ <dd>whether the group is enabled.</dd>
+ <dt>G</dt>
+ <dd>ticked if the constituents of the group are sharing gain settings.</dd>
+ <dt>Rel</dt>
+ <dd>ticked if shared gains are relative.</dd>
+ <dt>M</dt>
+ <dd>ticked if the constituents share mute status.</dd>
+ <dt>S</dt>
+ <dd>ticked if the constituents share solo status.</dd>
+ <dt>Rec</dt>
+ <dd>ticked if the constituents share record-enable status.</dd>
+ <dt>Mon</dt>
+ <dd>whether the constituents share monitor settings.</dd>
+ <dt>Sel</dt>
+ <dd>whether the constituents are selected together.</dd>
+ <dt>A</dt>
+ <dd>whether the constituents share active status. </dd>
</dl>
-<p> </p>
---
title: Tracks & Busses List
part: subchapter
---
-<p>This lists the tracks and busses that are present in the session. The list order reflects the order in the editor, and you can drag-and-drop track or bus names in the editor list to re-order them in the editor. The columns in the list can all be clicked to alter the track/bus state, and they represent the following:</p>
+<p>
+ This lists the tracks and busses that are present in the session. The list order reflects the order in the editor, and you can drag-and-drop track or bus names in the editor list to re-order them in the editor. The columns in the list represent the following:
+</p>
+
<dl>
-<dt id="visible">V</dt>
-<dd>whether the track or bus is visible; they can be hidden, in which case they will still play, but just not be visible in the editor; this can be useful for keeping the display uncluttered.</dd>
-<dt id="active">A</dt>
-<dd>whether the track or bus is active; unactive tracks will not play, and will not consume any CPU.</dd>
-<dt id="input">I</dt>
-<dd>for MIDI tracks, whether the MIDI input is enabled; this dictates whether MIDI data from the track's inputs ports will be passed through the track.</dd>
-<dt id="record">R</dt>
-<dd>whether the track is record-enabled.</dd>
-<dt id="mute">M</dt>
-<dd>whether the track is muted.</dd>
-<dt id="solo">S</dt>
-<dd>track solo state.</dd>
-<dt id="solo-isolated">SI</dt>
-<dd>track solo-isolated state.</dd>
-<dt id="solo-safe">SS</dt>
-<dd>solo safe state. </dd>
+ <dt id="visible">V</dt>
+ <dd>whether the track or bus is visible; they can be hidden, in which case they will still play, but just not be visible in the editor; this can be useful for keeping the display uncluttered.</dd>
+ <dt id="active">A</dt>
+ <dd>whether the track or bus is active; unactive tracks will not play, and will not consume any CPU.</dd>
+ <dt id="input">I</dt>
+ <dd>for MIDI tracks, whether the MIDI input is enabled; this dictates whether MIDI data from the track's inputs ports will be passed through the track.</dd>
+ <dt id="record">R</dt>
+ <dd>whether the track is record-enabled.</dd>
+ <dt id="record-safe">RS</dt>
+ <dd>whether the track is record safe; a record safe track cannot be armed for recording, to protect against a mistake.</dd>
+ <dt id="mute">M</dt>
+ <dd>whether the track is muted.</dd>
+ <dt id="solo">S</dt>
+ <dd>track solo state.</dd>
+ <dt id="solo-isolated">SI</dt>
+ <dd>track solo-isolated state.</dd>
+ <dt id="solo-safe">SS</dt>
+ <dd>solo safe state. </dd>
</dl>
-<p>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>
+
+<p class="note">
+ Each icon in these columns can be clicked to toggle the track/bus state, which is a very fast way to set multiple tracks/busses state at once.
+</p>
+
+<p>
+ 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: The Editing Toolbar
<li><a href="/ardours-interface/using-ardour-clock-displays/">the Clocks</a></li>
<li>3 status indicators:
<ul>
- <li><dfn>Solo</dfn>: Blinks when 1 or more track(s) are being soloed, see <a href="/mixing/muting-and-soloing/">Muting and Soloing</a>. Clicking this button while active toggles the solo off on all tracks.</li>
+ <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 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>
</p>
<ul>
- <li><dfn>Midi Panic</dfn>: allows to immediately stop 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/looping-the-transport/">loop</a> as defined by the <a href="/working-with-markers/loop-range/">Loop range</a>, until the "Stop playback" button is pressed. Clicking the "Play loop Range" button while already active switches to normal Play mode, which allows to exit the loop without stopping and restarting the playback.</li>
- <li><dfn>Play Range/Selection</dfn>: If a range has been defined using the Range Mode button, plays the range, of if an audio or MIDI region is selected, plays this region. In both cases, the playback stops at the end of the range or selected region.</li>
- <li><dfn>Play from playhead</dfn>: Starts the playback and optionally record (more bellow).</li>
- <li><dfn>Stop</dfn>: Whatever the playing mode (loop, range, ...) stops all playback. Some effects (like chorus) might still be audible for a while.</li>
- <li><dfn>Toggle Record</dfn>: Global switch button to activate/deactivate recording. While active, the button blinks red. The button doesn't start the recording itself: if one or more tracks are marked as record-enabled, pressing the "Play from Playhead" starts the recording on this/these track(s). See <a href="/recording/">Recording</a>.</li>
+ <li>
+ <dfn>Midi Panic</dfn>: allows to immediately stop 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/looping-the-transport/">loop</a> as defined by the <a href="/working-with-markers/loop-range/">Loop range</a>, until the "Stop playback" button is pressed. Clicking the "Play loop Range" button while already active switches to normal Play mode, which allows to exit the loop without stopping and restarting the playback.
+ </li>
+ <li>
+ <dfn>Play Range/Selection</dfn>: If a range has been defined using the Range Mode button, plays the range, of if an audio or MIDI region is selected, plays this region. In both cases, the playback stops at the end of the range or selected region.
+ </li>
+ <li>
+ <dfn>Play from playhead</dfn>: Starts the playback and optionally record (more bellow).
+ </li>
+ <li>
+ <dfn>Stop</dfn>: Whatever the playing mode (loop, range, …) stops all playback. Depending on other settings, some effects (like chorus or reverb) might still be audible for a while.
+ </li>
+ <li>
+ <dfn>Toggle Record</dfn>: Global switch button to activate/deactivate recording. While active, the button blinks red. The button doesn't start the recording itself: if one or more tracks are marked as record-enabled, pressing the "Play from Playhead" starts the recording on this/these track(s). See <a href="/recording/">Recording</a>.
+ </li>
</ul>
<p class="fixme">Language in the above paragraphs is awkward</p>
<p class="note">
- All these actions are bound to keyboard shortcuts, which allows for speedier use and more focus while working.
+ All these actions are bound to keyboard shortcuts, which allows for speedier use and more focused work.
</p>
<p>
</p>
<ul>
- <li><dfn>Internal/MTC</dfn> defines if the current timecode is handled by Ardour, or by an external Midi device (see <a href="/synchronization/timecode-generators-and-slaves/">Timecode Generators and Slaves</a>).</li>
- <li><dfn>Follow Edits</dfn> is a toggle switch that defines if the playhead is moved when using the Grab Mode or the Range Mode tools, i.e. if any action on the canvas moves the playhead along.</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 part of the audio before and after having tweaked it, without having to loop on it.</li>
+ <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 earing back the same part of the audio before and after having tweaked it, without having to loop on it.
+ </li>
</ul>
</p>
<p>
- We then locate bar 4 in the bbt ruler and while holding the constraint modifier, drag it to bar 4 in the drum performance.
+ We then locate bar 4 in the BBT ruler and while holding the constraint modifier, drag it to bar 4 in the drum performance.
</p>
<p>
</p>
<p class="note">
- Notice what is happeneing here: the tempo previous to your mouse pointer is being changed so that the beat you grabbed aligns with the pointer. Notice that the tempo lines previous to the changed one also move. This is because the previous tempo is ramping <strong>to</strong> the tempo you are changing. Look further to the left. The tempo lines in the first four bars do not move.
+ Notice what is happening here: the tempo previous to your mouse pointer is being changed so that the beat you grabbed aligns with the pointer. Notice that the tempo lines previous to the changed one also move. This is because the previous tempo is ramping <strong>to</strong> the tempo you are changing. Look further to the left. The tempo lines in the first four bars do not move.
</p>
<p>
projects / ardour-manual-diverged / blobdiff