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.
+</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 %}