Currently (August 2016), we have presets for the following devices/modes:
</p>
<ul>
+ <li>AKAI MidiMix (2 layouts)</li>
<li>AKAI MPD-32</li>
<li>AKAI MPK61</li>
<li>AKAI MPKmini</li>
+ <li>Alesis QX25</li>
+ <li>Arturia KeyLab49</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 (3 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 25</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 Axiom Air 25</li>
+ <li>M-Audio Axiom Air Mini 32</li>
<li>M-Audio Oxygen 8v2</li>
+ <li>M-Audio Oxygen 25</li>
+ <li>M-Audio Oxygen 49</li>
+ <li>M-Audio Oxygen 61v3 (2 layouts)</li>
<li>Novation Impulse 49</li>
<li>Novation Impulse 61</li>
<li>Novation LaunchControl XL</li>
<li>Novation LaunchKey 25</li>
+ <li>Novation LaunchKey 49</li>
<li>Roland SI-24</li>
<li>Roland V Studio 20</li>
+ <li>WiiMote</li>
+ <li>Xboard 61</li>
<li>Yamaha KX25</li>
</ul>
At this time, new binding maps need to be created with a text editor.
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>.
+ The file should be located in the midi_maps sub directory located in
+ the <a href="@@files-and-directories-ardour-knows-about">Ardour configuration directory</a>
</p>
<h3>Finding out what your MIDI control surface sends</h3>
like this:
</p>
<code>
- <Binding channel="1" ctl="13" ….
+ <Binding channel="1" ctl="13" …
</code>
<p>
This defines a binding for a MIDI Continuous Controller message involving
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>
+ Continous Controlers (CCs) have coninued to evolve for different controlers.
+ The use of Encoders, RPN, NRPN, and controller buttons that give a 0 value
+ when released instead of toggling are now supported. These all have their
+ own type. The whole list of CC types are:
+</p>
+<p>
+ <ul>
+ <li>ctl - sets a CC to the value sent (works the same as
+ <code>note</code> with the <code>momentary</code> parameter set)</li>
+ <li>ctl-toggle - for CC controls that send a 127 for button press
+ and 0 for button release. The release is ignored and the value is
+ toggled with each press. (works the same as <code>note</code>)</li>
+ <li>ctl-dial - passes the CC value to the controlled object</li>
+ <li>rpn - The CC value may be a 14 bit value</li>
+ <li>nrpn - The CC number and the value may both be 14 bit values</li>
+ <li>rpn-delta - The value is expected to be a signed 14bit value
+ that is added to the current value. For use with encoders</li>
+ <li>nrpn-delta - The value is expected to be a signed 14bit value
+ that is added to the current value. For use with encoders</li>
+ <li>enc-r, enc-l, enc-2 and enc-b - For 7 bit encoders. See below</li>
+ </ul>
+</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
Learn more about working with encoders
</a>)
</p>
+<p>
+ <ul>
+ <li><code><Binding channel="1" enc-r="13" …</code></li>
+ <li><code><Binding channel="1" enc-l="13" …</code></li>
+ <li><code><Binding channel="1" enc-2="13" …</code></li>
+ <li><code><Binding channel="1" enc-b="13" …</code></li>
+ </ul>
+ The <code>enc-*</code> value is the CC number used by the encoder.
+ Encoders only work with CC messages.
+</p>
+<p class="note">
+ Ardour 5.12 has a bug with the encoder detection where the first
+ encoder message resets the control to 0. Setting "Enable Feedback"
+ on allows encoders to work as expected.
+</p>
<p>
You can also bind sysex messages:
</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>
+<p class="note">
+ Enable Feeback applies to these "Control Addresses" only.
+</p>
<table class="dl">
<tr><th>/route/gain</th>
<td>the gain control ("fader") for the track/bus</td></tr>
</table>
<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>
<table class="dl">
-<tr><th>a number, eg. "1"
+<tr><th>a number, e.g. "1"
</th>
<td>identifies a track or bus by its remote control ID
</td></tr>
</p>
<h4>Bindings to Ardour "functions"</h4>
+<p class="note">
+ There is currently no feedback available for functions.
+</p>
<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
</table>
<h4>Binding to Ardour "actions"</h4>
+<p class="note">
+ It is not possible to have feedback available for actions because
+ these represent keyboard shortcuts which are input only.
+</p>
<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 <a
<Binding channel="1" note="15" uri="/route/mute B1" momentary="yes"/>
<Binding channel="1" note="16" uri="/route/mute B2" momentary="yes"/>
+ <Binding channel="1" enc-r="11" uri="/route/pandirection B1"/>
+ <Binding channel="1" enc-r="12" uri="/route/pandirection B2"/>
+
<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"/>
decimal numbers in the ranges 1-16, 0-127 and 0-127 respectively
(the channel range may change at some point).
</p>
+