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>
----
-title: Starting Ardour From the Command Line (Linux)
-menu_title: Starting from Linux Cmdline
-part: subchapter
----
+<h2>Starting Ardour From the Command Line (Linux)</h2>
<p>
Like (almost) any other program on Linux, Ardour can be started on the
</p>
<kbd class="cmd lin">ardour5 -N <em>/path/to/session</em></kbd>
-<h3>Other Command Line Options</h3>
-
---
title: Keyboard and Mouse Shortcuts
+
---
-title: System Configuration
+title: Ardour Configuration
part: part
---
---
-title: Peripherals
+title: Configuring MIDI
part: chapter
---
---
-title: Controlling Ardour with OSC
-include: controlling-ardour-with-osc.html
-exclude: yes
+title: Using External MIDI Devices
part: subchapter
---
----
-title: Controlling Ardour with OSC (Ardour 4.7 and Prior)
-include: controlling-ardour-with-osc-4.7-and-prior.html
-exclude: yes
-part: subchapter
----
+<p class="fixme">Add content</p>
+
---
-title: OSC Feedback With Ardour
+title: Setting Up MIDI
part: subchapter
---
+<h2>What Can Ardour Do With MIDI?</h2>
<p>
- Feedback from the Ardour to the the control surface is very useful for
- a number of things. Motor faders need to know where the the track
- they have been attached to is at before they were assigned otherwise
- the DAW fader will jump to where the controller fader is. Likewise,
- the buttons on each strip need to know what their value is so they can
- light their LED correctly. Transport controls should let you know if
- they are active too. This is what feedback is all about.
+ <dfn><abbr title="Musical Instrument Digital
+ Interface">MIDI</abbr></dfn> is a way to describe musical
+ performances and to control music hardware and software.
</p>
-
-<p>
- Ardour does feedback by sending the same path back that is used to
- control the same function. As such any controls that have feedback
- have a parameter that is the value of the control or it's state
- (on or off). In the case of OSC paths listed on the main OSC page
- as having no parameter, if they have feedback, they will also work
- with a 1 for button press and 0 for button release. This is because
- many OSC controllers will only use exactly the same path for feedback
- as for control. For example:
+<p>Ardour can import and record MIDI data, and perform a variety of
+ editing operations on it. Furthermore, MIDI can be used to control
+ various functions of Ardour.
</p>
-<dl class="bindings">
- <dt><kbd class="osc">/transport_stop</kbd></dt>
- <dd></dd>
-</dl>
-
-<p>can be used also in the form:</p>
-
-<dl class="bindings">
- <dt><kbd class="osc">/transport_stop <em>press</em></kbd></dt>
- <dd>where <em>press</em> is an int/bool indicating if the button is pressed or not.</dd>
-</dl>
-
+<h2>MIDI Handling Frameworks</h2>
<p>
- The feedback does not have the same meaning as the control message.
- Where the button release sent to Ardour will be ignored and has no
- meaning. Both states have meaning in feedback to the controller.
- The feedback will be:
+ MIDI input and output for Ardour are handled by the same "engine"
+ that handles audio input and output. Up to release 3.5, that means
+ that all MIDI I/O takes place via JACK. JACK itself uses the
+ native MIDI support of the operating system to receive and send
+ MIDI data. The native MIDI support provides device drivers for MIDI
+ hardware and libraries needed by software applications that want to
+ work with MIDI.
</p>
-<dl class="bindings">
- <dt><kbd class="osc">/transport_stop <em>state</em></kbd></dt>
- <dd>where <em>state</em> is an int/bool indicating if the transport is stopped or not.</dd>
+<dl>
+<dt>OS X</dt>
+<dd> <dfn>CoreMIDI</dfn> is the standard MIDI framework on OSX systems.
+</dd>
+<dt>Linux</dt>
+<dd>
+ <dfn><abbr title="Advanced Linux Sound API">ALSA</abbr> MIDI</dfn>
+ is the standard MIDI framework on Linux systems.
+</dd>
</dl>
-<p>
- With feedback turned on, OSC control commands that try to change a
- control that does not exist will get feedback that resets that control
- to off. For example, sending a /strip/recenable to a buss will not work
- and Ardour will try to turn the controller LED off in that case. Also
- note that Pan operation may be limited by pan width in some cases.
- That is with pan width at 100% (or -100%) there is no pan position
- movement available.
-</p>
-<p>
- It may come as a surprise, but feedback often generates more network
- traffic than control itself does. Some things are more obvious like
- head position or meters. But even a simple button push like transport
- start sends not only a signal to turn on the play LED, but also one to
- turn off the stop LED, the Rewind LED, the Fast Forward LED and the
- Loop LED. That is still minor, think instead of a surface refresh
- such as happens when the surface is first connected and then most of
- that happens every time the fader strips are banked. This is why
- feedback is enabled in sections so that as little feedback as is
- actually needed is sent. This is also a consideration if the surface
- is connected via wifi.
-</p>
-<h2>List of OSC feedback messages</h2>
-<h3>Feedback only</h3>
-<p>
- These messages are feedback only. They are sent as status from Ardour
- and some of them may be enabled separately from other feedback. See:
- <a href="/using-control-surfaces/controlling-ardour-with-osc/calculating-feedback-and-strip-types-values/">
- Calculating Feedback and Strip-types Values.</a>
-</p>
<p class="note">
- See strip section below for info about ssid and wrapping it into the
- path. Also /master and /monitor support what the /strip does.
+ On Linux systems, <dfn>QJackCtl</dfn> control software displays ALSA MIDI
+ ports under its "ALSA" tab (it does not currently display CoreMIDI
+ ports). By contrast, JACK MIDI ports show up under
+ the <kbd class="menu">MIDI</kbd> tab in QJackCtl.
</p>
+
+<h2>JACK MIDI Configuration</h2>
<p>
- In the case where Gainmode is set to position, the track name will
- show the dB value while values are changing.
+By default, JACK will <strong>not</strong> automatically detect and use existing MIDI
+ports on your system. You must choose one of several ways
+of <dfn>bridging</dfn> between the native MIDI frameworks
+(e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections
+below.
</p>
-<dl class="bindings">
- <dt><kbd class="osc">/strip/name <em>ssid</em> <em>track_name</em></kbd></dt>
- <dd>where <em>track_name</em> is a string representing the name of the track</dd>
- <dt><kbd class="osc">/session_name <em>session_name</em></kbd></dt>
- <dd>where <em>session_name</em> is a string representing the name of the session</dd>
- <dt><kbd class="osc">/strip/meter <em>ssid</em> <em>meter</em></kbd></dt>
- <dd>where <em>meter</em> is a value repesenting the current audio level.
- (the exact math used is determined by the feedback bits set)</dd>
- <dt><kbd class="osc">/strip/signal <em>ssid</em> <em>signal</em></kbd></dt>
- <dd>where <em>signal</em> is a float indicating the instantaneous
- audio level is -40dB or higher.</dd>
- <dt><kbd class="osc">/position/smpte <em>time</em></kbd></dt>
- <dd>where <em>time</em> is a string with the current play head time. Seconds as per smpte.</dd>
- <dt><kbd class="osc">/position/bbt <em>beat</em></kbd></dt>
- <dd>where <em>beat</em> is a string with the current play head bar/beat.</dd>
- <dt><kbd class="osc">/position/time <em>time</em></kbd></dt>
- <dd>where <em>time</em> is a string with the current play head time. Seconds are in milliseconds</dd>
- <dt><kbd class="osc">/position/samples <em>samples</em></kbd></dt>
- <dd>where <em>samples</em> is a string with the current play head position in samples.</dd>
- <dt><kbd class="osc">/heartbeat <em>LED</em></kbd></dt>
- <dd>where <em>LED</em> is a float that cycles 1/0 at 1 second intervals.</dd>
- <dt><kbd class="osc">/record_tally <em>state</em></kbd></dt>
- <dd>Some record enable is true or "ready to record". For a "Recording" sign at studio door.</dd>
-</dl>
-<h3>Transport Control</h3>
-<dl class="bindings">
- <dt><kbd class="osc">/transport_stop <em>state</em></kbd></dt>
- <dd><em>state</em> is true when transport is stopped</dd>
- <dt><kbd class="osc">/transport_play <em>state</em></kbd></dt>
- <dd><em>state</em> is true when transport speed is 1.0</dd>
- <dt><kbd class="osc">/ffwd <em>state</em></kbd></dt>
- <dd><em>state</em> is true when transport is moving forward but not at speed 1.0</dd>
- <dt><kbd class="osc">/rewind <em>state</em></kbd></dt>
- <dd><em>state</em> is true when transport speed is less than 0.0</dd>
- <dt><kbd class="osc">/loop_toggle <em>state</em></kbd></dt>
- <dd><em>state</em> is true when loop mode is true</dd>
- <dt><kbd class="osc">/cancel_all_solos <em>state</em></kbd></dt>
- <dd>Where <em>state</em> true indicates there are active solos that can be canceled.</dd>
-</dl>
+---
+title: MIDI on Linux
+part: subchapter
+---
-<h3>Recording control</h3>
-<dl class="bindings">
- <!--dt><kbd class="osc">/toggle_punch_in</kbd></dt>
- <dd></dd>
- <dt><kbd class="osc">/toggle_punch_out</kbd></dt>
- <dd></dd-->
- <dt><kbd class="osc">/rec_enable_toggle <em>state</em></kbd></dt>
- <dd>Master record enabled.</dd>
+<p>The right approach for using MIDI on Linux depends on which version of
+JACK you use. The world divides into:</p>
+
+<dl>
+<dt>Systems using JACK 1, versions 0.124 or later</dt>
+<dd>On these systems, just start JACK with the <code>-X alsa_midi</code> server argument. To support legacy control applications, you can also use the <code>-X seq</code> argument to the ALSA backend of JACK and get the exact same results.</dd>
+<dt>All others</dt>
+<dd>Use a2jmidid to act as a bridge between ALSA MIDI and JACK. Do not use the <code>-X seq</code> or <code>-X raw</code> arguments—the timing and performance of these options is not acceptable.
+</dd>
</dl>
-<h3>Master and monitor strips</h3>
+<h2>a2jmidid</h2>
+
<p>
- Master and monitor strips are similar to track strips but do not use
- the SSID. Rather they use their name as part of the path:
+ <dfn>a2jmidid</dfn> is an application that bridges between the system
+ <abbr title="Musical Instrument Digital Interface">MIDI</abbr> ports and
+ <abbr title="JACK Audio Connection Kit">JACK</abbr>.
</p>
-<dl class="bindings">
- <dt><kbd class="osc">/master/gain <em>dB</em></kbd></dt>
- <dd>where <em>dB</em> is a float ranging from -193 to +6 representing the actual gain of master in dB</dd>
- <dt><kbd class="osc">/master/fader <em>position</em></kbd></dt>
- <dd>where <em>position</em> is an int ranging from 0 to 1023 representing the fader control position</dd>
- <dt><kbd class="osc">/master/trimdB <em>dB</em></kbd></dt>
- <dd>where <em>dB</em> is a float ranging from -20 to +20 representing the actual trim for master in dB</dd>
- <dt><kbd class="osc">/master/pan_stereo_position <em>position</em></kbd></dt>
- <dd>where <em>position</em> is a float ranging from 0 to 1 representing the actual pan position for master</dd>
- <dt><kbd class="osc">/master/mute <em>yn</em></kbd></dt>
- <dd>where <em>yn</em> is a bool/int representing the actual mute state of the Master strip</dd>
- <dt><kbd class="osc">/monitor/gain <em>dB</em></kbd></dt>
- <dd>where <em>dB</em> is a float ranging from -193 to 6 representing the actual gain of monitor in dB</dd>
- <dt><kbd class="osc">/monitor/fader <em>position</em></kbd></dt>
- <dd>where <em>position</em> is an int ranging from 0 to 1023 representing the fader control position</dd>
-</dl>
-<h3>Track specific operations</h3>
<p>
- For each of the following, <em>ssid</em> is the surface strip ID for the track
-</p>
-<p class="note">
- Some Surfaces (many Android applets) are not able to deal with more
- than one parameter in a command. However, the two parameter commands
- below can also be sent as /strip/command/ssid param. Feedback can be
- set to match this with the /set_surface/feedback <em>state</em>
- command. See <a
- href="/using-control-surfaces/controlling-ardour-with-osc/calculating-feedback-and-strip-types-values/">
- Calculating Feedback and Strip-types Values.</a>
+ First you should make sure that there is no ALSA sequencer support enabled
+ in JACK. To do that open QJackCtl's <kbd class="menu">Setup</kbd> window.
</p>
-<dl class="bindings">
- <dt><kbd class="osc">/bank_up <em>LED</em></kbd></dt>
- <dd>where <em>LED</em> is a bool that indicates another bank_up operation is possible.</dd>
- <dt><kbd class="osc">/bank_down <em>LED</em></kbd></dt>
- <dd>where <em>LED</em> is a bool that indicates another bank_down operation is possible.</dd>
- <dt><kbd class="osc">/strip/name <em>ssid</em> <em>track_name</em></kbd></dt>
- <dd>where <em>track_name</em> is a string representing the name of the track
- (note there is no coresponding command to set the track name)</dd>
- <dt><kbd class="osc">/strip/mute <em>ssid</em> <em>mute_st</em></kbd></dt>
- <dd>where <em>mute_st</em> is a bool/int representing the actual mute state of the track</dd>
- <dt><kbd class="osc">/strip/solo <em>ssid</em> <em>solo_st</em></kbd></dt>
- <dd>where <em>solo_st</em> is a bool/int representing the actual solo state of the track</dd>
- <dt><kbd class="osc">/strip/monitor_input <em>ssid</em> <em>monitor_st</em></kbd></dt>
- <dd>where <em>monitor_st</em> is a bool/int. True/1 meaning the track is force to monitor input</dd>
- <dt><kbd class="osc">/strip/monitor_disk <em>ssid</em> <em>monitor_st</em></kbd></dt>
- <dd>where <em>monitor_st</em> is a bool/int. True/1 meaning the track is force to monitor disk,
- where both disk and input are false/0, auto monitoring is used.</dd>
- <dt><kbd class="osc">/strip/recenable <em>ssid</em> <em>rec_st</em></kbd></dt>
- <dd>where <em>rec_st</em> is a bool/int representing the actual rec state of the track</dd>
- <dt><kbd class="osc">/strip/record_safe <em>ssid</em> <em>rec_st</em></kbd></dt>
- <dd>where <em>rec_st</em> is a bool/int representing the actual record safe state of the track</dd>
- <dt><kbd class="osc">/strip/gain <em>ssid</em> <em>gain</em></kbd></dt>
- <dd>where <em>gain</em> is a float ranging from -193 to 6 representing the actual gain of the track in dB.</dd>
- <dt><kbd class="osc">/strip/fader <em>ssid</em> <em>position</em></kbd></dt>
- <dd>where <em>position</em> is an float ranging from 0 to 1 representing the actual fader position of the track.</dd>
- <dt><kbd class="osc">/strip/trimdB <em>ssid</em> <em>trim_db</em></kbd></dt>
- <dd>where <em>trim_db</em> is a float ranging from -20 to 20 representing the actual trim of the track in dB.</dd>
- <dt><kbd class="osc">/strip/pan_stereo_position <em>ssid</em> <em>position</em></kbd></dt>
- <dd>where <em>position</em> is a float ranging from 0 to 1 representing the actual pan position of the track</dd>
-</dl>
-<h3>Selection Operations</h3>
<p>
- Selection feedback is the same as for strips, only the path changes
- from <em>/strip</em> to <em>/select</em> and there is no <em>ssid</em>.
- there are some extra feedback and commands that will be listed here.
+ Set <kbd class="menu">Settings > MIDI Driver</kbd> to <kbd
+ class="input">none</kbd>.
+ Then uncheck the <kbd class="optoff">Misc > Enable ALSA Sequencer
+ support</kbd> option.<br />
+ Now it's time to restart your jack server before going on.
</p>
-<dl class="bindings">
- <dt><kbd class="osc">/select/n_inputs <em>number</em></kbd></dt>
- <dd>where <em>number</em> number of inputs for this strip</dd>
- <dt><kbd class="osc">/select/n_outputs <em>number</em></kbd></dt>
- <dd>where <em>number</em> number of outputs for this strip</dd>
- <dt><kbd class="osc">/select/comment <em>text</em></kbd></dt>
- <dd>where <em>text</em> is the strip comment</dd>
- <dt><kbd class="osc">/select/solo_iso <em>state</em></kbd></dt>
- <dd>where <em>state</em> is a bool/int representing the Actual solo isolate state of the track</dd>
- <dt><kbd class="osc">/select/solo_safe <em>state</em></kbd></dt>
- <dd>where <em>state</em> is a bool/int representing the actual solo safe/lock state of the track</dd>
- <dt><kbd class="osc">/select/polarity <em>invert</em></kbd></dt>
- <dd>where <em>invert</em> is a bool/int representing the actual polarity of the track</dd>
- <dt><kbd class="osc">/select/pan_stereo_width <em>width</em></kbd></dt>
- <dd>where <em>width</em> is a float ranging from 0 to 1 representing the actual pan width of the track</dd>
- <dt><kbd class="osc">/select/send_gain", <em>sendid</em> <em>send_gain</em></kbd></dt>
- <dd>where <em>sendid</em> = nth_send, <em>send_gain</em>is a float
- ranging from -193 to +6 representing the actual gain in dB for the send</dd>
- <dt><kbd class="osc">/select/send_fader", <em>sendid</em> <em>send_gain</em></kbd></dt>
- <dd>where <em>sendid</em> = nth_send, <em>send_gain</em>is a float
- ranging from 0 to 1 representing the actual position for the send as a fader</dd>
- <dt><kbd class="osc">/select/send_name <em>sendid</em> <em>send_name</em></kbd></dt>
- <dd>where <em>send_name</em> is a string representing the name of the buss
- this send goes to.</dd>
-</dl>
-<h3>Menu actions</h3>
+
+<h3>Check for a2jmidid availability</h3>
+
<p>
- Every single menu item in Ardour's GUI is accessible via OSC. However,
- there is no provision for returning the state of anything set this way.
- This is not a bad thing as most menu items either do not have an on/off
- state or that state is quite visible. Binding that affect other parameters
- that OSC does track will show on those OSC controls. Examples of this
- might be track record enable for tracks 1 to 32, play or stop.
+ First, check whether a2jmidid is already installed in your system. After
+ starting your JACK server, go to the command line and type
</p>
----
-title: Calculating Feedback and Strip-types Values
-part: subchapter
----
+<kbd class="cmd lin">a2jmidid -e</kbd>
<p>
- <em>/set_surface</em> has two values the user needs to calculate before
- use. In general these will not be calculated at run time, but
- beforehand. There may be more than one button with different values
- to turn various kinds of feedback on or off or to determine which
- kinds of strips are currently viewed/controlled.
+ If a2jmidid does not exist, install it with the software manager of your
+ Linux distribution and try again.
</p>
+<h2>Check available MIDI ports</h2>
+
<p>
- Both ,<em>feedback</em> and <em>strip-types</em> use bitsets to keep
- track what they are doing. Any number in a computer is made out of
- bits that are on or off, but we represent them as normal base 10
- numbers. Any one bit turned on will add a unique value to the
- number as a whole. So for each kind of feedback or strip type
- to be used, that number should be added to the total.
+ If you have correctly configured JACK for MIDI, then your MIDI ports should appear in
+ qjackctl under <kbd class="menu">Connections > MIDI </kbd>.
</p>
-<h3>strip_types</h3>
+<h3>Making it automatic</h3>
<p>
- strip_types is an integer made up of bits. The easy way to
- deal with this is to think of strip_types items being worth a number and
- then adding all those numbers together for a value to send.
- Strip Types will determine What kind of strips will be included in
- bank. This would include: Audio, MIDI, busses, VCAs, Master, Monitor
- and hidden or selected strips.
+Once you've verified that the ports appear in JACK as expected, you
+can make this happen whenever you start JACK.
</p>
-<ul>
- <li>
- 1 - AudioTracks.
- </li>
- <li>
- 2 - MidiTracks.
- </li>
- <li>
- 4 - AudioBuses.
- </li>
- <li>
- 8 - MidiBuses.
- </li>
- <li>
- 16 - VCAs.
- </li>
- <li>
- 32 - Master.
- </li>
- <li>
- 64 - Monitor.
- </li>
- <li>
- 128 - Audio Aux.
- </li>
- <li>
- 256 - Selected.
- </li>
- <li>
- 512 - Hidden.
- </li>
- </ul>
-<p class="note">
- Selected and Hidden bits are normally not needed as Ardour defaults to
- showing Selected strips and not showing Hidden strips. The purpose of
- these two flags is to allow showing only Selected strips or only
- Hidden strips. Using Hidden with other flags will allow Hidden strips
- to show inline with other strips.
-</p>
-<p>
- Some handy numbers to use might be: 15 (all tracks and buses), 31
- (add VCAs to that). Master or Monitor strips are generally not useful
- on a surface that has dedicated controls for these strips as there are
- /master* and /monitor* commands already. However, on a surface with
- just a bank of fader strips, adding master or monitor would allow
- access to them within the banks. Selected would be useful for working
- on a group or a set of user selected strips. Hidden shows strips the
- GUI has hidden.
-</p>
-<p class-"note">
- Audio Aux? say what? I am sure most people will have noticed that they
- can find no <em>Aux</em> strips in the Ardour mixer. There are none.
- There are buses that can be used a number of ways. From analog days,
- in OSC a bus is something that gets used as a sub mix before ending up
- going to Master. An auxiliary bus is used like a separate mixer and
- it's output goes outside the program or computer to be used as:
- a monitor mix, a back up recording, or what have you. In OSC where
- controller strips may be limited, it may be useful not to use up a
- strip for an aux that is not really a part of the mix. It is also
- useful to get a list of only aux buses if the control surface is a
- phone used to provide talent monitor mix control on stage. Each
- performer would be able to mix their own monitor. The user is free
- to enable both buses and auxes if they would prefer.
-</p>
-
-<h3>feedback</h3>
-<p>Feedback is an integer made up of bits. The easy way to
- deal with this is to think of feedback items being worth a number and
- then adding all those numbers together for a value to send.
+<p>If you use a newer version of JACK 1, just make sure the -X
+alsa_midi or -X seq options are enabled for whatever technique you use
+to start JACK.
</p>
- <ul>
- <li>
- 1 - Button status for strips.
- </li>
- <li>
- 2 - Variable control values for strips.
- </li>
- <li>
- 4 - Send SSID as path extension.
- </li>
- <li>
- 8 - heartbeat to surface.
- </li>
- <li>
- 16 - Enable master section feedback.
- </li>
- <li>
- 32 - Send Bar and Beat.
- </li>
- <li>
- 64 - Send timecode.
- </li>
- <li>
- 128 - Send meter as dB (-193 to +6) or 0 to 1 depending on gainmode
- </li>
- <li>
- 256 - Send meter a 16 bit value where each bit is a level
- and all bits of lower level are on. For use in a LED strip. This
- will not work if the above option is turned on.
- </li>
- <li>
- 512 - Send signal present, true if level is higher than -40dB
- </li>
- <li>
- 1024 - Send position in samples
- </li>
- <li>
- 2048 - Send position in time, hours, minutes, seconds and milliseconds
- </li>
- <li>
- 8192 - Turn on extra select channel feedback beyond what a /strip supports
- </li>
- </ul>
+
<p>
- So using a value of 19 would turn on feedback for strip and master
- controls, but leave meters, timecode and bar/beat feedback off.
+For other versions of JACK,
+add <kbd class="input">a2jmidid -e &</kbd> as an "after start-up" script
+in the <kbd class="menu">Setup > Options</kbd> tab of QJackCtl, so
+that it is started automatically whenever you start JACK.
</p>
+<p class="fixme">Is this true anymore in Ardour 5? This section may have been relevant in Ardour 3, but it might not be relevant anymore.</p>
+
---
-title: Parameter Types in OSC
+title: MIDI on OS X
part: subchapter
---
<p>
- An OSC message is laid out in this form:
+ In order for CoreMIDI to work with Jack MIDI, a CoreMIDI-to-JACK-MIDI
+ <dfn>bridge</dfn>
+ is required. This feature is available on versions equal to or great than
+ version 0.89 of JackOSX.
</p>
-<kbd>
- /path/of/command type parameter
-</kbd>
+<h2>Routing MIDI</h2>
+
+<h3>Inside Ardour</h3>
<p>
- The type is there to indicate what the parameter is. This gives
- the idea that parameter types are quite strict and if the command
- requires an Integer <em>"i"</em> then the controller had better send it.
- However, the checking of the parameter type is left to the receiving
- software.
+ MIDI ports show up in Ardour's MIDI connection matrix in multiple
+ locations. Bridged CoreMIDI ports as well as JACK MIDI ports that have
+ been created by other software clients will show up under the "Other" tab.
+ Bridged CoreMIDI hardware ports show up under the "Hardware" tab.
</p>
-<p>
- What this means in practical terms is that the surface can get away
- with sending the wrong type of parameter. There are some places
- where that just doesn't make sense. For example, a parameter that
- is specified as a Float with a range of 0 to 1, could be sent as
- an Integer, but would only have full scale and minimum value with
- nothing in between. This is not much use for a fader, though ok for
- a button.
-</p>
+<h3>External Applications</h3>
<p>
- There are a number of OSC controllers based on iOS and Android
- tablets that only send or receive parameters as floats or text.
- These controllers should have no problem sending bool or int values
- as floats. Ardour will interpret the values as required.
+ There are multiple options for connecting MIDI ports outside of Ardour.
</p>
+<ul>
+ <li><a href="http://www.snoize.com/MIDIMonitor/">MIDI Monitor</a> is a handy
+ tool for doing various MIDI-related tasks.</li>
+ <li><a href="http://notahat.com/midi_patchbay">MIDI Patchbay</a> lets you
+ connect ports and filters MIDI data.</li>
+</ul>
+
+
---
-title: Selection/Feedback Expansion Considerations in OSC
-part: subchapter
+title: Ardour's Interface
+part: part
---
-<p>
- Ardour does not send every possible feedback value for each channel.
- It does send expanded information on the selected channel. There are
- also extra commands for the selected strip. All the feedback and
- select commands have their own path <em>/select</em>.
- This means that for the selected channel the surface does not have to
- keep track of the strip ID. The /select strip will follow the
- "current mixer strip" in the GUI editor window.
-</p>
-<p>
- There are two major uses for this:
- <ol>
- <li>Single strip control surfaces. Using
- <em>/access_action Editor/select-next-route</em> or
- <em>/access_action Editor/select-prev-route</em>
- to step through the mixer strips.</li>
- <li>Using a "Super strip" section of knobs to control parts
- of the strip that are changed less often such as polarity, sends or
- plugin parameters.</li>
- </ol>
-</p>
-<p>
- Selection in Ardour's OSC implementation are complicated by the
- possibility of using more than one OSC controller at the same time.
- User "A" may select strip 4 and use a selected controller to make
- changes to that strip. User "B" may subsequently select strip 7 to
- make changes on. This leaves user "A" making changes to strip 7
- which they did not choose.
-</p>
-<p>
- For this reason Ardour offers local expansion aside from the GUI
- selection. Local expansion only affects the one OSC controller. GUI
- selection is global and affects all controllers using GUI selection
- as well as the GUI.
-</p>
+---
+title: About Ardour's Interface
+part: chapter
+---
<p>
- In general, in a one user situation where that one user may use either
- the OSC surface or the GUI, using GUI based selection makes the most
- sense. This is the default because this is the more common use.
+ In Ardour, you work in two main windows: the <dfn>Editor</dfn> and the <dfn>Mixer</dfn>.
</p>
-<p>
- When there is more than one operator, then expansion only is the
- mode of choice. It may make sense for one of the surfaces to
- use GUI selection where the operator is also using the GUI for some
- things. However, the set up should be carefully analyzed for the
- possibility of selection confusions. Expansion should be
- considered the <em>safe</em> option.
-</p>
+<figure>
+ <img src="/images/editor_split.png" alt="Ardour's mixer window">
+ <img src="/images/mixer_split.png" alt="Ardour's editor window">
+ <figcaption>
+ <ol class="multicol4">
+ <li>Main menu</li>
+ <li>Status bar</li>
+ <li>Transport bar & Times</li>
+</ol><ol class="multicol4" start="4">
+ <li>Mode switch</li>
+ <li>The <dfn>Editor</dfn> window</li>
+ <li>a track's mixer strip</li>
+</ol><ol class="multicol4" start="7">
+ <li>Editors List</li>
+ <li>The <dfn>Mixer</dfn> window</li>
+ <li>Favorite plugins</li>
+</ol><ol class="multicol4" start="10">
+ <li>Track list</li>
+ <li>Group list</li>
+ <li>Master strip</li>
+ </ol>
+ </figcaption>
+</figure>
<p>
- It is always ok to use expansion on the surface even in a one
- user scenario. This allows the user to use GUI and surface selection
- for different uses.
+ To switch between those windows, use the buttons (#4 Mode switch in the upper right), the shortcut <kbd class="mod2">M</kbd>, or the menu <kbd class="menu">Window > Editor <em>(or Mixer)</em> > Show</kbd>. Both windows can be visible at the same time (eg. for a multi-monitor setup) using <kbd class="menu">Detach</kbd> in the same menu.
</p>
-<p>
- It is also possible to use both if desired. /strip/select will ways
- set the GUI select, but /strip/expand will set the select feedback
- and commands locally without changing the GUI select. Another
- /strip/expand or a /strip/select will override that expand command
- and releasing the /strip/expand or /select/expand (setting it to 0 or
- false) will set the /select set of commands/feedback back to whichever
- strip the GUI has selected at that time. This could be used to switch
- between the GUI select and the local expand to compare two strips
- settings.
-</p>
---
-title: Using the OSC Setup Dialog
+title: Main Menu
+part: chapter
+---
+
+
+---
+title: The Session Menu
part: subchapter
---
<p>
- Starting with Ardour 5.1 OSC has a graphic setup dialog. This dialog
- can be accessed from Preferences->Control Surfaces. Select OSC and
- click on the Show Protocol Settings.
+ The <kbd class="menu">Session</kbd> menu groups together everything related to the session and the file operations.
</p>
-<p>
- The Ardour OSC dialog has three tabs. The main tab, the Strip Types
- tab and the Feedback tab.
-</p>
+<dl>
+ <dt>New...</dt><dd>Creates a <a href="/working-with-sessions/new-session-dialog/">new</a> session</dd>
+ <dt>Open...</dt><dd>Opens an existing session</dd>
+ <dt>Recent...</dt><dd>Opens a list of recent session that can be opened</dd>
+ <dt>Close</dt><dd>Closes the current session (but not Ardour)</dd>
+
+ <dt>Save</dt><dd>Saves the current session</dd>
+ <dt>Save As...</dt><dd>Saves to a new session (with options)</dd>
+ <dt>Rename...</dt><dd>Changes the name of the session</dd>
+ <dt>Snapshot (keep working on current version) ...</dt><dd>Create a <a href="/working-with-sessions/snapshots/">Snapshot</a> but any subsequent change will be saved to this session</dd>
+ <dt>Snapshot ( switch to new version) ...</dt><dd>Same thing, and any subsequent change will be saved to this new snapshot session</dd>
+ <dt>Save Template...</dt><dd>Saves the session as a <a href="/working-with-sessions/session-templates/">template</a>, without the audio</dd>
+ <dt>Metadata</dt>
+ <dt class="sub1">Edit Metadata...</dt><dd>Opens the <a href="/working-with-sessions/metadata/">Metadata</a> window, where informations about the session can be saved</dd>
+ <dt class="sub1">Import Metadata...</dt><dd>Creates the metadata by extracting them from another session</dd>
+
+ <dt>Add Track, Bus or VCA...</dt><dd>Adds a <a href="/working-with-tracks/adding-tracks-and-busses/">new track/bus/VCA</a> to the session, same as the <kbd class="menu">Track > Add Track, Bus or VCA...</kbd></dd>
+
+ <dt>Import</dt><dd>Opens the <a href="/adding-pre-existing-material/">Import</a> windows, to add media to the session</dd>
+ <dt>Import PT session</dt><dd>Import a ProTools© session file. Not everything in the original session can be imported.</dd>
+ <dt>Scripting</dt>
+ <dt class="sub1">Add Lua Script...</dt><dd>Loads or adds a <a href="/lua-scripting/">Lua Session script</a> to the current session</dd>
+ <dt class="sub1">Remove Lua Script</dt><dd>Removes a loaded Lua Session script from the session</dd>
+ <dt>Open Video...</dt><dd>Imports a <a href="/video-timeline/">video file</a> in the session</dd>
+ <dt>Remove Video</dt><dd>Removes the video part of the session (the video timeline disappears)</dd>
+ <dt>Export</dt>
+ <dt class="sub1">Export to Audio File(s)...</dt><dd><a href="/exporting/">Export</a> all or part of the session in audio form</dd>
+ <dt class="sub1">Stem export...</dt><dd><a href="/exporting/export-dialog/">Exports each track</a> as its own audio file (for e.g. DAW interchange)</dd>
+ <dt class="sub1">Export to Video File</dt><dd>Exports the session to a <a href="/video-timeline/operations/">video file</a></dd>
+ <dt>Clean-Up</dt>
+ <dt class="sub1">Bring all media into session folder</dt><dd>Copies all the media files imported from outside the session folder in that folder, see <a href="/working-with-sessions/cleaning_up/">Cleaning up Sessions</a></dd>
+ <dt class="sub1">Reset Peak Files</dt><dd>Reinitializes the buffered images representing the audio files</dd>
+ <dt class="sub1">Clean-up Unused Sources...</dt><dd>Quarantines all the media files not used in the session to a specific subfolder of the session</dd>
+ <dt class="sub1">Flush Wastebasket</dt><dd>Deletes those quarantined files</dd>
+
+ <dt>[] Properties</dt><dd>Shows the <a href="/preferences-and-session-properties/session-properties-dialog/">Session Properties</a> dialog, allowing to fine-tune the parameters of the current session</dd>
+
+ <dt>Lock</dt><dd>Locks the session by showing an Unlock window that (until cliked) blocks every action on Ardour's window</dd>
+
+ <dt>Quit</dt><dd>Exits Ardour. Prompts for saving the session if it has been modified.</dd>
+</dl>
+
+---
+title: The Transport Menu
+part: subchapter
+---
<p>
- Many OSC devices get their IP from a DHCP making it difficult to set
- an IP in Ardour's OSC settings. Therefore, most of the settings are
- <em>default</em> settings. Values are set and the next OSC surface to
- send a /set_surface* message to Ardour will use those settings. An OSC
- surface that has previously sent a message to Ardour will retain the
- settings it already had. The <em>Clear OSC Devices</em> will reset all
- device settings. A <em>/refresh</em> message will both reset the
- device settings as well as set that device to any new settings. The
- Use of <em>/set_surface</em> will override all settings except
- <em>Port Mode</em>.
+ The <dfn>Transport</dfn> menu handles how Ardour handles the playback and playhead.
</p>
-<h2>Dialog settings</h2>
+<dl>
+ <dt>Start/Stop</dt><dd>Starts or stops the playhead, and recording if it's armed</dd>
+ <dt>Play</dt>
+ <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 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>Enable Record</dt><dd>Triggers the global recording. Next time "Play" is pressed, it will record on the track(s) that are armed for recording</dd>
+
+ <dt>Set Loop from Selection</dt><dd>Converts the selection into a <a href="/working-with-markers/loop-range/">Loop range</a> by placing loop markers at the start and end of the selected range</dd>
+ <dt>Set Punch from Selection</dt><dd>Same thing, for <a href="/working-with-markers/punch-range/">Punch</a></dd>
+ <dt>Set Session Start/End from Selection</dt><dd>Same thing, for the start and end markers of the session, defining the sessions length</dd>
+
+ <dt>Forward</dt><dd>FIXME</dd>
+ <dt>Rewind</dt><dd>Plays the audio backwards from the playhead on</dd>
+ <dt>Transition to Roll</dt><dd>FIXME</dd>
+ <dt>Transition to Reverse</dt><dd>FIXME</dd>
+
+ <dt>Playhead</dt><dd></dd>
+ <dt class="sub1">Playhead to Mouse</dt><dd>Set the position of the playhead at the current position of the mouse cursor</dd>
+ <dt class="sub1">Playhead to Active Mark</dt><dd>If a marker is selected, set the position of the playhead at the position of the marker</dd>
+ <dt class="sub1">Center Playhead</dt><dd>Centers the view on the playhead without changing the zoom level (putting the playhead in the middle of the screen)</dd>
+
+ <dt class="sub1">Nudge Playhead Forward</dt><dd>Shifts the position of the playhead to the right by the amount shown in the <a href="/ardours-interface/the-editor/the-toolbar/the-nudge-controls/">nudge timer</a></dd>
+ <dt class="sub1">Nudge Playhead Backward</dt><dd>Same thing, to the left</dd>
+
+ <dt class="sub1">Move to Next Transient</dt><dd>When transient have been set, moves the playhead to the next one to the right</dd>
+ <dt class="sub1">Move to Previous Transient</dt><dd>Same, to the left</dd>
+
+ <dt class="sub1">Playhead to Next Grid</dt><dd>Regardless of the state of the Grid Mode, goes to the next grid to the right, as set by the <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">Snap/Grid unit</a></dd>
+ <dt class="sub1">Playhead to Previous Grid</dt><dd>Same, to the left</dd>
+
+ <dt class="sub1">Playhead to Next Region Boundary</dt><dd>Moves the playhead to the right to the next beginning or end of region on the selected track or, if no track is selected, on all tracks</dd>
+ <dt class="sub1">Playhead to Previous Region Boundary</dt><dd>Same, to the left</dd>
+ <dt class="sub1">Playhead to Next Region Boundary (No Track Selection)</dt><dd>Moves the playhead to next beginning or end of region, be it on the selected track or any other</dd>
+ <dt class="sub1">Playhead to Previous Region Boundary (No Track Selection)</dt><dd>Same, to the left</dd>
+ <dt class="sub1">Playhead to Next Region Sync</dt><dd>Moves the playhead to next Region Sync Point, that is by default the beginning of a region but <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">can be moved</a></dd>
+ <dt class="sub1">Playhead to Previous Region Sync</dt><dd>Same, to the left</dd>
+
+ <dt class="sub1">Jump to Next Mark</dt><dd>moves the playhead to the next <a href="/working-with-markers/creating-location-markers/">marker</a> on the Ruler</dd>
+ <dt class="sub1">Jump to Previous Mark</dt><dd>Same, to the left</dd>
+
+ <dt class="sub1">Go to Zero</dt><dd>Sends the playhead to the 00:00:00:00 time, regardless of the sessions Start marker</dd>
+ <dt class="sub1">Go to Start</dt><dd>Sends the playhead to the Start marker of the session</dd>
+ <dt class="sub1">Go to End</dt><dd>Sends the playhead to the End marker of the session</dd>
+ <dt class="sub1">Go to Wall Clock</dt><dd>Sends the playhead to the current value of system time, as shown on the top right of the <a href="/ardours-interface/status-bar/">Status bar</a></dd>
+ <dt>Active Mark</dt>
+ <dt class="sub1">To Next Region Boundary</dt><dd>Moves the currently selected <a href="/working-with-markers/">marker</a> to the next region beginning or end</dd>
+ <dt class="sub1">To Previous Region Boundary</dt><dd>Same, to the left</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">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 class="sub1">Locate to Mark <em>n</em></dt><dd>If it exists, goes to the <em>n-th</em> marker</dd>
+
+ <dt class="sub1">Set Session Start from Playhead</dt><dd>Puts the Start of the session marker at the playhead's position</dd>
+ <dt class="sub1">Set Session End from Playhead</dt><dd>Puts the End of the session marker at the playhead's position</dd>
+
+ <dt>[] Time Master</dt><dd>Sets Ardour as the Time master, i.e. Ardour sends the time information to the audio system</dd>
+ <dt>[] Punch In/Out</dt><dd>Based on the Punch in and Punch out markers if they exist, tells Ardour to record only between those two points</dd>
+ <dt>[] Punch In</dt><dd>Based on the Punch in marker, only allow to record from this point on</dd>
+ <dt>[] Punch Out</dt><dd>Based on the Punch out marker, forbids recording before this point</dd>
+ <dt>[] Audio Input</dt><dd>If checked, automatically switch the <a href="/recording/monitoring/monitor-setup-in-ardour/">monitor</a> from <em>input</em> to <em>playback</em>mode when playing</dd>
+ <dt>[] Follow Edits</dt><dd>If checked, selecting a region moves the playhead to its beginning</dd>
+ <dt>[] Auto Play</dt><dd>If checked, moving the playhead in the ruler starts the playback</dd>
+ <dt>[] Auto Return</dt><dd>If checked, when the playback is stopped, go back to the previous position of the playhead. If not, the playhead stays where it is when the playback is stopped</dd>
+ <dt>[] Click</dt><dd>Activates/desactivates the click track (metronome)</dd>
+ <dt>[] Follow Playhead</dt><dd>If checked, while playing, when the playhead reaches the right of the screen, Ardour scrolls one screen to the right to keep the playhead visible at all times</dd>
+ <dt>[] Stationary Playhead</dt><dd>If checked <em>and</em> if <kbd class="menu">Follow playhead</kbd> is checked, on playback, the playhead stays at the center of the screen, and the session scrolls</dd>
+ <dt>Panic</dt><dd>Immediately stops all MIDI playback (usefull e.g. when a MIDI bug in encountered)</dd>
+</dl>
-<h3>OSC setup tab</h3>
+---
+title: The Edit Menu
+part: subchapter
+---
<p>
-<img alt="the OSC configuration dialog"
- src="/images/osc-dialog.png">
-</p>
-
-<h4>Connection:</h4>
-
-<p>
- This field is informational only. It shows where Ardour will receive
- OSC messages. The system Name and the Port are the most important parts.
-</p>
-
-<h4>Port Mode:</h4>
-
-<p>
- This drop down allows the choice of Auto or Manual outbound port
- setting. The default Auto port mode, will send OSC messages back to
- the port messages from that surface are received from. This setting
- allows two surfaces on the same IP to operate independently. However,
- there are a number of OSC control surfaces that do not monitor the
- same port they send from and in fact may change ports they send from
- as well. Manual allows the outgoing port (the port the surface will
- receive on, to be manually set. In Manual port mode only one control
- surface per IP can work. Most phone or tablet OSC controllers like
- touchOSC or Control need Manual port mode. More than one controller
- can be used so long as each has it's own IP.
-</p>
-
-<h4>Manual Port:</h4>
-
-<p>
- This is an Entry box for setting the outgoing port when in
- Manual port mode.
-</p>
-
-<h4>Bank Size:</h4>
-
-<p>
- This sets the default bank size for the next surface to send a
- <em>/set_surface/*</em> OSC message. Bank size 0 (the default) sets
- no banking and allows controlling all strips included in strip_types
- at once.
-</p>
-
-<h4>Gain Mode:</h4>
-
-<p>
- Sets the faders (and sends faders) feedback math to position where a
- value between 0 and 1 represents the fader position of the same fader
- in the mixer GUI or dB where the feedback from fader movement will be
- returned as a dB value. When the Gain Mode is set to position, the
- /*/name feedback for the channel will show dB values in text while the
- fader is being adjusted and then return the the name text.
-</p>
-<h4>Debug:</h4>
-<p>
- For debugging purposes this allows logging either good OSC messages
- Ardour receives or invalid messages received or none.
-</p>
-<h4>Preset:</h4>
-<p>
- Ardour now allows the use of preset settings. The default settings
- used are the settings from the last session or the factory defaults
- the first time OSC is enabled. As soon as any of these settings are
- changed, the Preset will change to "User" and the new settings will be
- save to the osc directory Ardour configuration directory as
- <em>user.preset</em>. This preset file can be renamed for future use.
- It is suggested to also change the name value inside to avoid confusion
- in the preset listing. Ardour will ship with some of it's own presets
- that go with some popular OSC control and map combinations.
-</p>
-<h4>Clear OSC Devices</h4>
-<p>
- This button clears operating device profiles so that Ardour will reset
- all devices settings to use the new defaults from changed settings. a
- device may still override these new settings with the /set_surface set
- of commands. The reason for setting defaults settings is that some OSC
- controllers are not able to send more than one parameter at a time and
- so having correct defaults allows one "Connect" button rather than 4.
-</p>
-<h3>Default Strip Types tab</h3>
-<p>
-<img alt="the Default Strip Types tab"
- src="/images/osc-strip-types.png">
-</p>
-<p>
- This allows selecting which of Ardour's mixer strips will be available
- for control. The Factory default is all strips except master, monitor
- and hidden strips. If it is desired to only see input tracks the
- others can be deselected. It is also possible to change these settings
- from the control surface. A set of buttons could select showing only
- inputs or only buses. If a group is selected in the GUI then showing
- only selected strips will show only that group. Showing hidden tracks
- is handy for cases where a groups of tracks that grouped to a bus or
- controlled by a VCA are hidden, but one of those tracks needs a tweak.
-</p>
-
-<h3>Default Feedback tab</h3>
-
-<p>
-<img alt="the Default Feedback tab"
- src="/images/osc-feedbackdefault.png">
-</p>
-
-<p>
- This allows setting up which controls provide feedback. The Factory
- default is none. If the controller is unable to receive feedback, this
- should be left blank. In the case of metering, Metering as a LED strip
- only works if Metering as a Float is disabled.
-</p>
-
----
-title: Querying Ardour with OSC
-part: subchapter
----
-
-<p>
- In order to make a custom controller that knows what strips Ardour
- has, the controller needs to be able to query Ardour for that
- information. These set of commands are for smarter control surfaces
- That have the logic to figure out what to do with the information.
- These are not of value for mapped controllers like touchOSC and
- friends. The controller will need to send these queries to ardour
- as often as it needs this information. It may well make sense to use
- regular feedback for things that need to be updated often such as
- position or metering.
- Here are the commands used to query Ardour:
-</p>
-
-<dl class="bindings">
- <dt><kbd class="osc">/strip/list</kbd></dt>
- <dd>Ask for a list of strips</dd>
- <dt><kbd class="osc">/strip/sends <em>ssid</em></kbd></dt>
- <dd>Asks for a list of sends on the strip <em>ssid</em></dd>
- <dt><kbd class="osc">/strip/receives <em>ssid</em></kbd></dt>
- <dd>Asks for a list of tracks that have sends to the strip <em>ssid</em> points to</dd>
- <dt><kbd class="osc">/strip/plugin/list <em>ssid</em></kbd></dt>
- <dd>Asks for a list of plug-ins for strip <em>ssid.</em></dd>
- <dt><kbd class="osc">/plugin/descriptor <em>ssid</em> <em>piid</em></kbd></dt>
- <dd>Asks for a list of descriptors for plug-in <em>piid</em> on strip <em>ssid</em></dd>
-</dl>
-
-<h3>A list of strips</h3>
-
-<p>
- <code>/strip/list</code> asks Ardour for a list of strips that the
- current session has. Ardour replies with a message for each
- strip with the following information:
- <ul>
- <li>Strip type</li>
- <li>Strip name</li>
- <li>Number of inputs</li>
- <li>Number of outputs</li>
- <li>Muted (bool)</li>
- <li>Soloed (bool)</li>
- <li>Ssid (strip number)</li>
- <li>Record enabled (bool)</li>
- </ul>
- After all the strip messages have been sent, one final message is
- sent with:
- <ul>
- <li>The text <code>end_route_list</code></li>
- <li>The session frame rate</li>
- <li>The last frame number of the session</li>
- </ul>
-</p>
-<p class="note">A bus will not have a record enable and so a bus message
- will have one less parameter than a track. It is the controllers
- responsability to deal with this.
-</p>
-
-<h3>A list of sends</h3>
-<p>
- <code>/strip/sends <em>ssid</em></code> asks Ardour for a list of
- sends for strip number ssid. The reply is sent back to the
- controller as one message with the following information:
- <ul>
- <li>Ssid that information is for</li>
- <li>Each send's information:</li>
- <ul>
- <li>The send's target bus ssid</li>
- <li>The send's target bus name</li>
- <li>The send id for this strip</li>
- <li>The send gain as a fader possition</li>
- <li>The Send's enable state</li>
- </ul>
- </ul>
-</p>
-<p>
- The controller can tell how many sends there are from the number of
- parameters as each send has 5 parameters and there is one extra for
- ssid.
-</p>
-
-<h3>A list if tracks that send audio to a bus</h3>
-<p>
- <code>/strip/receives <em>ssid</em></code> will return a list of
- tracks that have sends to the bus at the ssid. The reply will
- contain the following information for each track conntected to this
- bus:
- <ul>
- <li>The ssid of the track sending</li>
- <li>The name of the sending track</li>
- <li>The id of the send at that track</li>
- <li>It's gain in fader possition</li>
- <li>The send's enable state</li>
- </ul>
-</p>
-
-<h3>A list of plug-ins for strip</h3>
-<p>
- <code>/strip/plugin/list <em>ssid</em></code> will return a list of
- plug-ins that strip ssid has. The reply will contain the following
- information:
- <ul>
- <li>Ssid that information is for</li>
- <li>Each plugin's information:</li>
- <ul>
- <li>The plug-in's id</li>
- <li>The plug-in's name</li>
- </ul>
- </ul>
-</p>
-
-<h3>A list of a plug-in's parameters</h3>
-<p>
- <code>/plugin/descriptor <em>ssid</em> <em>piid</em></code> will
- return the plug-in parameters for ppid plug-in on the ssid strip. The
- reply will contain the following information:
- <ul>
- <li>Ssid of the strip the plug-in is in</li>
- <li>The plug-in id for the plug-in</li>
- <li>The plug-in's name</li>
- <li>Information about each parameter</li>
- <ul>
- <li>The parameter id</li>
- <li>The parameter's name</li>
- <li>A bitset of flags (see below)</li>
- <li>Data type</li>
- <li>Minimum value</li>
- <li>Maximum value</li>
- <li>The number of scale points</li>
- <li>zero or more scale points of one value and one string each</li>
- <li>The current parameter value</li>
- </ul>
- </ul>
-</p>
-
-<p>
- The flag bitset above has been defined as (from lsb):
- <ul>
- <li>0 - enumeration</li>
- <li>1 - integer step</li>
- <li>2 - logarithmic</li>
- <li>3 - max unbound</li>
- <li>4 - min unbound</li>
- <li>5 - sample rate dependent</li>
- <li>6 - toggled</li>
- <li>7 - controllable</li>
- </ul>
-</p>
-
-<p>
- While this seems complex, it is really not that bad. Minimum, maximum and value will in most cases give you all you need.
-</p>
-
----
-title: Devices using Mackie/Logic Control Protocol
-menu_title: Mackie/Logic Control Devices
-part: subchapter
----
-
-<p>
- This will walk you through the process of configuring and using
- a MIDI control surface with Ardour that uses the <dfn>Mackie Control
- protocol</dfn> (MCP) or <dfn>Logic Control protocol</dfn>. Devices that
- have been tested and are known to work include the SSL Nucleus, Mackie
- Control Pro (plus extenders), Behringer devices in Mackie/Logic mode,
- and Steinberg CMC devices.
-</p>
-
-<h2>Enabling Mackie Control in Ardour</h2>
-
-<p>
- Navigate to <kbd class="menu">Edit > Preferences > Control Surfaces</kbd>.
- Double-click on <kbd class="menu">Mackie Control</kbd> to see the setup dialog:
-</p>
-
-<img src="/images/missing.png" alt="Mackie Control Setup Dialog" />
-
-<p>
- From the selector at the top, choose the type of device you are using.
- (<a
- href="/using-control-surfaces/devices-using-mackielogic-control-protocol/devices-not-listed/">
- What to do if your device is not listed</a>).
-</p>
-
-<p>
- Once your setup is complete, click "OK" to close the dialog. Now click
- on the enable checkbox for "Mackie Control".
-</p>
-
-<h2>Connecting control surface and Ardour MIDI ports</h2>
-
-<p>
- If you are using a device that uses ipMIDI, such as the SSL Nucleus, no
- MIDI port connections are required—Ardour and your control
- surface will be able to talk to each other automatically.
-</p>
-
-<p>
- If you are using a device that uses normal MIDI (via a standard MIDI or
- USB cable), you need to connect Ardour's Mackie Control in and out ports
- to the MIDI ports leading to and coming from the control surface.
-</p>
-
-<p>
- When you have made these connections once, Ardour will recreate them
- for you in the future, as long as you leave Mackie Control enabled.
-</p>
-
-<h2>Customizing your control surface</h2>
-
-<p>
- Every possible Mackie Control button can be bound to any action present
- in Ardour's GUI. Please check your control surface page for suggestions.
-</p>
-
-<h2>Preparing your device for use with Ardour</h2>
-
-<p>
- Most interfaces will require some configuration to send and respond to
- MCP.
-</p>
-
-<p class="note">
- When setting up the control surface, do <em>not</em> use "Pro Tools"
- mode. Pro Tools is the only DAW that still requires HUI. The rest of
- world uses Mackie Control Protocol. Ardour does not support HUI.
-</p>
-
----
-title: Behringer devices in Mackie/Logic Control Mode
-menu_title: Behringer devices
-part: subchapter
----
-
-<h2>Behringer BCF-2000 Faders Controller</h2>
-
-<p>
- <img alt="Digramatic Image of the BCF2000"
- src="/images/BCF2000.png">
-</p>
-
-<p>
- The Behringer BCF-2000 Fader Controller is a control surface with 8 motorized
- faders, 8 rotary encoders and 30 push buttons. The device is a class
- compliant USB Midi Interface and also has standard Midi DIN IN/OUT/THRU ports.
- The device has included a Mackie/Logic Control Emulation Mode since firmware v1.06.
- If you're devices firmware is older than v1.06 it will require an update before
- Mackie Control Emulation will work as described here.
-</p>
-
-<p>
- <img alt="Digramatic Image of the BCF2000 in Edit Global Mode"
- src="/images/BCF2000-EG.png">
-</p>
-
-<p>
- In order to put the controller into Mackie/Logic control mode turn on the
- unit while holding third button from the left in the top most row
- of buttons (under the rotary encoder row). Hold the button down until <dfn>EG</dfn>
- or edit global mode is displayed on the LCD screen of the unit. The global parameters
- can then be edited using the 8 rotary encoders in the top row.
-</p>
- <ul>
- <li><code>
- Encoder #1 sets the operating mode and should be set to <dfn>U-1</dfn> or
- USB mode 1 if using with a USB cable connection.
- </li></code>
- <li><code>
- Encoder #3 sets the foot switch mode and should most likely be set to
- <dfn>Auto</dfn> to detect how the foot switch is wired.
- </li></code>
- <li><code>
- Encoder #5 sets the device id, if you are using only 1 device the id
- should be set to <dfn>ID 1</dfn>. If you are using multiple BCF/BCR2000 each
- device is required to be set up sequentially and one at a time.
- </li></code>
- <li><code>
- Encoder #7 controls the MIDI <dfn>Dead Time</dfn> or the amount of milliseconds
- after a move has been made that the device ignores further changes, this
- should be set to <dfn>100</dfn>.
- </li></code>
- <li><code>
- Encoder #8 controls the MIDI message <dfn>Send Interval</dfn> in milliseconds
- and should be set to <dfn>10</dfn>
- </li></code>
- </ul>
-<p>
- To exit the <dfn>EG</dfn> mode press the <dfn>Exit</dfn> button. The device is now
- ready to use with Ardour.
-</p>
-
-<h3>Modes of Operation</h3>
-<p>
- <img alt="Digramatic Image of the BCF2000 Control Modes"
- src="/images/BCF2000-Modes.png">
-</p>
-<p>
- The four buttons arranged in a rectangle and located under the Behringer logo
- are the mode selection buttons in Logic Control Emulation Mode,
- currently Ardour has implemented support for two of these modes.
-</p>
-<p>
-The surface can be broken into 8 groups of controls.
-</p>
-
-<ol>
- <li>The rotary encoders at the top of the device</li>
- <li>The first row of buttons under the encoders</li>
- <li>The second row of buttons under the encoders</li>
- <li>The row of motorized faders<li>
- <li>
- The group of 4 buttons at the top right that will be
- referred to here as the <dfn>Shift Group</dfn>
- </li>
- <li>
- The group of 4 buttons under the <dfn>Shift Group</dfn>
- referred to here as the <dfn>Mode Group</dfn>
- </li>
- <li>
- The group of 2 buttons under the <dfn>Mode Group</dfn>
- referred to here as the <dfn>Select Group</dfn>
- </li>
- <li>
- The group of 4 buttons under the <dfn>Select Group</dfn>
- referred to here as the <dfn>Transport Group</dfn>
- </li>
-</ol>
-
-<h3>Mixer Pan Mode</h3>
-<p>
- <img alt="Digramatic Image of the BCF2000 Control Modes"
- src="/images/BCF2000-Pan.png">
-</p>
-<p>
- This is the standard work mode that organizes the control surface to emulate
- a standard mixer layout where controls for each track/bus are arranged vertically.
- The order of the faders is either controlled by the order of the tracks in the
- mixer or can be set manually by the user.
-</p>
-<dl>
- <dt>Encoders</dt>
- <dd>Mixer Pans. The red LEDs show the amount of pan left or right</dd>
- <dt>First Row of Buttons</dt>
- <dd>Mixer Mutes. The button led lights if the track is currently muted</dd>
- <dt>Second Row of Buttons</dt>
- <dd>Select Active Track/Bus. Currently selected track/bus is indicated by the button led</dd>
- <dt>Faders</dt>
- <dd>Mixer Gains</dd>
- <dt>Shift Group</dt>
- <dd>
- The top and bottom left buttons are the simply shifts to change the function of other buttons
- </dd>
- <dd>
- The top right is the <dfn>Fine Control</dfn> button that allows the increment values sent by
- by rotary encoders and faders to be a small value for more precise editing. This button
- can also act as a shift button.
- </dd>
- <dd>
- The bottom right is the <dfn>Global Shift</dfn> button that allows you to change back to the
- standard Mixer Pan view from other views and modes. This button can also act as a shift button.
- </dd>
- <dt>Mode Group</dt>
- <dd>The top two buttons functions are not currently implemented in Ardour.</dd>
- <dd>The bottom left button sets the device to <dfn>Pan</dfn> mode and should currently be lit</dd>
- <dd>
- The bottom right button sets the device to <dfn>Send</dfn> mode but will only allow the switch
- if the currently selected track/bus has a send or sends to control.
- </dd>
- <dt>Select Group</dt>
- <dd>
- In this mode they function as bank select left and right. If your session has more than 8 tracks
- the next set of 8 tracks is selected with the right button and the faders will move to match the
- current gain settings of that bank of 8 tracks/busses. If the last bank contains less than 8
- tracks/busses the unused faders will move to the bottom and the pan lights will all turn
- off. An unlimited amount of tracks can be controlled with the device.
- </dd>
- <dt>Transport Group</dt>
- <dd>The upper left button controls <dfn>Rewind<dfn>.
- <dd>The upper right button controls <dfn>Fast Foreword</dfn>
- <dd>The lower left button controls stop</dd>
- <dd>The lower right button controls play</dd>
-</dl>
-<h3>Send Mode</h3>
-<p>
- <img alt="Digramatic Image of the Send Mode"
- src="/images/BCF2000-Send.png">
-</p>
-<p>
- Send mode allows for the top row of encoders to control the sends for a selected channel.
- One interesting option is to flip the controls from the encoders to the faders by pressing
- the shift 1 button and the global view button at the same time.
-</p>
-<dl>
- <dt>Encoders</dt>
- <dd>
- In send mode, the encoders control sends from left to right instead of mixer pans.
- If there are less than 8 sends the behavior of the encoder will be to continue controlling
- the mixer pan. Visually it's indicated by the change in the LED from originating at the 12
- o'clock position to originating at the 7 o'clock position. If <dfn>FLIP</dfn> is pressed
- the encoder will control the mixer gain for the selected track/bus.
- </dd>
- <dt>First row of buttons</dt>
- <dd>No Change</dd>
- <dt>Second row of buttons</dt>
- <dd>No Change.</dd>
- <dt>Faders</dt>
- <dd>
- No change unless <dfn>FLIP</dfn>is pressed then it controls the send for the selected track/bus.
- </dd>
- <dt>Shift Group</dt>
- <dd>No Change</dd>
- <dt>Select Group</dt>
- <dd>No Change</dd>
- <dt>Transport Group</dt>
- <dd>No Change</dd>
-</dl>
-<h3>Mixer Pan While Holding Shift 1</h3>
-<p>
- <img alt="Digramatic Image of the Mixer Mode while holding down shift 1"
- src="/images/BCF2000-Shift1.png">
-</p>
-<p>
- The operations of various buttons change while holding down the <dfn>Shift 1</dfn> button
-</p>
-<dl>
- <dt>Encoders</dt>
- <dd>No Change</dd>
- <dt>First row of buttons</dt>
- <dd>These now control the Soloing of each track/bus in the current bank</dd>
- <dt>Second row of buttons</dt>
- <dd>These now control the Enable Record for each track</dd>
- <dt>Faders</dt>
- <dd>No Change</dd>
- <dt>Shift Group</dt>
- <dd>No change</dd>
- <dt>Mode Group</dt>
- <dd>No Change</dd>
- <dt>Select Group</dt>
- <dd>
- These now change the current bank of tracks being controlled over by
- one. So if you where controlling tracks 1-8 a push the right
- button the surface would now control tracks 2-9 pressing the left
- would then shift back to controlling tracks 1-8.
- </dd>
- <dt>Transport Group</dt>
- <dd>The upper left now controls turning on and off <dfn>Loop</dfn> mode.</dd>
- <dd>
- The upper right now toggles
- <dfn>Click</dfn>.
- </dd>
- <dd>The lower left toggles <dfn>Replace</dfn>.</dd>
- <dd>
- The lower right toggles
- <dfn>Global Record</dfn>.
- </dd>
-</dl>
-<h3>Mixer Pan While Holding Shift 2</h3>
-<p>
- <img alt="Digramatic Image of the Mixer Mode while holding down shift 2"
- src="/images/BCF2000-Shift2.png">
-</p>
-<p>
- The operations of various buttons change while holding down the <dfn>Shift 2</dfn> button
-</p>
-<dl>
- <dt>Encoders</dt>
- <dd>No Change</dd>
- <dt>First row of buttons</dt>
- <dd>FIX ME</dd>
- <dt>Second row of buttons</dt>
- <dd>These now control setting up different <dfn>Views</dfn>. See bellow for more info</dd>
- <dt>Faders</dt>
- <dd>No Change</dd>
- <dt>Shift Group</dt>
- <dd>No change</dd>
- <dt>Mode Group</dt>
- <dd>No Change</dd>
- <dt>Select Group</dt>
- <dd>Left button controls <dfn>Undo</dfn>(NEEDS VERIFIED)</dd>
- <dt>Transport Group</dt>
- <dd>FIX ME</dd>
- <dd>FIX ME</dd>
- <dd>FIX ME</dd>
- <dd>FIX ME</dd>
-</dl>
-
-<h3>Views</h3>
-
-<p>
- <img alt="Digramatic Image of the LED display for different Views"
- src="/images/BCF2000-Views.png">
-</p>
-
-<p class="fixme">FIX ME</p>
-
----
-title: SSL Nucleus
-part: subchapter
----
-
-<p>
- The Nucleus, from Solid State Logic, is a 16 fader Mackie Control
- device that includes many buttons, separate meters, two LCD displays
- and other features. The device is not cheap (around US$5000 at the
- time of writing), and has some <a href="#design">design features</a>
- (or lack thereof) which some Ardour developers find
- questionable. Nevertheless, it is a very flexible device, and makes
- a nice 16 fader surface without the need to somehow attach an
- extender to your main surface.
-</p>
-
-<h2>Pre-configuring the Nucleus</h2>
-
-<p>
- Your Nucleus comes complete with a number of "profiles" for a few
- well-known DAWs. At the time of writing it does not include one for
- Ardour (or related products such as Harrison Mixbus).
-</p>
-<p>
- We have prepared a profile in which as many buttons as possible send
- Mackie Control messages, which makes the device maximally useful
- with Ardour (and Mixbus). You can
- download <a href="https://community.ardour.org/files/ArdourNucleusProfile.zip">the
- profile</a>
- and load it to your Nucleus using the <code>Edit Profiles</code>
- button in SSL's Nucleus Remote application. Be sure to select it for
- the active DAW layer in order to make Ardour work as well as
- possible. <em>Note: unfortunately, the Nucleus Remote application
- only runs on OS X or Windows, so Linux users will need access to
- another system to load the profile. We will provide notes on the
- profile settings at a future time.</em>
-</p>
-
-<h2>Connecting the Nucleus</h2>
-
-<p>
- Unlike most Mackie Control devices, the Nucleus uses an ethernet
- connection to send and receive the MIDI messages that make up the
- Mackie Control protocol. Specifically, it uses a technology called
- "ipMIDI" which essentially "broadcasts" MIDI messages on a local
- area network, so that any connected devices (computers, control
- surfaces, tablets etc.) can participate.
-</p>
-<p>
- All other DAWs so far that support the Nucleus have chosen to do so
- by using a 3rd party MIDI driver called "ipMIDI", which creates a
- number of "virtual" MIDI ports on your computer. You, the user,
- tells the DAW which ports to connect to, and ipMIDI takes care of
- the rest.
-</p>
-<p>
- Ardour has builtin ipMIDI support, with no need of any 3rd party
- packages, and no need to identify the "ports" to connect to in order
- to communicate with the Nucleus. This makes setting it up a bit
- easier than most other systems.
-</p>
-<p>
- Unless ... you already installed the ipMIDI driver in order to use
- some other DAW with your Nucleus. If ipMIDI is configured to create
- any "ports", it is not possible for Ardour's own ipMIDI support to
- function. We decided to offer both methods of communicating with
- your Nucleus. If you regularly use other DAWs, and appreciate having
- ipMIDI permanently set up to communication with the Nucleus—that's
- OK, you can tell Ardour to use the ipMIDI driver you already
- have. But if you're not using other DAWs with the Nucleus (and thus
- have not installed the ipMIDI driver), then you can ignore the
- ipMIDI driver entirely, and let Ardour connect directly with no
- configuration.
-</p>
-
-<h3>Connecting via Ardour's own ipMIDI support</h3>
-
-<p class="alert alert-info">
- This is usable only on computers with no 3rd party ipMIDI
- driver software installed and configured. If you have the OS X or
- Windows ipMIDI driver from nerds.de, it <strong>MUST</strong> be
- configured to offer <strong>ZERO</strong> ports before using this
- method.
-</p>
-
-<p>
- Open <code>Preferences > Control Surfaces</code>. Ensure that the
- Mackie protocol is enabled, then double-click on it to open the
- Mackie Control setup dialog.
-</p>
-<p>
- Ensure that the device selected is "SSL Nucleus". The dialog should
- show a single numerical selector control below it, defining the
- ipMIDI port number to use (it should almost always be left at the
- default value of 21928).
-</p>
-<p>
- Communication is automatically established with the Nucleus and you
- need do nothing more.
-</p>
-<p>
- If this does not work, then make sure your network cables are
- properly connected, and that you are <strong>not</strong> running
- other ipMIDI software on the computer.
-</p>
-
-<h3>Connecting via 3rd party ipMIDI support</h3>
-
-<p class="alert alert-info">
- This is usable only on computers with 3rd party ipMIDI
- driver software installed and configured for (at least) 2 ports.
-</p>
-
-<p>
- Open <code>Preferences > Control Surfaces</code>. Ensure that the
- Mackie protocol is enabled, then double-click on it to open the
- Mackie Control setup dialog.
-</p>
-<p>
- Ensure that the device selected is "SSL Nucleus (via platform MIDI)". The dialog should
- show four combo/dropdown selectors, labelled (respectively):
-</p>
- <ul>
- <li><code>Main Surface receives via</code></li>
- <li><code>Main Surface sends via</code></li>
- <li><code>1st extender receives via</code></li>
- <li><code>1st extender sends via</code></li>
- </ul>
-<p>
- You should choose "ipMIDI port 1", "ipMIDI port 1", "ipMIDI port 2"
- and "ipMIDI port 2" for each of the 4 combo/dropdown selectors.
-</p>
-<p>
- Communication should be automatically established with the Nucleus.
-</p>
-<p>
- If this does not work, then make sure your network cables are
- properly connected, and that you are running the approprate ipMIDI
- driver and have configured it for 2 (or more) ports.
-</p>
-
-<h2><a name="design">Nucleus Design Discussion</a></h2>
-
-<p>
- You might be reading this part of the manual seeking some guidance
- on whether the Nucleus would make a suitable control surface for
- your workflows. We don't want to try to answer that question
- definitively, since the real answer depends on the very specific
- details of your workflow and situation, but we would like to point
- out a number of design features of the Nucleus that might change
- your opinion.
-</p>
-
-<h3>Cons</h3>
-<dl>
- <dt>No Master Faster</dt>
- <dd>It is not possible to control the level of the Master bus or
- Monitor section. Really don't know what SSL was thinking here.</dd>
- <dt>No dedicated rec-enable buttons</dt>
- <dd>You have to press the "Rec" button and convert the per-strip
- "Select" buttons into rec-enables</dd>
- <dt>No dedicated automation buttons</dt>
- <dd>You have to press the "Auto" button and convert the first 4
- vpots into 4 automation-related buttons, losing your current view
- of the session.</dd>
- <dt>No buttons with Mackie-defined "Marker" functionality</dt>
- <dd>Mackie's design intentions for the interoperation of the
- Marker, rewind and ffwd buttons requires profile editing in order
- to function properly.
- </dd>
- <dt>No "Dyn" button</dt>
- <dd>This is hard to assign in an edited profile. To be fair, other
- Mackie Control devices also lack this button.
- </dd>
-</dl>
-
-<h3>Pros</h3>
-<dl>
- <dt>Single cable connectivity</dt>
- <dd>No need for multiple MIDI cables to get 16 faders</dd>
- <dt>Broadcast connectivity</dt>
- <dd>Connecting to multiple computers does not require recabling</dd>
- <dt>16 faders from a single box</dt>
- <dd>No need to figure out how to keep extenders together</dd>
- <dt>Meters separated from displays</dt>
- <dd>Contrast with the Mackie Control Universal Pro, where meters
- interfere with the display
- </dd>
- <dt>DAW profiles</dt>
- <dd>Easy to flip profiles for use by different DAWs.</dd>
-</dl>
-
-
-<h3>Ambiguous</h3>
-<dl>
- <dt>Ability to make buttons generate USB keyboard events</dt>
- <dd>The extent to which this is useful reflects the target DAWs
- inability to manage all of its functionality via Mackie Control
- </dd>
- <dt>Sophisticated "profile" editing</dt>
- <dd>It is nice to be able to reassign the functionality of most
- buttons, but this is only necessary because of the relatively few
- global buttons on the surface.
- </dd>
- <dt>Builtin analog signal path</dt>
- <dd>SSL clearly expects users to route audio back from their
- computer via the Nucleus' own 2 channel output path, and maybe even
- use the input path as well. They take up a significant amount of
- surface space with the controls for this signal path, space that
- could have been used for a master fader or more Mackie Control
- buttons. The USB audio device requires a proprietary driver, so
- Linux users can't use this, and OS X/Windows users will have to
- install a device driver (very odd for a USB audio device these
- days). The analog path also no doubt adds notable cost to the
- Nucleus. There's nothing wrong with this feature for users that
- don't already have a working analog/digital signal path for their
- computers. But who is going to spend $5000 on a Nucleus that
- doesn't have this already?</dd>
-</dl>
-
----
-title: Mackie Control Setup on Linux
-part: subchapter
----
-
-<h2>Devices using ipMIDI</h2>
-
-<p>
- If you are using a device like the SSL Nucleus that uses ipMIDI,
- no set up is required other than to ensure that your control surface
- and computer are both connected to the same network.
-</p>
-
-<h2>Devices using conventional MIDI</h2>
-
-<p>
- Before attempting to use a Mackie Control device that communicates via
- a standard MIDI cable or a USB cable, you should ensure that
- <a href="/setting-up-your-system/setting-up-midi/midi-on-linux">your Linux
- MIDI environment is setup</a>.
-</p>
-
----
-title: What to do if your Device is not Listed
-menu_title: Unlisted devices
-part: subchapter
----
-
-<p>
- All Mackie Control devices are based on the original Logic Control and the
- documentation in the user manual that came with it. The Mackie Control and
- the Mackie Control Pro and so on, all use this same protocol. Any units
- from other manufactures will also use the same encoding as best the
- hardware will allow. If the unit in use has more than one Mackie Control
- option, it is best to choose Logic Control or LC. Any Templates for the
- buttons should be chosen the same way as the Function key Editor uses these
- button names. The "Mackie Control" option should be considered default and
- should be tried with any unlisted device before attemping to create a
- custom definition file.
-</p>
-
----
-title: Working With Extenders
-menu_title: Working With Extenders
-part: subchapter
----
-
-<p>
- Extenders will require a custom file as there are no combinations listed
- at this time. The best way is to start with the mc.device file and copy it
- to a new name such as xt+mc.device and then edit that file. It is best to
- name the file with the order the devices are expected to be used in as
- the position of the master device is specified in this file.
-</p>
-
-<p>
- The two lines of interest are:
-<p>
-
-<pre>
- <Extenders value="0"/>
- <MasterPosition value="0"/>
-</pre>
-
-<p>
- Add these two lines if they are not present. The <code>Extenders</code>
- value is the number of extenders used and should not include the master in
- that number.
-</p>
-
-<p>
- When an <code>Extenders</code> value of greater than 0 is used, extra midi
- ports will appear for the extenders to be connected to. The MIDI ports
- for the controllers will be named <code>mackie control #1</code>,
- <code>mackie control #2</code> and up. The numbers will go from left to
- right. That is, from lowest number channel to highest.
-</p>
-
-<p>
- The <code>MasterPosition</code> value is the port number the master unit
- (with the master fader) is connected to. So if there are three surfaces,
- <code><MasterPosition value="1"/></code> will expect the master on
- the left, <code><MasterPosition value="2"/></code> would be master
- in the middle and <code><MasterPosition value="3"/></code> would be
- master on the right. So the position matches the port name.
-</p>
-
-<p class="note">
- The default value of <code><MasterPosition value="0"/></code> has
- the same effect as <code><MasterPosition value="1"/></code>.
-</p>
-
-<p>
- If the <code>MasterPosition</code> value does not properly match the
- physcal position and MIDI port, the master fader and global controls will
- not work. The master unit will act like an extender.
-</p>
-
----
-title: MIDI Binding Maps
-part: subchapter
----
-
-<p>
- Ardour 2.X supported
- <a href="/using-control-surfaces/midi-learn"><dfn>MIDI learning</dfn></a>
- for more or less any control. This was a nice feature that quite a few other
- DAWs are providing by now, but it didn't allow Ardour to work "out of the
- box" with sensible defaults for existing commercial MIDI
- controllers. In Ardour 3 and later versions, we have augmented the
- MIDI learn feature with the ability to load a <dfn>MIDI binding map</dfn>
- for a given controller, which can set up an arbitrary number of physical
- controls with anything inside Ardour that can be controlled.
-</p>
-
-<p>
- Currently (August 2016), we have presets for the following devices/modes:
-</p>
-
-<ul>
- <li>AKAI MPD-32</li>
- <li>AKAI MPK61</li>
- <li>AKAI MPKmini</li>
- <li>Behringer BCF2000</li>
- <li>Behringer BCF2000 (Mackie Emulation mode; better to use
- Ardour's actual Mackie Control Protocol support)</li>
- <li>Behringer DDX3216</li>
- <li>Korg nanoKONTROL (2 layouts)</li>
- <li>Korg nanoKONTROL 2 (2 layouts)</li>
- <li>Korg Taktile</li>
- <li>M-Audio Axiom 25 (2 layouts)</li>
- <li>M-Audio Axiom 61</li>
- <li>M-Audio Oxygen 49</li>
- <li>M-Audio Oxygen 61v3</li>
- <li>M-Audio Oxygen 25</li>
- <li>M-Audio Oxygen 8v2</li>
- <li>Novation Impulse 49</li>
- <li>Novation Impulse 61</li>
- <li>Novation LaunchControl XL</li>
- <li>Novation LaunchKey 25</li>
- <li>Roland SI-24</li>
- <li>Roland V Studio 20</li>
- <li>Yamaha KX25</li>
-</ul>
- At this time, new binding maps need to be created with a text editor.
-<p>
- MIDI binding maps are accessible by double-clicking <kbd class="menu">Edit
- > Preferences > Control Surfaces > Generic MIDI</kbd>. Ardour will
- retain your selection after you choose one.
-</p>
-
-<h2>Creating new MIDI maps</h2>
-<h3>The Basic Concept</h3>
-<p>
- Since the beginning of time (well, sometime early in the 2.X series),
- Ardour has had the concept of identifying each track and bus with a
- <dfn>remote control ID</dfn>. This ID uniquely identifies a track or bus
- so that when messages arrive from elsewhere via MIDI or OSC , we can determine
- which track or bus they are intended to control. Ardour has a
- <a
- href="/working-with-tracks/controlling-track-ordering/track-ordering-and-remote-control-ids/">number
- of ways of assigning remote control IDs</a>, but they don't really matter
- very much when creating MIDI binding maps, so we won't discuss that here.
- You just need to know that there is a "first track" and its remote control
- ID is 1, and so on.
-</p>
-<h3>Getting Started</h3>
-<p>
- MIDI bindings are stored in files with the suffix ".map" attached to their
- name. The minimal content looks like this:
-</p>
-<pre>
-<?xml version="1.0" encoding="UTF-8"?>
-<ArdourMIDIBindings version="1.0.0" name="The name of this set of
-bindings">
-</ArdourMIDIBindings>
-</pre>
-<p>
- So, to start, create a file with that as the initial contents.
-</p>
-<p>
- On OS X, Ardour loads midi maps from its binary-bundle folder in
- <code>Ardour-<version>/midi_maps/</code> and checks
- various other locations as well (defined by the ARDOUR_MIDIMAPS_PATH
- environment variable). On GNU/Linux the easiest is to save the file to
- <code>~/.config/ardour3/midi_maps/</code>.
-</p>
-
-<h3>Finding out what your MIDI control surface sends</h3>
-<p>
- This is the most complex part of the job, but its still not very hard.
- You need to connect the control surface to an application that will show
- you the information that the device sends each time you modify a knob,
- slider, button etc. There are a variety of such applications (notably
- <code>gmidimon</code> and <code>kmidimon</code>, but you can actually use
- Ardour for this if you want. Start Ardour in a terminal window, connect
- MIDI ports up, and in the Preferences window, enable "Trace Input" on the
- relevant MIDI port. A full trace of the MIDI data received will show up in
- the terminal window. (Note: in Ardour3, you get a dedicated, custom dialog
- for this kind of tracing.)
-</p>
-<h3>Types of Bindings</h3>
-<p>
- There are two basic kinds of bindings you can make between a MIDI message
- and something inside Ardour. The first is a binding to a specific parameter
- of a track or bus. The second is a binding to a function that will change
- Ardour's state in some way.
-</p>
-<h4>Binding to Track/Bus controls</h4>
-<p>
- A track/bus binding has one of two basic structures
-</p>
-<code>
- <Binding <em>msg specification</em> uri="<em>... control address ...</em>"/>
- <Binding <em>msg specification</em> function="<em>... function name ...</em>"/>
-</code>
-
-<h4>Message specifications</h4>
-<p>
- You can create a binding for either 3 types of channel messages, or for a
- system exclusive ("sysex") message. A channel message specification looks
- like this:
-</p>
-<code>
- <Binding channel="1" ctl="13" ....
-</code>
-<p>
- This defines a binding for a MIDI Continuous Controller message involving
- controller 13, arriving on channel 1. There are 16 MIDI channels, numbered
- 1 to 16. Where the example above says <code>ctl</code>, you can alternatively
- use <code>note</code> (to create binding for a Note On message) or
- <code>pgm</code> (to create a binding for a Program Change message).
-</p>
-<p>
- As of Ardour 4.2, <code>enc-r</code>, <code>enc-l</code>, <code>enc-2</code> and
- <code>enc-b</code> may be used for surfaces that have encoders that send
- offsets rather than values. These accept Continuous Controller messages
- but treat them as offsets. These are good for banked controls as they are
- always at the right spot to start adjusting. (
- <a href="/using-control-surfaces/midi-binding-maps/working-with-encoders/">
- Learn more about working with encoders
- </a>)
-</p>
-<p>
- You can also bind sysex messages:
-</p>
-<code>
- <Binding sysex="f0 0 0 e 9 0 5b f7" ....
- <Binding sysex="f0 7f 0 6 7 f7" ....
-</code>
-<p>
- The string after the <code>sysex=</code> part is the sequence of MIDI bytes,
- as hexadecimal values, that make up the sysex message.
-</p>
-<p>
- Finally, you can bind a totally arbitrary MIDI message:</p>
-<code>
- <Binding msg="f0 0 0 e 9 0 5b f7" ....
- <Binding msg="80 60 40" ....
-</code>
-<p>
- The string after the <code>msg=</code> part is the sequence of MIDI bytes, as
- hexadecimal values, that make up the message you want to bind. Using this is
- slightly less efficient than the other variants shown above, but is useful for
- some oddly designed control devices.
-</p>
-
-<p class="note">
- As of Ardour 4.6 it is possible to use multi-event MIDI strings such as
- two event CC messages, RPN or NRPN.
-</p>
-
-<p class="note">
- The <code>sysex=</code> and <code>msg=</code> bindings will only work with
- <code>function=</code> or <code>action=</code> control addresses. They
- will <em>not</em> work with the <code>uri=</code> control addresses.
- Controls used with <code>uri=</code> require a <em>Value</em> which is
- only available in a known place with channel mode MIDI events.
-</p>
-
-<h4>Control address</h4>
-<p>
- A <dfn>control address</dfn> defines what the binding will actually control.
- There are quite a few different things that can be specified here:
-</p>
-<dl class="wide-table">
-<dt>/route/gain</dt>
-<dd>the gain control ("fader") for the track/bus</dd>
-<dt>/route/trim</dt>
-<dd>the trim control for the track/bus (new in 4.1)</dd>
-<dt>/route/solo</dt>
-<dd>a toggleable control for solo (and listen) of the track/bus</dd>
-<dt>/route/mute</dt>
-<dd>a toggleable control to mute/unmute the track/bus</dd>
-<dt>/route/recenable</dt>
-<dd>a toggleable control to record-enable the track</dd>
-<dt>/route/panwidth</dt>
-<dd>interpreted by the track/bus panner, should control image "width"</dd>
-<dt>/route/pandirection</dt>
-<dd>interpreted by the track/bus panner, should control image "direction"</dd>
-<dt>/route/plugin/parameter</dt>
-<dd>the Mth parameter of the Nth plugin of a track/bus
-</dd>
-<dt>/route/send/gain</dt>
-<dd>the gain control ("fader") of the Nth send of a track/bus</dd>
-</dl>
-<p>Each of the specifications needs an address, which takes various forms too. For track-level controls (solo/gain/mute/recenable), the address is one the following:</p>
-<dl class="wide-table">
-<dt>a number, eg. "1"
-</dt>
-<dd>identifies a track or bus by its remote control ID
-</dd>
-<dt>B, followed by a number
-</dt>
-<dd>identifies a track or bus by its remote control ID within the current bank (see below for more on banks)
-</dd>
-<dt>one or more words
-</dt>
-<dd>identifies a track or bus by its name
-</dd>
-</dl>
-<p>
- For send/insert/plugin controls, the address consists of a track/bus
- address (as just described) followed by a number identifying the plugin/send
- (starting from 1). For plugin parameters, there is an additional third
- component: a number identifying the plugin parameter number (starting from
- 1).
-</p>
-<p>
- One additional feature: for solo and mute bindings, you can also add
- <code>momentary="yes"</code> after the control address. This is useful
- primarily for NoteOn bindings—when Ardour gets the NoteOn it
- will solo or mute the targetted track or bus, but then when a NoteOff
- arrives, it will un-solo or un-mute it.
-</p>
-
-<h4>Bindings to Ardour "functions"</h4>
-<p>
- Rather than binding to a specific track/bus control, it may be useful to
- have a MIDI controller able to alter some part of Ardour's state. A
- binding definition that does this looks like this:
-</p>
-<code>
- <Binding channel="1" note="13" function="transport-roll"/>
-</code>
-<p>
- In this case, a NoteOn message for note number 13 (on channel 1) will
- start the transport rolling. The following function names are available:
-</p>
-<dl class="narrower-table">
-<dt>
-<code>transport-stop</code>
-</dt>
-<dd>stop the transport
-</dd>
-<dt>
-<code>transport-roll</code>
-</dt>
-<dd>start the transport "rolling"
-</dd>
-<dt>
-<code>transport-zero</code>
-</dt>
-<dd>move the playhead to the zero position
-</dd>
-<dt>
-<code>transport-start</code>
-</dt>
-<dd>move the playhead to the start marker
-</dd>
-<dt>
-<code>transport-end</code>
-</dt>
-<dd>move the playhead to the end marker
-</dd>
-<dt>
-<code>loop-toggle</code>
-</dt>
-<dd>turn on loop playback
-</dd>
-<dt>
-<code>rec-enable</code>
-</dt>
-<dd>enable the global record button
-</dd>
-<dt>
-<code>rec-disable</code>
-</dt>
-<dd>disable the global record button
-</dd>
-<dt>
-<code>next-bank</code>
-</dt>
-<dd>Move track/bus mapping to the next bank (see Banks below)
-</dd>
-<dt>
-<code>prev-bank</code>
-</dt>
-<dd>Move track/bus mapping to the previous bank (see Banks below)
-</dd>
-</dl>
-
-<h4>Binding to Ardour "actions"</h4>
-<p>
- You can also bind a sysex or arbitrary message to any of the items
- that occur in Ardour's main menu (and its submenus). The best place
- to look for the (long) list of how to address each item is in your
- keybindings file, which will contain lines that look like this:
-</p>
-<code>
-(gtk_accel_path "<Actions>/Editor/temporal-zoom-in" "equal")
-</code>
-<p>
- To create a binding between an arbitrary MIDI message (we'll use a
- note-off on channel 1 of MIDI note 60 (hex) with release velocity
- 40 (hex)), the binding file would contain:
-</p>
-<code>
- <Binding msg="80 60 40" action="Editor/temporal-zoom-in"/>
-</code>
-<p>
- The general rule, when taken an item from the keybindings file and
- using it in a MIDI binding is to simply strip the
- <code><Action></code> prefix of the second field in the
- keybinding definition.
-</p>
-
-<h3>Banks and Banking</h3>
-<p>
- Because many modern control surfaces offer per-track/bus controls
- for far fewer tracks & busses than many users want to control,
- Ardour offers the relatively common place concept of <dfn>banks</dfn>. Banks
- allow you to control any number of tracks and/or busses easily,
- regardless of how many faders/knobs etc. your control surface has.<br />
- To use banking, the control addresses must be specified using the
- <dfn>bank relative</dfn> format mentioned above ("B1" to identify
- the first track of a bank of tracks, rather than "1" to identify
- the first track).
-</p>
-<p>
- One very important extra piece of information is required to use
- banking: an extra line near the start of the list of bindings
- that specifies how many tracks/busses to use per bank. If the
- device has 8 faders, then 8 would be a sensible value to use for
- this. The line looks like this:</p>
-<code>
- <DeviceInfo bank-size="8"/>
-</code>
-<p>
- In addition, you probably want to ensure that you bind something
- on the control surface to the <code>next-bank</code> and
- <code>prev-bank</code> functions, otherwise you and other users
- will have to use the mouse and the GUI to change banks, which
- rather defeats the purpose of the bindings.
-</p>
-<h2>A Complete (though muddled) Example</h2>
-<pre>
-<?xml version="1.0" encoding="UTF-8"?>
-<ArdourMIDIBindings version="1.0.0" name="pc1600x transport controls">
- <DeviceInfo bank-size="16"/>
- <Binding channel="1" ctl="1" uri="/route/gain B1"/>
- <Binding channel="1" ctl="2" uri="/route/gain B2"/>
- <Binding channel="1" ctl="3" uri="/route/send/gain B1 1"/>
- <Binding channel="1" ctl="4" uri="/route/plugin/parameter B1 1 1"/>
- <Binding channel="1" ctl="6" uri="/bus/gain master"/>
-
- <Binding channel="1" note="1" uri="/route/solo B1"/>
- <Binding channel="1" note="2" uri="/route/solo B2" momentary="yes"/>
-
- <Binding channel="1" note="15" uri="/route/mute B1" momentary="yes"/>
- <Binding channel="1" note="16" uri="/route/mute B2" momentary="yes"/>
-
- <Binding sysex="f0 0 0 e 9 0 5b f7" function="transport-start"/>
- <Binding sysex="f0 7f 0 6 7 f7" function="rec-disable"/>
- <Binding sysex="f0 7f 0 6 6 f7" function="rec-enable"/>
- <Binding sysex="f0 0 0 e 9 0 53 0 0 f7" function="loop-toggle"/>
-
- <Binding channel="1" note="13" function="transport-roll"/>
- <Binding channel="1" note="14" function="transport-stop"/>
- <Binding channel="1" note="12" function="transport-start"/>
- <Binding channel="1" note="11" function="transport-zero"/>
- <Binding channel="1" note="10" function="transport-end"/>
-</ArdourMIDIBindings>
-</pre>
-<p>
- Please note that channel, controller and note numbers are specified as
- decimal numbers in the ranges 1-16, 0-127 and 0-127 respectively
- (the channel range may change at some point).
-</p>
-
----
-title: Working With Encoders in Ardour
-menu_title: Working With Encoders
-part: subchapter
----
-
-<p>
- Encoders are showing up more frequently on controllers. However, they use
- the same MIDI events as Continuous Controllers and they have no standard
- way of sending that information as MIDI events. Ardour 4.2 has implemented
- 4 of the more common ways of sending encoder information.
-</p>
-<p>
- Encoders that send the same continuous values as a pot would are not
- discussed here as they are already supported by <code>ctl</code>.
-</p>
-<P>
- Encoders as this page talks about them send direction and offset that the
- DAW will add to or subtract from the current value.
-</p>
-<p>
- The 4 kinds of encoder supported are:
-</p>
-<ul>
-<li>
- enc-r: On the bcr/bcf2000 this is called "Relative Signed Bit". The most
- significant bit sets positive and the lower 6 signifcant bits are the
- offset.
-</li>
-<li>
- enc-l: The bcr2000 calls this "Relative Signed Bit 2". The most
- significant bit sets negative and the lower 6 signifcant bits are the
- offset. If you are using one of these two and the values are right but
- reversed, use the other. This one is the one the Mackie Control Protocol
- uses.
-</li>
-<li>
- enc-2: The bcr2000 calls this one "Relative 2s Complement". Positive
- offsets are sent as normal from 1 to 64 and negative offsets are sent as
- 2s complement negative numbers.
-</li>
-<li>
- enc-b: The bcr2000 calls this one "Relative Binary Offset". Positive
- offsets are sent as offset plus 64 and negative offsets are sent as 64
- minus offset.
-</li>
-</ul>
-<p>
- If the wrong one is chosen, either the positive or negative side will act
- incorrectly. It is not really possible to auto detect which one the
- controller is using. Trial and error is the only way if the specification
- of the controller is not known.
-</p>
-<p>
- Many controllers have more than one choice as well, check the manual for
- the surface.
-</p>
-
----
-title: MIDI Learn
-part: subchapter
----
-
-<h2>Philosophy</h2>
-
-<p>
- There are no "best" ways to map an arbitrary MIDI controller for controlling Ardour. There may be very legitimate reasons for different users to prefer quite different mappings.
-</p>
-
-<p>
- On every platform that Ardour runs on, there are excellent free-of-charge tools for making connections between MIDI hardware and "virtual" MIDI ports like the ones that Ardour creates and uses. Rather than waste precious developer time replicating these connection/patch managers, we prefer to leverage their existence by having users rely on them to actually connect Ardour to other MIDI devices and software. On OS X, we recommend Pete Yandell's MIDI Patchbay. On Linux, a wide variety of tools are available including QJackctl, aconnect, Patchage, and more.
-</p>
-
-<h2>Basics</h2>
-
-<ol>
- <li>Enable Generic MIDI control: <kbd class="menu">Edit > Preferences
- > Control Surfaces > Generic MIDI</kbd></li>
- <li>Connect Ardour's MIDI port named <samp>control</samp> to whatever
- hardware or software you want (using a MIDI patchbay app)</li>
- <li><kbd class="mod1 mouse">Middle</kbd>-click on whatever on-screen
- fader, plugin parameter control, button etc. you want to control</li>
- <li>A small window appears that says "Operate Controller now"</li>
- <li>Move the hardware knob or fader, or press the note/key.</li>
- <li>The binding is complete. Moving the hardware should control the Ardour fader etc. </li>
-</ol>
-
-<h2>Avoiding work in the future</h2>
-
-<p>
- If you want the bindings you set up to be used automatically in every session, the simplest thing to do is to use <kbd class="menu">Session > Save Template</kbd>. Then, when creating new sessions, select that template and all the bindings will be automatically set up for you.
-</p>
-
----
-title: Using the Presonus Faderport
-menu_title: Presonus Faderport
-part: subchapter
----
-
-<p>
- Since version 4.5, Ardour has had full support for the Presonus
- Faderport. This is a compact control surface featuring a single
- motorized fader, a single knob (encoder) and 24 buttons with fixed
- labels. It is a relatively low-cost device that functions very well
- to control a single (selected) track or bus, along with a variety of
- other "global" settings and conditions.
-</p>
-
-<h2>Connecting the Faderport</h2>
-
-<p>
- The Faderport comes with a single USB socket on the back. Connect a
- suitable USB cable from there to a USB port on your computer. As of
- the end of 2015, you should avoid USB3 ports—these cause erratic
- behaviour with the device. This issue might get fixed by Presonus in
- the future.
-</p>
-
-<p class="well">
- Ardour uses the Faderport in what Presonus calls "native" mode. You
- do not need to do anything to enable this—Ardour will set the
- device to be in the correct mode. In native mode, the Faderport
- sends and receives ordinary MIDI messages to/from the host, and the
- host understands the intended meaning of these messages. We note
- this detail to avoid speculation about whether Ardour supports the
- device via the HUI protocol—it does not.
-</p>
-
-<p>
- The Faderport 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 Faderport to Ardour, open the Preferences dialog, and
- then click on "Control Surfaces". Click on the "Enable" button
- in the line that says "Faderport" in order to activate Ardour's
- Faderport support. Then double click on the line that says
- "Faderport". A new dialog will open, containing (among other things)
- two dropdown selectors that will allow you to identify the MIDI
- ports where your Faderport is connected.
-</p>
-
-<p>
-<img alt="the Faderport configuration dialog"
- src="/images/faderport_dialog.png">
-</p>
-
-<p>
- Once you select the input and output port, Ardour will initialize
- the Faderport and it will be ready to use. You only need do this
- once: once these ports are connected and your session has been
- saved, the connections will be made automatically in this and other
- future sessions.
-</p>
-
-<p>
- You do not need to use the power supply that comes with the
- Faderport but without it, the fader will not be motorized. This
- makes the overall experience of using the Faderport much less
- satisfactory, since the fader will not move when Ardour tells it
- to, leading to very out-of-sync conditions between the physical
- fader position and the "fader position" inside the program.
-</p>
-
-<h2>Using the Faderport</h2>
-
-<p>
- The Faderport's controls can be divided into three groups:
- <ol>
- <li>Global controls such as the transport buttons</li>
-
- <li>Controls which change the settings for particular track or
- bus</li>
-
- <li>Controls which alter which track or bus is modified by the
- per-track/bus controls.</li>
- </ol>
-</p>
-<p>
- Because the Faderport has only a single set of per-track controls,
- by default those controls operate on the first selected track or
- bus. If there is no selected track or bus, the controls will do
- nothing.
-</p>
-
-<h3>Transport Buttons</h3>
-<p>
- The transport buttons all work as you would expect.
- <dl>
- <dt>Rewind</dt>
- <dd>
- <p>
- When pressed on its own, starts the transport moving backwards. Successive presses
- speed up the "rewind" behaviour.
- </p>
- <p>
- If pressed while also holding the Stop button, the playhead will
- return to the zero position on the timeline.
- </p>
- <p>
- If pressed while also holding the Shift button, the playhead will
- move to the session start marker.
- </p>
- </dd>
- <dt>Fast Forward</dt>
- <dd>
- <p>
- When pressed on its own, starts the transport moving faster than normal. Successive presses
- speed up the "fast forward" behaviour.
- </p>
- <p>
- If pressed while also holding the Shift button, the playhead
- will move to the session end marker.
- </p>
- </dd>
- <dt>Stop</dt>
- <dd>
- Stops the transport. Also used in combination with the Rewind
- button to "return to zero".
- </dd>
- <dt>Play</dt>
- <dd>
- Starts the transport. If pressed while the transport is
- already rolling at normal speed, causes the playhead to jump to
- the start of the last "roll" and continue rolling ("Poor man's
- looping").
- </dd>
- <dt>Record Enable</dt>
- <dd>Toggles the global record enable setting
- </dd>
- </dl>
-</p>
-
-<h3>Other Global Controls</h3>
-<p>
- The Mix, Proj, Trns buttons do not obviously correspond any
- particular functions or operations in Ardour. We have therefore
- allowed users to choose from a carefully curated set of possible
- actions that seem related to the button labels in some clear
- way. This can be done via the Faderport configuration dialog
- accessed via <code>Preferences > Control Surfaces</code>. Each
- button has 3 possible actions associated with it:
- <ul>
- <li>Plain Press: action to be taken when the button is pressed on
- its own.</li>
- <li>Shift-Press: action to be taken when the button is pressed in
- conjunction with the Shift button.</li>
- <li>Long Press: action to be taken when the button is pressed on
- its own and held down for more than 0.5 seconds.</li>
- </ul>
- Click on the relevant drop-down selector to pick an action as you
- prefer.
-</p>
-<p>
- The User button also has no obvious mapping to specific Ardour
- functionality, so we allow users to choose from <em>any</em>
- possible GUI action. The menu for selecting the action is somewhat
- confusing and it can be hard to find what you're looking
- for. However, all possible actions are there, so keep looking!
-<p>
- <dl>
- <dt>Mix</dt>
- <dd>
- <p>
- Possible actions include:
- <ul>
- <li>Toggle Editor & Mixer visibility</li>
- <li>Show/Hide the Editor mixer strip</li>
- </ul>
- </p>
- </dd>
- <dt>Proj</dt>
- <dd>
- <p>
- Possible actions include:
- <ul>
- <li>Toggle Meterbridge visibility</li>
- <li>Toggle Session Summary visibility</li>
- <li>Toggle Editor Lists visibility</li>
- <li>Zoom to session</li>
- <li>Zoom in</li>
- <li>Zoom out</li>
- </ul>
- </p>
- </dd>
- <dt>Trns</dt>
- <dd>
- <p>
- Possible actions include:
- <ul>
- <li>Toggle Locations window visibility</li>
- <li>Toggle Metronome</li>
- <li>Toggle external sync</li>
- <li>Set Playhead at current pointer position</li>
- </ul>
- </p>
- </dd>
- <dt>Undo/Redo</dt>
- <dd>
- Undo Causes the last operation carried out in the editor to be
- undone. When pressed in conjuction with the Shift button, it
- causes the most recent undone operation to be re-done.
- </dd>
- <dt>Punch</dt>
- <dd>
- <p>
- When pressed on its own, toggles punch recording. If there is no
- punch range set for the session, this will do nothing.
- </p>
- <p>
- When pressed in conjunction with the Shift button, this moves
- the playhead to the previous Marker
- </p>
- </dd>
- <dt>User</dt>
- <dd>
- <p>
- See above. Any and all GUI-initiated actions can be driven with
- by pressing this button on its own, or with a "long" press.
- </p>
- <p>
- When pressed in conjunction with the Shift button, this will move
- the playhead to the next marker.
- </p>
- </dd>
- <dt>Loop</dt>
- <dd>
- <p>
- When pressed on its own, this toggles loop playback. If the
- Ardour preference "Loop-is-mode" is enabled, this does nothing
- to the current transport state. If that preference is disabled,
- then engaging loop playback will also start the transport.
- </p>
- <p>
- When pressed in conjunction with the Shift button, this will
- create a new (unnamed) marker at the current playhead
- position.
- </p>
- </dd>
- </dl>
-</p>
-
-<h3>Per-track Controls</h3>
-<p>
- <dl>
- <dt>Mute</dt>
- <dd>
- This toggles the mute setting of the currently controlled
- track/bus. The button will be lit if the track/bus is muted.
- </dd>
- <dt>Solo</dt>
- <dd>
- This toggles the solo (or listen) setting of the currently
- controlled track/bus. The button will be lit if the track/bus is
- soloed (or set to listen mode).
- </dd>
- <dt>Rec</dt>
- <dd>
- This toggles the record-enabled setting of the currently
- controlled track/bus. The button will be lit if the track is
- record-enabled. This button will do nothing if the Faderport is
- controlling a bus.
- </dd>
- <dt>Fader</dt>
- <dd>
- The fader controls the gain applied to the currently controlled
- track/bus. If the Faderport is powered, changing the gain in
- Ardour's GUI or via another control surface, or via automation,
- will result in the fader moving under its own control.
- </dd>
- <dt>Knob/Dial/Encoder</dt>
- <dd>
- <p>
- The knob controls 1 or 2 pan settings for the current
- controlled track/bus. When used alone, turning the knob controls
- the "azimuth" or "direction" (between left and right) for the
- panner in the track/bus (if any). This is all you need when
- controlling tracks/busses with 1 input and 2 outputs.
- </p>
- <p>
- If controlling a 2 input/2 output track/bus, Ardour's panner
- has two controls: azimuth (direction) and width. The width
- must be reduced to less than 100% before the azimuth can be
- changed. Pressing the "Shift" button while turning the knob
- will alter the width setting.
- </p>
- <p>
- The knob can also be turned while the "User" button is held,
- in order to modify the input gain for the currently controlled
- track.
- </p>
- </dd>
- <dt>Read</dt>
- <dd>
- Enables playback/use of fader automation data by the controlled track/bus.
- </dd>
- <dt>Write</dt>
- <dd>
- Puts the fader for the controlled track/bus into automation
- write mode. While the transport is rolling, all fader changes
- will be recorded to the fader automation lane for the relevant track/bus.
- </dd>
- <dt>Touch</dt>
- <dd>
- Puts the fader for the controlled track/bus into automation
- touch mode. While the transport is rolling, touching the fader
- will initiate recording all fader changes until the fader is
- released. When the fader is not being touched, existing
- automation data will be played/used to control the gain level.
- </dd>
- <dt>Off</dt>
- <dd>
- This disables all automation modes for the currently controlled
- track/bus. Existing automation data will be left unmodified by
- any fader changes, and will not be used for controlling gain.
- </dd>
- </dl>
-</p>
-
-<h3>Track Selection Controls</h3>
-<p>
- You can manually change the track/bus controlled by the Faderport by
- changing the selected track in Ardour's editor window. If you select
- more than 1 track, the Faderport will control the first selected
- track and <em>only</em> that track/bus.
-</p>
-<p>
- <dl>
- <dt>Left (arrow)</dt>
- <dd>
- This causes the Ardour GUI to select the previous track/bus
- (using the current visual order in the editor window), which
- will in turn cause the Faderport to control that track. If there
- is no previous track/bus, the selected track/bus is left
- unchanged, and the Faderport continues to control it.
- </dd>
- <dt>Right (arrow)</dt>
- <dd>
- This causes the Ardour GUI to select the next track/bus
- (using the current visual order in the editor window), which
- will in turn cause the Faderport to control that track. If there
- is no next track/bus, the selected track/bus is left
- unchanged, and the Faderport continues to control it.
- </dd>
- <dt>Output</dt>
- <dd>
- <p>
- Pressing the Output button causes the Faderport to control
- the fader, pan, mute and solo settings of the Master bus. If
- your session does not contain a Master bus, it does nothing.
- This is a toggle button—pressing it again returns Faderport
- to controlling whichever track/bus was selected before the
- first press of the Output button.
- </p>
- <p>
- If your session uses Ardour's monitor section, you can use
- Shift-Output to assign it to the Faderport in the same way
- that Output assigns the Master bus. This is also a toggle
- setting, so the second Shift-Output will return the Faderport
- to controlling whichever track/bus was selected before.
- </p>
- <p>
- If you press Shift-Output after a single press to Output
- (i.e. control the Monitor Section while currently controlling
- the Master bus) or vice versa (i.e. control the Master bus
- while currently controlling the Monitor Section), the press
- will be ignored. This avoids getting into a tricky situation
- where it is no longer apparent what is being controlled and
- what will happen if you try to change it.
- </p>
- </dd>
- <dt>Bank</dt>
- <dd>
- The "Bank" button is currently not used by Ardour
- </dd>
- </dl>
-</p>
-
----
-title: Using the Ableton Push 2
-menu_title: Ableton Push 2
-part: subchapter
----
-
-<p>
- <img alt="the Ableton Push 2 surface" src="/images/push2-main.jpg">
-</p>
-
-<p>
- 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 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>
- 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
- once: once these ports are connected and your session has been
- saved, the connections will be made automatically in this and other
- future sessions.
-</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:
- <dl>
- <dt>Perform using the 8 x 8 pad "grid"</dt>
- <dd>The Push 2 has really lovely pressure-sensitive pads that can
- also generate either aftertouch or note (polyphonic) pressure.</dd>
- <dt>Global Mixing</dt>
- <dd>See many tracks at once, and control numerous parameters for each.</dd>
- <dt>Track/Bus Mixing</dt>
- <dd>View a single track/bus, with even more parameters for the track.</dd>
- <dt>Choose the mode/scale, root note and more for the pads</dt>
- <dd>37 scales are available. Like Live, Ardour offers both
- "in-key" and "chromatic" pad layouts.</dd>
- </dl>
-
- … 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"
- (no extra latency is incurred from this routing). Although you can
- manually connect this port to whatever you wish, the normal
- 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
- controls on the Push 2 will <em>not</em> not be delivered to the
- "Push 2 Pads" port. This makes no difference in practice, because
- the other controls do not send messages that are useful for musical
- performance.
-</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>
- <dt>Volumes</dt>
- <dd>The display shows a knob and text displaying
- the current gain setting for the track, and a meter that
- corresponds precisely to the meter shown in the Ardour GUI for
- that track. Changing the meter type (e.g. from Peak to K12) in the
- GUI will also change it in the Push 2 display. The physical knob
- will alter track/bus gain.
- </dd>
- <dt>Pans</dt>
- <dd>The display shows a knob indicating the pan direction/azimuth
- for the corresponding track/bus. Turning the physical knob will
- pan the track left and right. If the track/bus has no panner
- (i.e. it has only a single output), no knob is shown and the
- physical knob will do nothing. </dd>
- <dt>Pan Widths</dt>
- <dd><p>For tracks with 2 outputs, the display will show a knob
- indicating the pan width setting for the corresponding
- track/bus. The physical knob can be turned to adjust the
- width.
- </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
- reduce the width in order to pan it. Similarly, a track panned
- anywhere other than dead center has limits on the maximum
- width setting. If these concepts are not familiar to you,
- please be aware than many DAWs use a "panner" that actually
- implement "balance" and not "panning", hence the difference.
- </p>
- </dd>
- <dt>A Sends</dt>
- <dd>The display shows a knob indicating the gain level for the
- first send in that track. If the track has no send, no knob will
- be shown, and the physical knob for that track will do nothing.
- </dd>
- <dt>B Sends, C Sends, D Sends</dt>
- <dd>Like "A Sends", but for the 2nd, 3rd and 4th sends of a
- track/bus respectively.
- </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
- highlighted, and the selection will change in Ardour's GUI as well
- (and also any other control surfaces).
-</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>
- <li>The solo button will blink red</li>
- <li>Track names will be prefixed by "*" if they are soloed, and
- "-" if they are muted due to soloing.</li>
- </ol>
-</p>
-
-<p>
- To cancel solo, either:
- <ul>
- <li>Select the soloed track(s) and press the solo button
- again</li>
- <li>Press and hold the solo button for more than 1 second</li>
- </ul>
-</p>
-
-<h2>Track Mix</h2>
-
-<p>Track Mix mode allows you to focus on a single track in more detail
- than is possible in Global Mix mode. To enter (or leave) Track Mix
- mode, press the "Mix" button.
-</p>
-
-<p>
- In Track Mix mode, various aspects of the state of the first
- selected track/bus will be displayed on the Push 2. Above the
- display, the first 4 knobs control track volume (gain), pan
- directiom/azimuth, pan width, and where appropriate, track input
- trim.
-</p>
-
-<p>
- Below the display, 7 buttons provide immediate control of mute,
- solo, rec-enable, monitoring (input or disk or automatic), solo
- isolate and solo safe state. When a a track is muted due to other
- track(s) soloing, the mute button will flash (to differentiate from
- its state when it is explicitly muted).
-</p>
-
-<p>
- The video display also shows meters for the track, which as in
- Global Mix mode, precisely match the meter type shown in Ardour's
- GUI. There are also two time displays showing the current playhead
- position in both musical (beats|bars|ticks) format, and as
- hours:minutes:seconds.
-</p>
-
-<p>
- To change which track is visible in Track Mix mode, use the
- left/right arrow/cursor keys just below and to the right of the
- video display.
-</p>
-
-<h2>Scale Selection</h2>
-
-<p>
- Press the Scale button to enter Scale mode. The display will look
- like this:
-</p>
-
-<p>
- <img alt="track mix mode on Push2 screen"
- src="/images/push2-scale.png">
-</p>
-
-<p>
- In the center, 37 scales are presented. Scroll through them by
- either using the cursor/arrow keys to the lower right of the
- display, or the knobs above the display. The scale will change
- dynamically as you scroll. You can also scroll in whole pages using
- the upper right and upper left buttons above the display (they will
- display "<" and ">" if scrolling is possible).
-</p>
-
-<p>
- To change the root note of the scale, press the corresponding button
- above or below the video display.The button will be lit to indicate
- your selection (and the text will be highlighted).
-</p>
-
-<p>
- By default, Ardour configures the Push 2 pads to use "in-key" mode,
- where all pads correspond to notes "in" the chosen scale. Notes
- corresponding to the root note, or the equivalent note in higher
- octaves, are highlighted with the color of the current target MIDI
- track.
-</p>
-
-<p>
- In
- "chromatic" mode, the pads correspond to a continuous sequence of
- notes starting with your selected root note. Pads corresponding to
- notes in the scale are illuminated; those corresponding to the root
- note are lit with the color the current target MIDI track. Other
- pads are left dark, but you can still play them.
-</p>
-
-<p>
- To switch between them, press button on the lower left of the video
- display; the text above it will display the current mode (though it
- is usually visually self-evident from the pad lighting pattern).
-</p>
-
-<p>
- To leave Scale mode, press the "Scale" button again. You may also
- use the upper left button above the display, though if you have
- scrolled left, it may require more than one press.
-</p>
-
-<h2>Specific Button/Knob Functions</h2>
-
-<p>
- In addition to the layouts described above, many (but not all) of
- the buttons and knobs around the edges of the Push 2 will carry out
- various functions related to their (illuminated) label. As of Ardour
- 5.4, this includes:
- <dl>
- <dt>Metronome (button and adjacent knob)</dt>
- <dd>
- Enables/disables the click (metronome). The knob directly above
- it will control the volume (gain) of the click.
- </dd>
- <dt>Undo/Redo</dt>
- <dd>
- Undo or redo the previous editing operation.
- </dd>
- <dt>Delete</dt>
- <dd>
- Deletes the currently selected region, or range, or
- note. Equivalent to using Ctrl/Cmd-x on the keyboard.
- </dd>
- <dt>Quantize</dt>
- <dd>
- If a MIDI region is selected in Ardour, this will open the
- quantize dialog.
- </dd>
- <dt>Duplicate</dt>
- <dd>
- Duplicates the current region or range selection.
- </dd>
- <dt>Rec-Enable</dt>
- <dd>
- Enables and disables Ardour's global record enable state.
- </dd>
- <dt>Play</dt>
- <dd>
- Starts and stops the transport. Press Shift-Play to return to the session start.
- </dd>
- <dt>Add Track</dt>
- <dd>
- Opens Ardour's Add Track/Bus dialog.
- </dd>
- <dt>Browse</dt>
- <dd>
- Open's Ardour's import dialog to select and audition existing
- audio and MIDI files.
- </dd>
- <dt>Master</dt>
- <dd>
- Pressing this button jumps directly to Track Mix mode, with the
- master out bus displayed.
- </dd>
- <dt>Cursor arrows</dt>
- <dd>
- These are used by some modes to navigate within the display (e.g
- Scale mode). In other modes, the up/down cursor arrows will
- scroll the GUI display up and down, while the left/right cursor
- arrows will generally scroll within the Push 2 display itself.
- </dd>
- <dt>Repeat</dt>
- <dd>
- Enables/disables loop playback. This will follow Ardour's "loop
- is mode" preference, just like the loop button in the Ardour
- GUI.
- </dd>
- <dt>Octave buttons</dt>
- <dd>
- These shift the root note of the current pad scale up or down by
- 1 octave.
- </dd>
- <dt>Page buttons</dt>
- <dd>
- These scroll Ardour's editor display left and right along the
- timeline.
- </dd>
- <dt>Master (top right) knob</dt>
- <dd>
- This knob controls the gain/volume of Ardour's main output. If
- the session has a monitor saec
- </dd>
- </dl>
-</p>
-
-
----
-title: Configuring MIDI
-part: chapter
----
-
-
----
-title: Using External MIDI Devices
-part: subchapter
----
-
-<p class="fixme">Add content</p>
-
-
----
-title: Setting Up MIDI
-part: subchapter
----
-
-<h2>What Can Ardour Do With MIDI?</h2>
-<p>
- <dfn><abbr title="Musical Instrument Digital
- Interface">MIDI</abbr></dfn> is a way to describe musical
- performances and to control music hardware and software.
-</p>
-<p>Ardour can import and record MIDI data, and perform a variety of
- editing operations on it. Furthermore, MIDI can be used to control
- various functions of Ardour.
-</p>
-
-<h2>MIDI Handling Frameworks</h2>
-<p>
- MIDI input and output for Ardour are handled by the same "engine"
- that handles audio input and output. Up to release 3.5, that means
- that all MIDI I/O takes place via JACK. JACK itself uses the
- native MIDI support of the operating system to receive and send
- MIDI data. The native MIDI support provides device drivers for MIDI
- hardware and libraries needed by software applications that want to
- work with MIDI.
+ The <dfn>Edit</dfn> menu groups together the actions related to the edition, and so will be mostly used while in Editor mode.
</p>
<dl>
-<dt>OS X</dt>
-<dd> <dfn>CoreMIDI</dfn> is the standard MIDI framework on OSX systems.
-</dd>
-<dt>Linux</dt>
-<dd>
- <dfn><abbr title="Advanced Linux Sound API">ALSA</abbr> MIDI</dfn>
- is the standard MIDI framework on Linux systems.
-</dd>
+ <dt>Undo (<em>action</em>)</dt><dd>Reverts the last editing operation, namely <em>action</em></dd>
+ <dt>Redo</dt><dd>Does the last editing operation again, after an Undo</dd>
+
+ <dt>Undo Selection Change</dt><dd>Reverts the last selection operation</dd>
+ <dt>Redo Selection Change</dt><dd>Does the last selection operation again after an Undo Selection Change</dd>
+
+ <dt>Cut</dt><dd>Deletes the current selection, but puts it in memory ready to be pasted</dd>
+ <dt>Copy</dt><dd>Copies the current selection to memory</dd>
+ <dt>Paste</dt><dd>Pastes the memory at the <a href="/ardours-interface/the-editor/the-toolbar/the-edit-point-control/">edit point</a>, after a Cut or Copy operation</dd>
+
+ <dt>Select</dt>
+ <dt class="sub1">Select All Objects</dt><dd>Selects all the regions and automation pints in the session</dd>
+ <dt class="sub1">Select All Tracks</dt><dd>Selects all the tracks, busses and control masters in the session</dd>
+ <dt class="sub1">Deselect All</dt><dd>Deselects all objects or tracks, nothing is selected</dd>
+ <dt class="sub1">Invert Selection</dt><dd>Select the previously unselected regions, and deselect the previously selected ones</dd>
+
+ <dt class="sub1">Set Range to Loop Range</dt><dd>Creates a range selection on the selected tracks, based on the selected loop markers, and switches to <a href="/ardours-interface/the-editor/the-toolbar/the-toolbox/">Range Mode tool</a></dd>
+ <dt class="sub1">Set Range to Punch Range</dt><dd>Same as above, based on the selected punch markers</dd>
+ <dt class="sub1">Set Range to Selected Regions</dt><dd>Same as above, based on the selected regions (i.e. from the start of the earliest region to the end of the latest one)</dd>
+
+ <dt class="sub1">Select All After Edit Point</dt><dd>Select all the regions and automation points that exist after the Edit Point, even if the region starts before it. If some tracks are selected, only selects on these tracks.</dd>
+ <dt class="sub1">Select All Before Edit Point</dt><dd>Same as above, but before the Edit point (i.e. to the left of it)</dd>
+ <dt class="sub1">Select All Overlapping Edit Range</dt><dd>Select all the regions and automation points of which at least a part is in the current selection range</dd>
+ <dt class="sub1">Select All Inside Edit Range</dt><dd>Selects all the regions that are completely inside the selection range, i.e. their start and end are inside the range. If some tracks are selected, only selects on these tracks.</dd>
+ <dt class="sub1">Select All in Punch Range</dt><dd>Selects all the regions of which a part in in the punch range. If some tracks are selected, only selects on these tracks.</dd>
+ <dt class="sub1">Select All in Loop Range</dt><dd>Same as above, based on the loop range</dd>
+
+ <dt class="sub1">Move Range Start to Previous Region Boundary</dt><dd>Extends the left boundary of the range to the left to the next region start or end. The region must be in the range.</dd>
+ <dt class="sub1">Move Range Start to Next Region Boundary</dt><dd>Same as above, to the right (reduces the selection)</dd>
+ <dt class="sub1">Move Range End to Previous Region Boundary</dt><dd>Same as above, with the right edge of the range, to the left (reduces the selection)</dd>
+ <dt class="sub1">Move Range End to Next Region Boundary</dt><dd>Same as above, with the right edge, to the right (extends the selection)</dd>
+
+ <dt class="sub1">Start Range</dt><dd>Sets the left edge of the range to the Edit point</dd>
+ <dt class="sub1">Finish Range</dt><dd>Sets the right edge of the range to the Edit point</dd>
+
+ <dt class="sub1">Select Next Track or Bus</dt><dd>Select the track or bus under the currently selected one. If multiple tracks are selected, only the first one is considered</dd>
+ <dt class="sub1">Select Previous Track or Bus</dt><dd>Same as above, with the track/bus above the first one selected.</dd>
+
+ <dt>Delete</dt><dd>Deletes all that is currently selected</dd>
+ <dt>Crop</dt><dd>Cuts the parts of the regions that are outside the range boundaries. Only applies on the regions that belong at least in part to the range.</dd>
+ <dt>Split/Separate</dt><dd>Cuts the selected regions at the Edit point, separating them in two regions</dd>
+ <dt>Separate</dt>
+ <dt class="sub1">Separate Under</dt><dd>Removes all the parts of the regions that are under the selected one. Once done, the selected region is alone on its part of the track.</dd>
+ <dt class="sub1">Separate Using Loop Range</dt><dd>Cuts the selected regions or the regions on the selected tracks along the Loop range's start and end markers. If nothing is selected, acts on all tracks at once.</dd>
+ <dt class="sub1">Separate Using Punch Range</dt><dd>Same as above, with the Punch range markers</dd>
+ <dt>Align</dt>
+ <dt class="sub1">Align Start</dt><dd>Moves the selected regions to align the beginning of the regions to the Edit point</dd>
+ <dt class="sub1">Align Start Relative</dt><dd>When multiple regions are selected, moves all the regions together as a block to align the beginning of the earliest one to the Edit point.</dd>
+ <dt class="sub1">Align End</dt><dd>Moves the selected regions to align the end of the regions to the Edit point</dd>
+ <dt class="sub1">Align End Relative</dt><dd>When multiple regions are selected, moves all the regions together as a block to align the end of the latest one to the Edit point.</dd>
+ <dt class="sub1">Align Sync</dt><dd>Moves the selected regions to align the Sync point of the regions to the Edit point</dd>
+ <dt class="sub1">Align Sync Relative</dt><dd>When multiple regions are selected, moves all the regions together as a block to align the earliest Sync point to the Edit point.</dd>
+ <dt>Fade</dt>
+ <dt class="sub1">Fade Range Selection</dt><dd>For all the regions that either begin or end in the range, create a fade in or out on the regions length.</dd>
+ <dt class="sub1">Set Fade In Length</dt><dd>If the edit point is withing the region boundaries, adjusts selected audio regions' fade in to end at the edit point.</dd>
+ <dt class="sub1">[] Fade In</dt><dd>Toggles the fade in on the selected region on or off</dd>
+ <dt class="sub1">Set Fade Out Length</dt><dd>Same as above, for the fade out</dd>
+ <dt class="sub1">[] Fade Out</dt><dd>Toggles the fade out on the selected region on or off</dd>
+
+ <dt>Remove Last Capture</dt><dd>Destroy the last recording. A prompt reminds the user this <em>cannot</em> be undone.</dd>
+
+ <dt>Edit point</dt>
+ <dt class="sub1">Change Edit Point</dt><dd>Toggles between the mouse and the playhead as the Edit point</dd>
+ <dt class="sub1">Change Edit Point Including Marker</dt><dd>Toggles between the mouse, the playhead and marker as the Edit point</dd>
+ <dt>Snap Mode</dt>
+ <dt class="sub1">() No Grid</dt><dd>Disables <a href="/ardours-interface/the-editor/the-toolbar/the-grid-controls/">snapping</a>, i.e. allows free movement of regions and boundaries</dd>
+ <dt class="sub1">() Grid</dt><dd>Forces snapping, so any move of region boundary will be lined to the grid as chosen</dd>
+ <dt class="sub1">() Magnetic</dt><dd>If the movement of the region or boundary happens near a grid line, snaps, otherwise, allow free movement</dd>
+
+ <dt class="sub1">Next Snap Mode</dt><dd>Toggles between the No Grid, Grid and Magnetic snap modes</dd>
+ <dt class="sub1">Next Snap Choice</dt><dd>Circles through the snap choices, as detailed below</dd>
+ <dt class="sub1">Previous Snap Choice</dt><dd>Circles through the snap choices, as detailed below, in reverse order</dd>
+ <dt class="sub1">Next Musical Snap Choice</dt><dd>Circles through the musical snap choices, e.g. those expressed in bars and beats</dd>
+ <dt class="sub1">Previous Musical Snap Choice</dt><dd>Same as previous, but in reverse order</dd>
+ <dt>Snap To</dt>
+ <dt class="sub1">Snap to CD Frame</dt><dd>The grid unit will be 1/75th of a second</dd>
+ <dt class="sub1">Snap to Timecode Frame/Second/Minute</dt><dd>The grid unit will be based on the timecode settings for the session</dd>
+ <dt class="sub1">Snap to Second/Minute</dt><dd>The grid unit will be based on absolute times</dd>
+ <dt class="sub1">Snap to <em>n</em>th</dt><dd>The grid unit will be 1/<em>n</em> beats and will depend on the tempo and meter in effect at that point in the timeline.</dd>
+ <dt class="sub1">Snap to Beat</dt><dd>Same as above, whole beat</dd>
+ <dt class="sub1">Snap to Bar</dt><dd>Same as above, whole bar</dd>
+ <dt class="sub1">Snap to Mark</dt><dd>The grid will be made of markers</dd>
+ <dt class="sub1">Snap to Region Start</dt><dd>No grid, the regions will snap to the closest region start on any track</dd>
+ <dt class="sub1">Snap to Region End</dt><dd>Same as above with the regions' ends</dd>
+ <dt class="sub1">Snap to Regions Sync</dt><dd>Same as above, with the Sync points (by default, start of the region)</dd>
+ <dt class="sub1">Snap to Region Boundaries</dt><dd>Same as above, for both the starts and ends of regions</dd>
+
+ <dt>Tempo</dt><dd></dd>
+ <dt class="sub1">Set Tempo from Region = Bar</dt><dd>Computes the tempo so that the duration of the first selected region is 1 bar. Ardour prompts if the user wants it to be the global tempo, or a tempo marker at the beginning of the region used</dd>
+ <dt class="sub1">Set Tempo from Edit Range = Bar</dt><dd>Same thing, with the current Range instead of a region</dd>
+ <dt>[] Smart Object Mode</dt><dd>Toggles the Smart Mode, allowing the mouse to be in Range Mode in the upper half of a region, and in Grab Mode in the lower half</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>Preferences</dt><dd>Displays the <a href="/preferences-and-session-properties/preferences-dialog/">Preferences</a> panels, allowing to change Ardour's behaviour</dd>
</dl>
-<p class="note">
- On Linux systems, <dfn>QJackCtl</dfn> control software displays ALSA MIDI
- ports under its "ALSA" tab (it does not currently display CoreMIDI
- ports). By contrast, JACK MIDI ports show up under
- the <kbd class="menu">MIDI</kbd> tab in QJackCtl.
-</p>
-
-<h2>JACK MIDI Configuration</h2>
-<p>
-By default, JACK will <strong>not</strong> automatically detect and use existing MIDI
-ports on your system. You must choose one of several ways
-of <dfn>bridging</dfn> between the native MIDI frameworks
-(e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections
-below.
-</p>
-
---
-title: MIDI on Linux
+title: The Region Menu
part: subchapter
---
-<p>The right approach for using MIDI on Linux depends on which version of
-JACK you use. The world divides into:</p>
-
-<dl>
-<dt>Systems using JACK 1, versions 0.124 or later</dt>
-<dd>On these systems, just start JACK with the <code>-X alsa_midi</code> server argument. To support legacy control applications, you can also use the <code>-X seq</code> argument to the ALSA backend of JACK and get the exact same results.</dd>
-<dt>All others</dt>
-<dd>Use a2jmidid to act as a bridge between ALSA MIDI and JACK. Do not use the <code>-X seq</code> or <code>-X raw</code> arguments—the timing and performance of these options is not acceptable.
-</dd>
-</dl>
-
-<h2>a2jmidid</h2>
-
-<p>
- <dfn>a2jmidid</dfn> is an application that bridges between the system
- <abbr title="Musical Instrument Digital Interface">MIDI</abbr> ports and
- <abbr title="JACK Audio Connection Kit">JACK</abbr>.
-</p>
-
-<p>
- First you should make sure that there is no ALSA sequencer support enabled
- in JACK. To do that open QJackCtl's <kbd class="menu">Setup</kbd> window.
-</p>
-
-<p>
- Set <kbd class="menu">Settings > MIDI Driver</kbd> to <kbd
- class="input">none</kbd>.
- Then uncheck the <kbd class="optoff">Misc > Enable ALSA Sequencer
- support</kbd> option.<br />
- Now it's time to restart your jack server before going on.
-</p>
-
-<h3>Check for a2jmidid availability</h3>
-
-<p>
- First, check whether a2jmidid is already installed in your system. After
- starting your JACK server, go to the command line and type
-</p>
-
-<kbd class="cmd lin">a2jmidid -e</kbd>
-
-<p>
- If a2jmidid does not exist, install it with the software manager of your
- Linux distribution and try again.
-</p>
-
-<h2>Check available MIDI ports</h2>
-
<p>
- If you have correctly configured JACK for MIDI, then your MIDI ports should appear in
- qjackctl under <kbd class="menu">Connections > MIDI </kbd>.
+ The <kbd class="menu">Region</kbd> Menu is where the user can tweak its regions, the parts of audio or MIDI that sit on the timeline.
</p>
-<h3>Making it automatic</h3>
-
-<p>
-Once you've verified that the ports appear in JACK as expected, you
-can make this happen whenever you start JACK.
-</p>
+<dl>
+ <dt>Insert Region from Region List</dt><dd>If a region is selected in the Editor List, add it at the Edit point</dd>
+ <dt>Play</dt><dd>Starts playback at the beginning of the selected region(s), and stops at its(their) end</dd>
+ <dt>Loop</dt><dd>Creates a loop range on the selected region's boundaries, and starts the looped playback</dd>
+ <dt>Rename...</dt><dd>Changes the name of the region, that appears in its top left area</dd>
+ <dt>Properties...</dt><dd>Shows the <kbd class="menu">Region properties</kbd> window, that displays detailed information about the region and allow for some modifications</dd>
+ <dt>Loudness Analysis...</dt><dd>Shows the <kbd class="menu">Audio Report/Analysis</kbd> window, that displays detailed <a href="/meters/">dBFS information</a> as well as a spectrogram (dBFS of frequency against time)</dd>
+ <dt>Spectral Analysis...</dt><dd>Shows the <kbd class="menu">Audio Report/Analysis</kbd> window, that displays a integrated spectral view of the region (dBFS agaisnt frequency)</dd>
+ <dt>Edit</dt>
+ <dt class="sub1">Combine</dt><dd>Creates a new region by joining the selected audio regions in the same track, and replaces those region with the newly created compound. The same rules are applied to create the compound as for playback regarding e.g. layering</dd>
+ <dt class="sub1">Uncombine</dt><dd>Splits back the compound created by <em>combining</em> into its original audio regions</dd>
+ <dt class="sub1">Pitch Shift...</dt><dd>Changes the tune of the audio region, by octave, semitones or percentage, based on spectral analysis. Optionaly, and if they have been set for the region, preserves the formants</dd>
+ <dt class="sub1">Split/Separate</dt><dd>Cuts the selected regions at the Edit point, separating them in two regions</dd>
+ <dt class="sub1">Split at Percussion Onset</dt><dd>Allows splitting the selected regions on its PErcussion Onsets marker as set by the Rhythm Ferret (Not usable as of 5.5)</dd>
+ <dt class="sub1">Make Mono Regions</dt><dd>Creates mono regions out of a stereo or multichannel region by splitting it into its discrete channels. The created regions are added to the Editor List</dd>
+ <dt class="sub1">Close Gaps</dt><dd>Extends (or reduces) the selected regions to be perfecltly aligned. Optionnaly, sets up a crossfade duration, or a pull-back (spacing between regions)</dd>
+ <dt class="sub1">Place Transient</dt><dd>Places a transient at the Edit Point. Used e.g. for the <kbd class="menu">Pitch Shift...</kbd> action</dd>
+ <dt class="sub1">Rhythm Ferret...</dt><dd>Opens the <kbd class="menu">Rhythm Ferret</kbd> which is a powerfull tool to sequence audio files</dd>
+ <dt class="sub1">Strip Silence...</dt><dd>Opens the <kbd class="menu">Strip Silence</kbd> window which is a very handy tool to remove all audio under a user-chosen threshold (with a preview)</dd>
+ <dt class="sub1">Reverse</dt><dd>Mirrors the audio horizontally</dd>
+ <dt>Layering</dt>
+ <dt class="sub1">Raise to Top</dt><dd>On overlapping regions, puts the selected one(s) on top</dd>
+ <dt class="sub1">Raise</dt><dd>On overlapping region, makes the selected one(s) one layer higher</dd>
+ <dt class="sub1">Lower</dt><dd>Makes the selected region(s) one layer lower</dd>
+ <dt class="sub1">Lower to Bottom</dt><dd>Sends the selected region to the background</dd>
+ <dt>MIDI</dt>
+ <dt class="sub1">Transpose...</dt><dd>On a MIDI region, shows the <a href="/editing-and-arranging/edit-midi/transpose-midi/"><kbd class="menu">Transpose MIDI</kbd> window</a>, allowing to shift the pitch of the whole MIDI region by ± <em>n</em> semitones or octaves</dd>
+ <dt class="sub1">Insert Patch Change...</dt><dd>Inserts a patch change at the Edit Point, allowing a change of patch, channel, program and/or bank</dd>
+ <dt class="sub1">Quantize...</dt><dd>Shows the <a href="/editing-and-arranging/edit-midi/quantize-midi/"><kbd class="menu">Quantize</kbd> window</a>, allowing to perfectly align the MIDI notes to the musical grid</dd>
+ <dt class="sub1">Legatize</dt><dd>Shortens or elongates the MIDI notes to make them perfectly sequentials, i.e. the end of a note is the start of the following one</dd>
+ <dt class="sub1">Remove Overlap</dt><dd>FIXME Shortens or elongates the MIDI notes to make them perfectly sequentials, i.e. the end of a note is the start of the following one</dd>
+ <dt class="sub1">Transform...</dt><dd><a href="/editing-and-arranging/edit-midi/transformation-midi/"><kbd class="menu">Transform</kbd> window</a>, that allows for mathematical operations on the midi notes</dd>
+ <dt class="sub1">Unlink from Other copies</dt><dd>Makes the selected MIDI region independant, e.g. editing this region won't affect any other one.</dd>
+ <dt class="sub1">List Editor...</dt><dd>Shows the <kbd class="menu">List Editor</kbd> which sequentially lists all the MIDI events in the region, and allows for precise modifications</dd>
+ <dt>Gain</dt>
+ <dt class="sub1">[] Opaque</dt><dd>When checked, makes the region opaque audio-wise, i.e., the underlying regions won't be audible</dd>
+ <dt class="sub1">[] Mute</dt><dd>When checked, mutes <em>only</em> the selected region on the track, without muting the track. The muted regions will have <em>!!</em> prepended to their name and will be semi-transparent</dd>
+ <dt class="sub1">Normalize...</dt><dd>Shows the <kbd class="menu">Normalize region</kbd> dialog, which allows to scale the region level by setting its maximum level, optionaly constraining the RMS</dd>
+ <dt class="sub1">Boost Gain</dt><dd>Increases the gain on the selected region by boosting the audio, without touching the enveloppe or automation</dd>
+ <dt class="sub1">Cut Gain</dt><dd>Reduces the gain without touching the enveloppe or automation</dd>
+ <dt class="sub1">Reset Envelope</dt><dd>If the gain enveloppe has been edited, resets it to its initial value (constant at 0 dB)</dd>
+ <dt class="sub1">[] Envelope Active</dt><dd>When unchecked, disables any enveloppe editing that has been made. The enveloppe will be displayed in yellow instead of green.</dd>
+ <dt>Position</dt>
+ <dt class="sub1">Move to Original Position</dt><dd>Moves the region where it was initially recorded or inserted in the session</dd>
+ <dt class="sub1">Snap Position to Grid</dt><dd>If the Grid Mode is set to <em>Grid</em>, snaps the region to the nearest grid line</dd>
+ <dt class="sub1">[] Lock</dt><dd>Blocks the selected regions at their current positions in time and tracks, avoiding any movement on the timeline. The region name will be surrounded by <em>></em> and <em><</em> brackets</dd>
+ <dt class="sub1">[] Glue to Bars and Beats</dt><dd>Locks the region position to relative to the musical grid, i.e. a change of tempo will move the region to keep it on the same bar/beat</dd>
+ <dt class="sub1">[] Lock to Video</dt><dd>Same as above, relative to the position in the video</dd>
+ <dt class="sub1">Set Sync Position</dt><dd>Creates or move the Sync position, i.e. the point of the region that will be aligned or snapped to the grid, and that is (by default) the beggining of the region.</dd>
+ <dt class="sub1">Remove Sync</dt><dd>Removes any user defined Sync point, and resets the sync position to the beginning of the region</dd>
+ <dt class="sub1">Nudge Later</dt><dd>Moves the region to the right by the amount shown in the <a href="/ardours-interface/the-editor/the-toolbar/the-nudge-controls/">nudge timer</a></dd>
+ <dt class="sub1">Nudge Earlier</dt><dd>Same as above, to the left</dd>
+ <dt class="sub1">Nudge Later by Capture Offset</dt><dd>Moves the region to the right by the capture latency computed by ardour based on the user's settings regarding latency</dd>
+ <dt class="sub1">Nudge Earlier by Capture Offset</dt><dd>Same as above, to the left</dd>
+ <dt class="sub1">Sequence Regions</dt><dd>Puts the selected regions one after the other, so that the end of one region is the beggining of the next one, removing any overlap or silence. The reference point is the earliest region.</dd>
+ <dt>Trim</dt>
+ <dt class="sub1">Trim Start at Edit Point</dt><dd>If the Edit Point is within the region boundaries, shortens the region to align its start with the Edit Point</dd>
+ <dt class="sub1">Trim End at Edit Point</dt><dd>Same as above, for the end of the region</dd>
+ <dt class="sub1">Trim to Loop</dt><dd>Uses both the start and end Loop markers to shorten the region</dd>
+ <dt class="sub1">Trim to Punch</dt><dd>Same as above with the Punch markers</dd>
+ <dt class="sub1">Trim to Previous</dt><dd>On overlapping regions, shortens the selected one so that the previous region is complete, i.e. the new start point for the selected region is the end point of the previous region on the timeline</dd>
+ <dt class="sub1">Trim to Next</dt><dd>Same as above, with the end of the selected region aligned to the start of the following one.</dd>
+ <dt>Ranges</dt>
+ <dt class="sub1">Set Loop Range</dt><dd>Creates a Loop range based on the selected regions, i.e. the strt of the loop range is the start of the earliest region, and the end of the loop is the end of the latest region.</dd>
+ <dt class="sub1">Set Punch</dt><dd>Same as above, for the Punch range</dd>
+ <dt class="sub1">Add Single Range Marker</dt><dd>Same as above, for the Edit range</dd>
+ <dt class="sub1">Add Range Marker Per Region</dt><dd>For each selected region, creates its own Edit range based on the boundaries of each region</dd>
+ <dt class="sub1">Set Range Selection</dt><dd>Creates a range selection based on the boundaries of the selected regions</dd>
+ <dt>Fades</dt>
+ <dt class="sub1">[] Fade In</dt><dd>Activates/desactivates the Fade In at the start of the region</dd>
+ <dt class="sub1">[] Fade Out</dt><dd>Same as above, for the Fade out at the end of the region</dd>
+ <dt class="sub1">[] Fades</dt><dd>Shortcut to activate/desactivate both the fade in and fade out</dd>
+ <dt>Duplicate</dt>
+ <dt class="sub1">Duplicate</dt><dd>Creates a copy of the selected region(s) and happend it to the original</dd>
+ <dt class="sub1">Multi-Duplicate...</dt><dd>Shows the <kbd class="menu">Duplicate</kbd> dialog, allowing to create multiple copies, or a not-integer number of copies (the last one will then be truncated)</dd>
+ <dt class="sub1">Fill Track</dt><dd>Creates duplicates until it fills the session, i.e. reaches the End marker of the session. The last duplicate may be truncated to fit in</dd>
+ <dt>Export...</dt><dd>Shows the <a href="/exporting/export-dialog/"><kbd class="menu">Export</kbd> dialog</a>, with all parameters set to export only the selected region(s)</dd>
+ <dt>Bounce (without processing)</dt><dd>Creates a bounce, i.e. a version of the region with all the edits (boundaries, enveloppe), as a new region in the Editor List, without any of the effects of the mixer strip</dd>
+ <dt>Bounce (with processing)</dt><dd>Same as above, <em>with</em> the effects of the mixer strip</dd>
+
+ <dt>Remove</dt><dd>Deletes the region from the edit (no file is harmed in the process, and the region stays in the Editor for later use)</dd>
+</dl>
-<p>If you use a newer version of JACK 1, just make sure the -X
-alsa_midi or -X seq options are enabled for whatever technique you use
-to start JACK.
-</p>
+---
+title: The Track Menu
+part: subchapter
+---
<p>
-For other versions of JACK,
-add <kbd class="input">a2jmidid -e &</kbd> as an "after start-up" script
-in the <kbd class="menu">Setup > Options</kbd> tab of QJackCtl, so
-that it is started automatically whenever you start JACK.
+ The <kbd class="menu">Track</kbd> menu is where one can deal with the tracks, busses and control masters.
</p>
-<p class="fixme">Is this true anymore in Ardour 5? This section may have been relevant in Ardour 3, but it might not be relevant anymore.</p>
+<dl>
+ <dt>Add Track, Bus or VCA...</dt><dd>Shows the <a href="/working-with-tracks/adding-tracks-and-busses/"><kbd class="menu">Add Track, Bus or VCA...</kbd> window</a>, where one can add one or more tracks, busses or control masters to the session and define its parameters</dd>
+ <dt>Duplicate Tracks/Busses...</dt><dd>Shows the <kbd class="menu">Duplicate Tracks and Busses</kbd> window, allowing to duplicate the selected track(s) and optionnaly, its playlist</dd>
+
+ <dt>Toggle Record Enable</dt><dd>Sets the Record Enable mode On on the selected track(s). These tracks will record audio/midi next time the global record is active and playback is started.</dd>
+ <dt>Toggle Solo</dt><dd>Sets the solo On on the selected tracks, so only these tracks will play</dd>
+ <dt>Toggle Mute</dt><dd>Mutes the selected tracks, they wont play until unmuted</dd>
+
+ <dt>Insert Time</dt><dd>Shows the <kbd class="menu">Insert Time</kbd> window, allowing to insert a blank time in the selected tracks' playlist. By default, it'll be inserted at the Edit Point, but that can be changed in the dialog, as does the behaviour of the regions</dd>
+ <dt>Remove Time</dt><dd>Same as above, but to remove time</dd>
+ <dt>Move Selected Tracks Up</dt><dd>Changes the position of the selected tracks one track up towards the top. In the mixer, the tracks will be moved to the left.</dd>
+ <dt>Move Selected Tracks Down</dt><dd>Same as above, towards the bottom</dd>
+ <dt>Height</dt>
+ <dt class="sub1">Fit Selection (Vertical)</dt><dd>Will fit the selected track(s) in the window. If too many tracks are selected, they'll be reduced to their minimum height.</dd>
+ <dt class="sub1">Largest</dt><dd>Sets the selected tracks height to a very high value, hence making the tracks wide on screen</dd>
+ <dt class="sub1">Larger</dt><dd>Same as above, but a little less high</dd>
+ <dt class="sub1">Large</dt><dd>Same as above, but again less high</dd>
+ <dt class="sub1">Normal</dt><dd>Sets the height of the track to its default value which is a trade-off between readability and number of tracks displayed</dd>
+ <dt class="sub1">Small</dt><dd>Reduces the size of the tracks to a low value, increasing the number of on screen tracks</dd>
+
+ <dt>Toggle Active</dt><dd>Toggles the active state of a track. An inactive track will be grayed and wont play any sound. That can be seen in the <kbd class="menu">A</kbd> colomn of the <a href="/ardours-interface/the-editor/the-editor_s-lists/tracks-and-busses-list/">Tracks and Busses List</a></dd>
+ <dt>Remove</dt><dd>Deletes this track and its playlist (no file is harmed in the process, and the regions from the playlist stay in the Editor for later use)</dd>
+</dl>
---
-title: MIDI on OS X
+title: The View Menu
part: subchapter
---
<p>
- In order for CoreMIDI to work with Jack MIDI, a CoreMIDI-to-JACK-MIDI
- <dfn>bridge</dfn>
- is required. This feature is available on versions equal to or great than
- version 0.89 of JackOSX.
+ The <dfn>View</dfn> menu sets how the session is seen, and what's visible or not.
</p>
-<h2>Routing MIDI</h2>
-
-<h3>Inside Ardour</h3>
-
-<p>
- MIDI ports show up in Ardour's MIDI connection matrix in multiple
- locations. Bridged CoreMIDI ports as well as JACK MIDI ports that have
- been created by other software clients will show up under the "Other" tab.
- Bridged CoreMIDI hardware ports show up under the "Hardware" tab.
-</p>
+<dl>
+ <dt>[] Maximise Editor Space</dt><dd>Puts the Editor window in full screen mode</dd>
+ <dt>[] Maximize Mixer Space</dt><dd>Puts the Mixer window in full screen mode</dd>
+
+ <dt>Primary Clock</dt>
+ <dt class="sub1">Focus On Clock</dt><dd>Sets the focus on the <a href="/ardours-interface/transport-bar-and-times/times/">main clock</a>, allowing to type in numbers directly to change the playhead position</dd>
+ <dt class="sub1">Timecode</dt><dd>Sets the main clock in timecode mode, so it displays time in the Hours:Minutes:Seconds:Frames format</dd>
+ <dt class="sub1">Bars & Beats</dt><dd>Sets the main clock in musical time mode, so it displays time in the Bars:Beats:Ticks format</dd>
+ <dt class="sub1">Minutes & Seconds</dt><dd>Sets the main clock in absolute time mode, so it displays time in the Hours:Minutes:Seconds.Milliseconds format</dd>
+ <dt class="sub1">Samples</dt><dd>Sets the main clock in samples time mode, so the time is displayed in samples from the absolute start</dd>
+ <dt>Secondary Clock</dt>
+ <dt class="sub1">Timecode</dt><dd>Same as for the main clock (see above)</dd>
+ <dt class="sub1">Bars & Beats</dt><dd>Same as for the main clock</dd>
+ <dt class="sub1">Minutes & Seconds</dt><dd>Same as for the main clock</dd>
+ <dt class="sub1">Samples</dt><dd>Same as for the main clock</dd>
+
+ <dt>Zoom</dt>
+ <dt class="sub1">Zoom In</dt><dd>Zooms in, focusing the <em>Zoom Focus</em> (see bellow)</dd>
+ <dt class="sub1">Zoom Out</dt><dd>Zooms out</dd>
+ <dt class="sub1">Zoom to Session</dt><dd>Adjust the zoom value so that all the session (as defined by its start and end markers) fit in the window</dd>
+ <dt class="sub1">Zoom to Selection</dt><dd>Adjust the zoom value so that all the selected regions fit in the window</dd>
+ <dt class="sub1">Fit Selection (Vertical)</dt><dd>Fits the selected track(s) in the window. If too many tracks are selected, they'll be reduced to their minimum height.</dd>
+ <dt class="sub1">Toggle Zoom State</dt><dd>Reverts to last zoom state (kind of "undo" for zoom, even if edits have been made inbetween)</dd>
+ <dt class="sub1">Expand Track Height</dt><dd>Increases the height of the selected tracks. If no track is selected, then all the tracks are expanded</dd>
+ <dt class="sub1">Shrink Track Height</dt><dd>Same as above, but reduces the height of the tracks</dd>
+ <dt>Zoom Focus</dt>
+ <dt class="sub1">Zoom Focus Left</dt><dd>Sets the screen's left side as the zoom target, i.e. when zooming in, the left side of the screen will stay at the same place in the timeline</dd>
+ <dt class="sub1">Zoom Focus Right</dt><dd>Same, with the right of the screen</dd>
+ <dt class="sub1">Zoom Focus Center</dt><dd>Same, with the center of the screen</dd>
+ <dt class="sub1">Zoom Focus Playhead</dt><dd>Sets the playhead as the focus point of the zoom, i.e. the point in time that will stay fixed</dd>
+ <dt class="sub1">Zoom Focus Mouse</dt><dd>Same as above, with the mouse pointer</dd>
+ <dt class="sub1">Zoom Focus Edit Point</dt><dd>Same as above, with the Edit Point</dd>
+ <dt class="sub1">Next Zoom Focus</dt><dd>Circles between the previous modes</dd>
+ <dt>Rulers</dt>
+ <dt class="sub1">[] Min:Sec</dt><dd>Showss (when checked) or hides a line in <a href="/ardours-interface/the-editor/the-ruler/">the Ruler</a> with the time formatted as Hours:Minutes:Seconds.Milliseconds</dd>
+ <dt class="sub1">[] Timecode</dt><dd>Same as above, with the time formatted as Hours:Minutes:Seconds:Frames</dd>
+ <dt class="sub1">[] Samples</dt><dd>Same as the above, with the time displayed in samples from the absolute start</dd>
+ <dt class="sub1">[] Bars & Beats</dt><dd>Same as the above, with the time formatted as Bars:Beats:Ticks</dd>
+
+ <dt class="sub1">[] Meter</dt><dd>Shows / hides the Meter line in the ruler, where the signature can be adjusted along the playline</dd>
+ <dt class="sub1">[] Tempo</dt><dd>Shows / hides the Tempo line, where the BPM can be changed with markers</dd>
+ <dt class="sub1">[] Ranges</dt><dd>Shows / hides the Range line, where ranges can be defined</dd>
+ <dt class="sub1">[] Loop/Punch</dt><dd>Shows / hides the Loop/Punch line, where loops and Punches can be defined</dd>
+ <dt class="sub1">[] CD Markers</dt><dd>Shows / hides the Range line, where CD Markers can be defined</dd>
+ <dt class="sub1">[] Markers</dt><dd>Shows / hides the Markers line, where custom markers can be defined</dd>
+
+ <dt class="sub1">[] Video</dt><dd>Shows / hides the Video timeline, where frames of the video are shown for syncing purposes</dd>
+ <dt>Video Monitor</dt>
+ <dt class="sub1">Original Size</dt><dd>When the <a href="/video-timeline/">Video Monitor</a> is active, resets its size to the original size, i.e. 1 pixel in the video is 1 pixel on screen</dd>
+ <dt class="sub1">[] Letterbox</dt><dd>When checked, forces the ratio (width/height) to be the one of the original video. If unched, the video will be stretched to fit the window</dd>
+
+ <dt class="sub1">[] Always on Top</dt><dd>Stays above all other windows, enabling to work in Ardour without the video windows to be hidden in the background</dd>
+ <dt class="sub1">[] Fullscreen</dt><dd>Sets the Xjadeo window to be fullscreen. Can be usefull in a dual monitor setup</dd>
+
+ <dt class="sub1">[] Timecode</dt><dd>When checked, displays a Timecode over the video, in the Hours:Minutes:Seconds:Frames format</dd>
+ <dt class="sub1">[] Frame number</dt><dd>When checked, shows the absolute frame number inside the video, i.e. this image is the <em>n</em>th of the video</dd>
+ <dt class="sub1">[] Timecode Background</dt><dd>Adds a black background to the timecode for readability</dd>
+ <dt>Scroll</dt>
+ <dt class="sub1">Scroll Tracks Down</dt><dd>Scrolls the view toward the bottom of the session from one screen (vertically, so along tracks)</dd>
+ <dt class="sub1">Scroll Tracks Up</dt><dd>Same as above, towards the top</dd>
+ <dt class="sub1">Scroll Forward</dt><dd>Scrolls the view toward the right of the session from one screen (horizontally, so along time)</dd>
+ <dt class="sub1">Scroll Backward</dt><dd>Same as above, to the left</dd>
+ <dt>Views</dt>
+ <dt class="sub1">Save View <em>n</em></dt><dd>Saves the position on the timeline in the memory, horizontally and vertically (along time and tracks)</dd>
+ <dt class="sub1">Go to View <em>n</em></dt><dd>Loads and displays a saved position (see above)</dd>
+
+ <dt>[] Show Editor Mixer</dt><dd>When checked, the selected tracks' mixer strip is displayed on the left of the editor window, allowing for a quick access to e.g. efffects and routing</dd>
+ <dt>[] Show Editor List</dt><dd>In the Editor window, shows the <a href="/ardours-interface/the-editor/the-editor_s-lists/">Editor List</a>, giving access to a number of handy lists (regions, tracks, ...)</dd>
+ <dt>[] Toggle Mixer List</dt><dd>In the Mixer view, shows the Mixer list, giving access to some handy lists (<a href="/ardours-interface/the-mixer/favorite-plugins-window/">Favorite plugins</a>, <a href="/ardours-interface/the-mixer/the-strips-list/">The Strip list</a>,...)</dd>
+ <dt>[] Toggle Monitor Section Visibility</dt><dd>If the <kbd class="option">Use monitoring section on this session</kbd> has been checked in the <a href="/preferences-and-session-properties/session-properties-dialog/monitoring/">Session Properties window</a>, shows pr hide the Monitor Section in the Mixer</dd>
+ <dt>[] Show Measure Lines</dt><dd>If checked, in the Editor, shows a vertical white lines at each measure start</dd>
+ <dt>[] Show Summary</dt><dd>If checked, in the Editor, shows the <a href="/ardours-interface/the-editor/the-summary/">Summary</a>, allowing a faste navigation in the session</dd>
+ <dt>[] Show Group Tabs</dt><dd>If checked, makes the groups visible as tabs on the left in the Editor, and on the top in the mixer</dd>
+ <dt>[] Show Marker Lines</dt><dd>If checked, each marker is extended across all the tracks in the editor with a line of the same color</dd>
+</dl>
-<h3>External Applications</h3>
+---
+title: The Window Menu
+part: subchapter
+---
<p>
- There are multiple options for connecting MIDI ports outside of Ardour.
+ The <dfn>Window</dfn> menu deals with the layout of the different windows, and their visibility.
</p>
-<ul>
- <li><a href="http://www.snoize.com/MIDIMonitor/">MIDI Monitor</a> is a handy
- tool for doing various MIDI-related tasks.</li>
- <li><a href="http://notahat.com/midi_patchbay">MIDI Patchbay</a> lets you
- connect ports and filters MIDI data.</li>
-</ul>
-
-
-
-
----
-title: Ardour's Interface
-part: part
----
-
+<dl>
+ <dt>[] Audio/MIDI Setup</dt><dd>Shows the <a href="/working-with-sessions/new-session-dialog/"><kbd class="menu">Audio/MIDI Setup</kbd> window</a>, where the sound system configuration can be modified</dd>
+
+ <dt>Editor</dt>
+ <dt class="sub1">Show</dt><dd>Switches to the Editor view</dd>
+ <dt class="sub1">Hide</dt><dd>Hides the Editor, hence showing the Mixer when the windows are attached</dd>
+ <dt class="sub1">Attach</dt><dd>If the Editor window is detached, separated from the main window, attach it back</dd>
+ <dt class="sub1">Detach</dt><dd>If the Editor is attached to the main window, fetach it (makes the Editor a separated window, usefull for multi-monitor setup)</dd>
+ <dt>Mixer</dt>
+ <dt class="sub1">Show/Hide/Attach/Detach</dt><dd>Same as for the Editor, for the <em>Mixer</em> window</dd>
+ <dt>Preferences</dt><dd></dd>
+ <dt class="sub1">Show/Hide/Attach/Detach</dt><dd>Same as for the Editor, for the <em>Preferences</em> window</dd>
+ <dt>Meterbridge</dt><dd>Shows the <a href="/meters/"><kbd class="menu">Meterbridge</kbd> window</a>, that displays all the tracks' meter at once and their recording status, and is very handy for multitrack recording</dd>
+ <dt>Scripting</dt><dd>Opens the <a href="/lua-scripting/"><kbd class="menu">Lua Scripting</kbd> window</a>, allowing to edit and run Lua scripts</dd>
+
+ <dt>[] Tracks and Busses</dt><dd>Opens the <kbd class="menu">Tracks and Busses</kbd> window, which is a shortcut to many tracks/busses operations (routing, effects, ...)</dd>
+ <dt>[] Locations</dt><dd><dd>Opens the <a href="/ardours-interface/the-editor/the-editor_s-lists/ranges-and-marks-list/"><kbd class="menu">Ranges and Marks</kbd> window</a>, a single point of control for all range and location markers</dd>
+ <dt>[] Binding Editor</dt><dd>Opens the <a href="/default-keyboard-bindings/"><kbd class="menu">Key Bindings</kbd> window</a>, which allows for easy creation or modification of any keyboard shortcut</dd>
+ <dt>[] Bundle Manager</dt><dd>Opens the <kbd class="menu">Bundle Manager</kbd> window, allowing to create and manage <em>Bundles</em>, which are a way to simplify connection management, by defining groups of ports</dd>
+ <dt>[] Big Clock</dt><dd>Opens the <a href="/ardours-interface/transport-bar-and-times/times/">Main Clock</a> as its own separate (and huge) window, which is helpfull when recording</dd>
+
+ <dt>[] Video Monitor</dt><dd>If a <a href="/video-timeline/">video</a> has been imported in the session, opens a video window (namely, <em>Xjadeo</em>), synced to the timeline</dd>
+
+ <dt>Midi Tracer</dt><dd>Opens the <kbd class="menu">MIDI Tracer</kbd> window, allowing to follow each and every MIDI message entering or leaving Ardour</dd>
+ <dt>[] Audio Connections</dt><dd>Opens the <a href="/signal-routing/Patchbay/"><kbd class="menu">Audio Connection Manager</kbd> window</a>, a way to make connections to, from and within Ardour's mixer</dd>
+ <dt>[] MIDI Connections</dt><dd>Same as above, for the MIDI connections</dd>
+ <dt>[] Log</dt><dd>Shows the <kbd class="menu">Log</kbd> window, where Ardour lists usefull information, warnings and errors</dd>
+</dl>
---
-title: About Ardour's Interface
-part: chapter
+title: The Help Menu
+part: subchapter
---
<p>
- In Ardour, you work in two main windows: the <dfn>Editor</dfn> and the
- <dfn>Mixer</dfn>.
+ The <dfn>Help</dfn> Menu gives acces to useful information about Ardour.
</p>
-<figure>
- <img src="/images/editor_split.png" alt="Ardour's mixer window">
- <img src="/images/mixer_split.png" alt="Ardour's editor window">
- <figcaption>
- <ol class="multicol4">
- <li>Main menu</li>
- <li>Status bar</li>
- <li>Transport bar & Times</li>
-</ol><ol class="multicol4" start="4">
- <li>Mode switch</li>
- <li>The <dfn>Editor</dfn> window</li>
- <li>a track's mixer strip</li>
-</ol><ol class="multicol4" start="7">
- <li>Editors List</li>
- <li>The <dfn>Mixer</dfn> window</li>
- <li>Favorite plugins</li>
-</ol><ol class="multicol4" start="10">
- <li>Strips list</li>
- <li>Group list</li>
- <li>Master strip</li>
- </ol>
- </figcaption>
-</figure>
-<p>
- To switch between those windows, use the buttons (#4 Mode switch in the upper right),
- the shortcut <kbd class="mod2">M</kbd>, or the menu
- <kbd class="menu">Window > Editor <em>(or Mixer)</em> > Show</kbd>.
- Both windows can be visible at the same time (eg. for a multi-monitor
- setup) using <kbd class="menu">Detach</kbd> in the same menu.</p>
-
----
-title: Main Menu
-part: chapter
----
-
-<p class="fixme">Add content</p>
+<dl>
+ <dt>[] About</dt><dd>Shows the <kbd class="menu">About Ardour</kbd> window, which contains information about the version, config, authors,and license of Ardour</dd>
+ <dt>Chat</dt><dd>This is a shortcut to the webchat version of the Freenode IRC channel of Ardour, where the developpers meet, and questions can be asked if the Manual is not enough</dd>
+ <dt>Manual</dt><dd>Link to a FLOSSManual guide to Ardour</dd>
+ <dt>Reference</dt><dd>Link to this manual, hosted on ardour.org</dd>
+ <dt>User Forums</dt><dd>Link to ardour.org's user forum</dd>
+ <dt>How to Report a Bug</dt><dd>Link to an helping page about reporting bugs</dd>
+ <dt>Report a Bug</dt><dd>Link to Ardour's Mantis bugtracker</dd>
+ <dt>Ardour Website</dt><dd>Link to Ardour's main and official website</dd>
+ <dt>Ardour Development</dt><dd>Link to the developpers' part of the official website</dd>
+</dl>
---
---
<img src="/images/status-bar.png" alt="The status bar">
+
<p>The status bar is an informative bar at the top of the window, showing:</p>
+
<ul>
<li><dfn>File:</dfn> the file format used in the session, including when recording</li>
<li><dfn>TC:</dfn> is the timecode, i.e. the number of frames per second used by the session (for videos)</li>
<li><dfn>a Log button</dfn> that indicates if Ardour has encountered any warning or error.</li>
</ul>
-<p>The buffers are labelled as <kbd class="menu">p</kbd> for playback and <kbd class="menu">c</kbd> for capture. If the
+<p>The buffers are labeled as <kbd class="menu">p</kbd> for playback and <kbd class="menu">c</kbd> for capture. If the
system is fast enough, these buffers should be 100% full at all times, showing the system has time to precompute
all the data before delivering it to the audio system. A buffer constantly under 20% is a sign of an underpowered
computer system or of too much processing.</p>
<p>An Xrun (short for buffer over- or under-run) happens when the system has been forced to skip audio frames, e.g. if the latency
asked is too short for the computing power of the machine. It usually results in clicks, pops and crackles if it happens while recording.</p>
-<p>The log button turns yellow when a warning is shows, and red when an error occurs. Clicking the log button gives acces to the log.</p>
+<p>The log button turns yellow when a warning occurs, and red when an error occurs. Clicking the log button gives acces to the log.</p>
---
title: Transport bar and times
</p>
<ul>
- <li><a href="/controlling-playback/using-the-transport-bar/">the Transport Controls</a></li>
- <li><a href="/ardours-interface/using-ardour-clock-displays/">the Clocks</a></li>
+ <li>the Transport Controls</li>
+ <li>the Clocks</li>
<li>3 status indicators:
<ul>
<li><dfn>Solo</dfn>: Blinks when one or more tracks are being soloed, see <a href="/mixing/muting-and-soloing/">Muting and Soloing</a>. Clicking this button disables any active explicit and implicit solo on all tracks and busses.</li>
<li><dfn>Audition</dfn>: Blinks when 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="/ardours-interface/meters/">Metering in Ardour</a></li>
+ <li>A global Meter, showing the level of the Master Output, see <a href="/introducing-ardour/meters/">Metering in Ardour</a></li>
<li>the Mode Selector, allowing to switch between Editor and Mixer views, or edit the Preferences.</li>
</ul>
<dfn>Play Loop Range</dfn>: Repeats the defined <a href="/controlling-playback/looping-the-transport/">loop</a> as defined by the <a href="/working-with-markers/loop-range/">Loop range</a>, until the "Stop playback" button is pressed. Clicking the "Play loop Range" button while already active switches to normal Play mode, which exits the loop without stopping and restarting playback.
</li>
<li>
- <dfn>Play Range/Selection</dfn>: If a range has been defined using the Range Mode button, plays the range, of if an audio or MIDI region is selected, plays this region. In both cases, the playback stops at the end of the range or selected region.
+ <dfn>Play Range/Selection</dfn>: If a range has been defined using the Range Mode button, plays the range; or if an audio or MIDI region is selected, plays this region. In both cases, the playback stops at the end of the range or selected region.
</li>
<li>
<dfn>Play from playhead</dfn>: Starts the playback and optionally record (more below).
</p>
<p>
- The Shuttle Speed Control supports 2 operating modes, that can be chosen with right click > Mode:
+ The Shuttle Speed Control supports 2 operating modes, that can be chosen with right click > Mode:
</p>
<ul>
<p>
<p>
- The 3 vertical buttons on the right of the transport bar control the behaviour of the playhead:
+ The 3 vertical buttons on the right of the transport bar control the behavior of the playhead:
</p>
<ul>
</li>
</ul>
+<h2>Using Key Bindings</h2>
+
+<p>
+ Ardour has many available commands for playback control that can be bound
+ to keys. Many of them have default bindings, some do not, so the list below
+ shows both the default bindings and internal command names for some of them.
+</p>
+
+<dl class="wide-table">
+ <dt><kbd>Space</kbd></dt>
+ <dd>switch between playback and stop.</dd>
+ <dt><kbd>Home</kbd></dt>
+ <dd>Move playhead to session start marker</dd>
+ <dt><kbd>End</kbd></dt>
+ <dd>Move playhead to session end marker</dd>
+ <dt><kbd>→</kbd></dt>
+ <dd>Playhead to next region boundary</dd>
+ <dt><kbd>←</kbd></dt>
+ <dd>Playhead to previous region boundary</dd>
+ <dt><kbd>0</kbd></dt>
+ <dd>Move playhead to start of the timeline</dd>
+</dl>
+
+<p>
+ Go to the <kdb class="menu">Transport</kbd> and <kdb class="menu">Transport >> Playhead</kbd> to find more.
+</p>
+
---
title: Times
part: subchapter
---
<p>
- <dfn>Clocks</dfn> in Ardour are used to display <dfn>time values</dfn> precisely.
- In many cases, they are also one way to edit (change) time values, and in a few
- cases, the only way. All clocks share the same basic appearance and functionality,
- which is described below, but a few clocks serve particularly important roles.
+ <dfn>Clocks</dfn> in Ardour are used to display <dfn>time values</dfn> precisely. In many cases, they are also one way to edit (change) time values, and in a few cases, the only way. All clocks share the same basic appearance and functionality, which is described below, but a few clocks serve particularly important roles.
</p>
<h2>Transport Clocks</h2>
</p>
<h3>The Big Clock</h3>
+
<p>
To show the current playhead position in a big, resizable window, activate
<kbd class="menu">Window > Big Clock</kbd>. The big clock is very useful
large big clock window filling a good part of the display, and on the right,
the same clock during active recording.
</p>
+
<a href="/images/bigclock.png"><img src="/images/bigclock.png" height="100" alt="an image of the big clock filling a screen" /></a>Â <a href="/images/bigclock-recording.png"><img src="/images/bigclock-recording.png" height="100" alt="an image of the big clock while recording"
/></a>
<h3>The Special Role of the Secondary Transport Clock</h3>
+
<p>
On a few occasions Ardour needs to display time values to the user, but there
is no obvious way to specify what units to use. The most common case is the big
cursor that appears when dragging regions. For this and other similar cases,
Ardour will display time using the same units as the secondary clock.
</p>
+
<h4>Why are there two transport clocks?</h4>
+
<p>
Having two transport clocks lets you see the playhead position in two different
time units without having to change any settings. For example, you can see the
</p>
<h3>Selection and Punch Clocks</h3>
+
<p>
The transport bar also contains a set of 5 clocks that show the current
<dfn>selection range</dfn> and <dfn>punch ranges</dfn>. Clicking on the punch
<img src="/images/selectionpunchclocks.png" alt="An image of the the selection and punch clocks in Ardour 3" />
<h2>Clock Modes</h2>
+
<p>
Every clock in Ardour has four different, selectable <dfn>clock
modes</dfn>. Each mode displays time using different units.
part: chapter
---
+<figure>
+ <img src="/images/detailed-editor-window.png" alt="Ardour's editor windo
+w">
+ <figcaption>
+ <ol class="multicol4">
+ <li>Toolbar</li>
+ <li>Rulers</li>
+</ol><ol class="multicol4" start="3">
+ <li>Editor's List</li>
+ <li>a Mixer strip</li>
+</ol><ol class="multicol4" start="5">
+ <li>Summary</li>
+ <li>an audio track</li>
+ </ol>
+</ol><ol class="multicol4" start="7">
+ <li>a MIDI track</li>
+ <li>automation</li>
+ </ol>
+ </figcaption>
+</figure>
+
<p>
The <dfn>Editor</dfn> window includes the editor track <dfn>canvas</dfn>
where you can arrange audio and MIDI data along a timeline. This is the
window you will be in while editing and arranging a project. The window
has a general "horizontal" sense to it: the timeline flows from left to
right, the playhead showing the current position in the session moves
- from left to right — the window really represents <dfn>time</dfn>
+ from left to right—the window really represents <dfn>time</dfn>
in a fairly literal way.
</p>
It is possible to show a single channel strip in the editor window, and
some people find this enough to work on mixing without actually opening
the mixer window. Most of the time though, you will want both of these
- windows at various stages of a session's lifetime — sometimes
+ windows at various stages of a session's lifetime—sometimes
you'll be focused on editing, sometimes on mixing and possibly some of
the time on both.
</p>
</ol><ol class="multicol5" start="4">
<li>Edit Point</li>
</ol><ol class="multicol5" start="5">
- <li>Nudge</li>
+ <li>Nudge</li>
</ol>
</figcaption>
</figure>
<p>
- The Toolbar is made of 5 "zones"
-</p
+ The Toolbar is made of 5 parts, described in this part.
+</p>
---
-title: The Toolbar
+title: The Toolbox
part: subchapter
---
-<img src="/images/toolbar-tools.png" alt="Editor toolbar's tools">
+<img src="/images/toolbar-tools.png" alt="Editor toolbar's tools, aka toolbox">
<h2>Global Edit mode</h2>
On a MIDI region, it allows to lasso-select multiple notes at a time.</dd>
</dl>
-
-
<p class="fixme">Make sure the Internal Edit and Draw tool act as described</p>
-
---
title: the Zoom Controls
part: subchapter
you are going to use any of the Region grid units.
</p>
-
---
title: the Edit Point Control
part: subchapter
---
-title: the Nudge Controls
+title: The Nudge Controls
part: subchapter
---
<img class="left" src="/images/toolbar-nudge.png" alt="Editor toolbar's Nudge">
<p>
- The <dfn>nudge controls</dfn> will move the selected region(s) by a fixed amount
- of time. The left and right buttons move either backward or forward in time, and the small
- clock to the left of these buttons sets the amount of time to nudge by.
- As with all other clocks, you can right-click on the clock to choose the
- time representation you want to use.
+ The <dfn>nudge controls</dfn> will move the selected region(s) by a fixed amount of time. The left and right buttons move either backward or forward in time, and the small clock to the left of these buttons sets the amount of time to nudge by. As with all other clocks, you can right-click on the clock to choose the time representation you want to use.
+</p>
+
+<p>
+ If there are no selected objects, the nudge controls can be used to move the playhead backward or forward by the amount shown on the clock.
+</p>
+
+---
+title: The Ruler
+part: subchapter
+---
+
+<img src="/images/ruler.png" alt="Ardour's Ruler">
+
+<p>
+ The <dfn>Ruler</dfn> scales the session along time, allows navigating, and can be marked for different uses. The main use of the Ruler is to move the playhead: clicking anywhere on the timeline will bring the playhead at this location in time.
</p>
<p>
- If there are no selected objects, the nudge controls can be
- used to move the playhead backward or forward by the amount shown on the clock.
+ It is made of a succession of rows, each having a special role related to time.From top to bottom, those rows are :
</p>
+<dl>
+ <dt><dfn>Timecode</dfn></dt><dd>scaling the session whith the traditional Hours:Mins:Secs:Frames notation</dd>
+ <dt><dfn>Bars:Beats</dfn></dt><dd>slicing the time according to the time signature ot the Meter</dd>
+ <dt><dfn>Meter</dfb></dt><dd>shows the time signature. It can be changed along the timeline, by <kbd class="mouse">Right click</kbd> > <kbd class="menu">New Meter</kbd>. The Bars:Beats ruler will reflect the change.</dd>
+ <dt><dfn>Tempo</dfn></dt><dd>shows the BPM. It can be changed along the timeline, by <kbd class="mouse">Right click</kbd> > <kbd class="menu">New Tempo</kbd>. The Bars:Beats ruler will reflect the change.</dd>
+ <dt><dfn>Range Markers</dfn></dt><dd>allow to create and modify ranges directly on the Ruler.</dd>
+ <dt><dfn>Loop/Punch Ranges</dfn></dt><dd>are special kind of ranges designed to be played as a loop and to do punch recording, i.e. recording on a precise section of time, respectively.</dd>
+ <dt><dfn>CD Markers</dfn></dt><dd>are markers designed to be used while creating a recording that has to be split in time, as an audio CD</dd>
+ <dt><dfn>Location Markers</dfn></dt><dd>is meant to receive any kind of marker, user generated or from Ardour itself.</dd>
+</dl>
+
+<p>
+ Most of the operations on the markers are described in <a href="/working-with-markers/">Working with Markers</a>, while the Meter, Tempo, Bars:Beats and Timecode use are described in <a href="/tempo-meter/tempo-and-meter/">Tempo and Meter</a>.
+</p>
---
vary the width of the list.
</p>
-
---
title: Region List
part: subchapter
</p>
---
-title: Tracks & Busses List
+title: Tracks and Busses List
part: subchapter
---
<dt id="solo-isolated">SI</dt>
<dd>track solo-isolated state.</dd>
<dt id="solo-safe">SS</dt>
- <dd>solo safe state. </dd>
+ <dd>solo safe state.</dd>
</dl>
<p class="note">
</p>
---
-title: Track & Bus Group List
+title: Track and Bus Group List
part: subchapter
---
<dt>Sel</dt>
<dd>whether the constituents are selected together.</dd>
<dt>A</dt>
- <dd>whether the constituents share active status. </dd>
+ <dd>whether the constituents share active status.</dd>
</dl>
---
-title: Ranges & Marks List
+title: Ranges and Marks List
part: subchapter
---
<p>
- The <dfn>Ranges & Marks List</dfn> is a tab in the <dfn>Editor
- Lists</dfn> area on the right of the Editor window. If the editor
- list area isn't visible it can be enabled by checking
- <kbd class="option">View > Show Editor List</kbd>.
- The Ranges & Marks list can be used as a single point
- of control for all range and location markers (including the punch and
- loop ranges), or as a supplement to other methods of working with them.
+ The <dfn>Ranges & Marks List</dfn> is a tab in the <dfn>Editor Lists</dfn> area on the right of the Editor window. If the editor list area isn't visible it can be enabled by checking <kbd class="option">View > Show Editor List</kbd>. The Ranges & Marks list can be used as a single point of control for all range and location markers (including the punch and loop ranges), or as a supplement to other methods of working with them.
</p>
<h2>Common elements</h2>
changing of the display between Timecode, Bars:Beats, Minutes:Seconds,
and Samples.<br />
</p>
+
<p>
The <kbd class="menu">—</kbd> (subtract) button in front of each
user-defined range or marker in the list allows that particular item to
be removed. The name fields of custom ranges and markers can be edited.
</p>
+
<p>
The <kbd class="option">Hide</kbd> checkboxes make markers and ranges invisible
on the respective ruler to reduce visual clutter; the markers remain
than the absolute time. This will make the respective marker follow
changes in the tempo map.
</p>
+
<p>
At the bottom of the list are buttons to add new markers or ranges.
</p>
that may contain audio data between tracks.</dd>
</dl>
+---
+title: The Summary
+part: subchapter
+---
+<img src="/images/summary.png" alt="Ardour's Summary">
+<p>
+ The <dfn>Summary</dfn> is a global overview of the session, allowing for a good "bird's eye" view of where in time and tracks the work happens.
+</p>
+<p>
+ Each horizontal line represents a track in the session, with the colored bars being the audio and MIDI regions, colored as per their track's color setting.
+</p>
+<p>
+ Two yellow vertical lines show the position of the <em>Start</em> and <em>End</em> markers, defining the session's length. The red line shows the playhead's position.
+</p>
+<p>
+ The transparent white rectangle represents what's actually displayed in the Editor window, i.e. what part of the session is being looked at on screen.
+</p>
+<p>
+ The Summary also doubles as a navigator:
+</p>
-
-
-
-
-
-
-
-
-
-
-
-
-
+<ul>
+ <li>the arrows on the left allow to scroll the view horizontally, by 1 length of the veiw each time</li>
+ <li>the arrows on the right allow to scroll vertically, by 1 track each time</li>
+ <li>the white rectangle can be dragged anywhere on the session, moving the view accordingly</li>
+ <li>each border and corner of the white square can be resized, changing the view accordingly</li>
+</ul>
---
part: chapter
---
+<figure>
+ <img src="/images/detailed-mixer-window.png" alt="Ardour's mixer window">
+ <figcaption>
+ <ol class="multicol3">
+ <li>Favorite Plugins</li>
+ <li>Strip List</li>
+</ol><ol class="multicol3" start="3">
+ <li>Group list</li>
+ <li>a track's strip</li>
+</ol><ol class="multicol3" start="5">
+ <li>Master strip</li>
+ <li>Monitor section</li>
+ </ol>
+ </figcaption>
+</figure>
+
+<p>
+ The <dfn>Mixer</dfn> window on the other hand represents signal flow and is the window you will probably be using most when mixing a session. It includes <dfn>channel strips</dfn> for each track and bus in your session. It has a general "vertical" sense to it: signals flow from the top of each channel strip through the processing elements in the strip to reach the output listed at the bottom.
+</p>
+
<p>
- The <dfn>Mixer</dfn> window on the other hand represents signal flow and
- is the window you will probably be using most when mixing a session. It
- includes <dfn>channel strips</dfn> for each track and bus in your session.
- It has a general "vertical" sense to it: signals flow from the top of each
- channel strip through the processing elements in the strip to reach the
- output listed at the bottom.
+ This section describes the Mixer. To learn more about the process of mixing, see <a href="/mixing/">Mixing<a>.
</p>
-
-
---
title: The Mixer - Favorite Plugins Window
part: subchapter
When favorites are added with the <a href="/working-with-plugins/plugin-manager">Plugin Manager</a>, they are appended to the bottom of the list.
</p>
-
-
---
title: The Mixer - The Strips list
part: subchapter
---
-<p class="fixme">add content</p>
+<p>
+ The <dfn>Strips List</dfn> is a quick way to manage big sessions, with lots of tracks, where the mixer would otherwise be too crowded.
+</p>
+
+<p>
+ It is a list of all the tracks, busses and VCA in the session, with a tick to allow for hiding or showing them. This visibility status also affects the Editor view, and is exactly the same as toggling the <kbd class="option">V</kbd> checkbox in the <a href="/ardours-interface/the-editor/the-editor_s-lists/tracks-and-busses-list/">Tracks and Busses</a> panel of the Editor List.
+</p>
+
+<p>
+ Dragging and dropping tracks inside the Strips List allows to reorganise the tracks in the session, both in the Mixer and the Editor.
+</p>
+
+<p>
+ It is possible, by <kbd class="mouse">right</kbd> clicking, to act on multiple tracks at once:
+</p>
+
+<ul>
+ <li>Show All</li>
+ <li>Hide All</li>
+ <li>Show All Audio Tracks</li>
+ <li>Hide All Audio Tracks</li>
+ <li>Show All Audio Busses</li>
+ <li>Hide All Audio Busses</li>
+ <li>Show All MIDI Tracks</li>
+ <li>Hide All MIDI Tracks</li>
+</ul>
+
+<p>
+ The <kbd class="menu">+</kbd> button under the list is a shortcut to create a new track, bus or VCA, as in clicking <kbd class="menu">Track > Add Track, Bus or VCA…</kbd>.
+</p>
---
title: The Mixer - The Groups list
part: subchapter
---
-<p class="fixme">add content</p>
+<p>
+ The <dfn>Goups List</dfn> allows to quickly manage the <a href="/working-with-tracks/track-and-bus-groups/">groups</a> of the session, and make use of them.
+</p>
+
+<p>
+ Each group has a <kbd class="option">Show</kbd> checkbox to quickly toggle their visibility. Clicking an already selected group allows to rename it.
+</p>
+
+<p>
+ The context menu, reached by <kbd class="mouse">right</kbd> clicking a group, allows for multiple mixing actions:
+</p>
+
+<dl>
+ <dt>Create New Group From...</dt><dd>Creates a new group based on some track properties. The choice is :
+ <ul>
+ <li><kbd class="menu">Selection...</kbd> to create a group of all selected tracks</li>
+ <li><kbd class="menu">Record Enabled...</kbd> to create a group of all the tracks that are record enabled</li>
+ <li><kbd class="menu">Soloed...</kbd> to create a group of all the soloed tracks</li>
+ </ul></dd>
+ <dt>Create New Group with Master From...</dt><dd>Acts exactly as the previous choice, but also creates a Control Master tied to these tracks.</dd>
+ <dt>Assign Selection to Control Master...</dt><dd>Allows to link all the selected tracks to a chosen Control Master, whether or not they belong to a group.</dd>
+ <dt>Assign Record Enabled to Control Master...</dt><dd>Allows to link all the record armed tracks to a chosen Control Master.</dd>
+ <dt>Assign Soloed to Control Master...</dt><dd>Allows to link all the soloed tracks to a chosen Control Master.</dd>
+ <dt>Enable All Groups</dt><dd>Enable all the groups, i.e. their selected properties are synchronized.</dd>
+ <dt>Disable All Groups</dt><dd>Disable all the groups, i.e. changing a property in a track won't affect the others.</dd>
+</dl>
+
+<p>
+ When a group is selected, <kbd class="mouse">right</kbd> clicking it adds the following menu entries :
+</p>
+
+<dl>
+ <dt>Create New Group with Master From...</dt><dd>Acts exactly as the previous choice, but also creates a Control Master tied to these tracks.</dd>
+ <dt>Edit Group...</dt><dd>Shows the <kbd class="menu">Track/bus Group</kbd> <a href="/working-with-tracks/track-and-bus-groups/">window</a>.</dd>
+ <dt>Collect Group</dt><dd>Rearranges the tracks/busses order to visualy group together the tracks belonging to the same group.</dd>
+ <dt>Remove Group</dt><dd>Deletes the group (but not the tracks/busses belongidng to this group).</dd>
+ <dt>Assign Group to Control Master...</dt><dd>Allows to link all the tracks in the group to a chosen VCA.</dd>
+ <dt>Add/Remove Subgroup Bus</dt><dd>Creates/removes a new bus connected to the Master, and send the output of all the tracks in the group to this new bus.</dd>
+ <dt>Add New Aux Bus (pre/post-fader)</dt><dd>Creates a new bus connected to the Master, and create <a href="/signal-routing/aux-sends/">Aux Sends</a> (pre or post-fader) in all the tracks in the group to this new bus.</dd>
+</dl>
+
+<p>
+ The <kbd class="menu">+</kbd> button under the list allows the creation of an (empty) group, while the <kbd class="menu">−</kbd> button deletes the selected group (but not the tracks in this group).
+</p>
---
title: The Mixer - The Master Strip
<p class="fixme">add content</p>
-
---
title: The Mixer - The Monitor Section
part: subchapter
-
-
---
title: Sessions & Tracks
part: part
title: New/Open Session Dialog
part: subchapter
---
+
<p class="fixme">Info is out of date, image needs updating</p>
<p>
---
<p>
- Every track and bus in Ardour is assigned a <dfn>remote control ID</dfn>.
- When a <a href="/using-control-surfaces/">control surface</a> or any other
- remote control is used to control Ardour, these IDs are used to identify
- which track(s) or buss(es) are the intended target of incoming commands.
+ Every track and bus in Ardour is assigned a <dfn>remote control ID</dfn>. When a <a href="/using-control-surfaces/">control surface</a> or any other remote control is used to control Ardour, these IDs are used to identify which track(s) or buss(es) are the intended target of incoming commands.
</p>
<p>
- By default, remote IDs will be assigned to tracks and busses in the order
- that they are created, starting from 1. The master bus and monitor section
- have their own unique IDs (318 and 319).
+ Remote IDs will be assigned to tracks and buses in the order that they appear in the mixer window from left to right, starting from 1. Manual assignment of remote IDs is not possible. The master bus and monitor section can be accessed by name.
</p>
-<p>
- Ardour provides two methods to control remote control IDs, which can be
- chosen via <kbd class="menu">Edit > Preferences > Control Surfaces
- > Control surface remote ID</kbd>:
-</p>
-
-<dl class="wide-table">
- <dt>follows order of mixer</dt>
- <dd>This will reset the remote control IDs to match the mixer and editor
- track order order, starting with rcID 1. Manual assignment of rcIDs is
- not possible.</dd>
- <dt>assigned by user</dt>
- <dd>When enabled, the remote control ID is completely independent of the
- ordering in either window, and may be changed manually by the user via the
- <kbd class="menu"><em>trackname</em> > Remote Control ID...</kbd>
- dialog in each mixer strip.
- </dd>
-</dl>
-
---
title: Bus Controls
part: subchapter
part: chapter
---
+<p class="fixme">Add content</p>
+
---
title: File and Session Management and Compatibility
part: chapter
---
-
+<p class="fixme">Add content</p>
---
---
-
-
---
-title: Looping the Transport
+title: Controlling Playback
part: subchapter
---
-<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
- before returning to the start and repeating.
- 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
- <a href="/working-with-markers/the-loop-range">Loop Range Markers</a>.
-</p>
-
-<p class="fixme">Broken link</p>
-
----
-title: Positioning the Playhead
-part: subchapter
----
+<h2>Positioning the Playhead</h2>
<p>
The <dfn>playhead</dfn> is a vertical line with two arrows at each end
that indicates the current position of playback.
</p>
-<h2>Positioning the playhead at the current pointer position</h2>
+<h3>Positioning the playhead at the current pointer position</h3>
<p>
Pressing <kbd>P</kbd> will set the playhead to the current position of
will move the playhead to that position.
</p>
-<h2>Positioning the playhead with the transport clocks</h2>
+<h3>Positioning the playhead with the transport clocks</h3>
<p>
Click on either the primary or secondary transport clock and
to move the playhead to a specific position.
</p>
-<h2>Positioning the playhead at a marker</h2>
+<h3>Positioning the playhead at a marker</h3>
<p>
Click <kbd class="mouse">Right</kbd> on the marker and select either
markers <dfn>start</dfn> and <dfn>end</dfn>, respectively.
</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 before returning to the start and repeating. 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 <a href="/working-with-markers/the-loop-range">Loop Range Markers</a>.
+</p>
+
+<p class="fixme">Broken link</p>
+
---
title: Using Key Bindings
part: subchapter
<p class="fixme">Broken links</a>
-
-
---
title: Editing
part: part
part: chapter
---
-
+<p class="fixme">Add content</p>
---
+
---
title: Arranging
part: part
part: chapter
---
+<p class="fixme">Add content</p>
+
---
title: Arranging Regions
part: chapter
---
+<p class="fixme">Add content</p>
+
---
title: Region Loops and Groups
part: chapter
---
-
+<p class="fixme">Add content</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.
+ 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>
<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>
part: chapter
---
+<p class="fixme">Add content</p>
+
---
title: Mixdown
+
---
title: Surround
part: part
part: chapter
---
+<p class="fixme">Add content</p>
+
---
title: Multichannel Tracks and Signal Routing
part: chapter
---
+<p class="fixme">Add content</p>
+
---
title: Surround Panning and Mixing
+
---
title: Sync & Video
part: part
+---
+title: Control Surfaces
+part: part
+---
+
+
+---
+title: Controlling Ardour with OSC
+include: controlling-ardour-with-osc.html
+exclude: yes
+part: chapter
+---
+
+---
+title: OSC: Controlling Ardour with OSC
+include: osc-control.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: OSC: Using the Setup Dialog
+include: osc-setup-dialog.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: OSC: Querying Ardour
+include: querying-ardour-with-osc.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: OSC: Feedback
+include: feedback-in-osc.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: OSC: Feedback and Strip-types Values
+include: calculating-feedback-and-strip-types-values.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: OSC: Personal Monitoring Control
+include: osc-personal-monitoring.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: OSC: Parameter Types
+include: parameter-types-in-osc.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: OSC: Selection and Expansion Considerations
+include: selection-considerations-in-osc.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: OSC control for Ardour 4.7 and Prior
+include: osc-control-in-ardour-4.7-and-prior.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: Devices using Mackie/Logic Control Protocol
+include: devices-using-mackielogic-control-protocol.html
+exclude: yes
+part: chapter
+---
+
+---
+title: Behringer devices in Mackie/Logic Control Mode
+menu_title: Behringer devices
+include: behringer-devices-in-mackielogic-control-mode.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: SSL Nucleus
+include: ssl-nucleus.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: Mackie Control Setup on Linux
+include: mackie-control-setup-on-linux.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: What to do if your Device is not Listed
+menu_title: Unlisted devices
+include: devices-not-listed.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: Working With Extenders
+menu_title: Working With Extenders
+include: working-with-extenders.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: Generic MIDI
+part: chapter
+---
+
+
+---
+title: MIDI Binding Maps
+include: midi-binding-maps.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: MIDI Learn
+include: midi-learn.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: Working With Encoders in Ardour
+menu_title: Working With Encoders
+include: working-with-encoders.html
+exclude: yes
+part: subchapter
+---
+
+---
+title: Using the Presonus Faderport
+menu_title: Presonus Faderport
+include: presonus-faderport.html
+exclude: yes
+part: chapter
+---
+
+---
+title: Using the Ableton Push 2
+menu_title: Ableton Push 2
+include: ableton-push2.html
+exclude: yes
+part: chapter
+---
+
---
title: Scripting
part: subchapter
---
+
+---
+title: Appendix
+part: part
+---
+
+
+---
+title: List of Menu Actions
+include: menu-actions-list.html
+exclude: yes
+part: chapter
+---
+
projects / ardour-manual-diverged / blobdiff