<p>
Ardour 2.X supported
- <a href="/using-control-surfaces/midi-learn"><dfn>MIDI learning</dfn></a>
+ <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
controls with anything inside Ardour that can be controlled.
</p>
<p>
- At this time, these binding maps need to be created with a text editor.
- Currently, we have presets for:
+ Currently (August 2016), we have presets for the following devices/modes:
</p>
<ul>
- <li>Behringer BCF 2000</li>
- <li>Korg_nanoKONTROL</li>
- <li>M-Audio Oxygen 8 v2</li>
- <li>Roland SI-24</li>
+ <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>M-Audio Axiom 25</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
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>
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.
<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>
(the channel range may change at some point).
</p>
+{% children %}