diff --git a/_manual/22_using-control-surfaces/03_midi-binding-maps.html b/_manual/22_using-control-surfaces/03_midi-binding-maps.html
index e42b3c60..cda1d597 100644
--- a/_manual/22_using-control-surfaces/03_midi-binding-maps.html
+++ b/_manual/22_using-control-surfaces/03_midi-binding-maps.html
@@ -114,6 +114,14 @@ bindings">
use note
(to create binding for a Note On message) or
pgm
(to create a binding for a Program Change message).
+ enc-r
, enc-l
, enc-2
and
+ enc-b
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. See the link at the bottom of
+ the page for a longer explanation.
+
You can also bind sysex messages:
@@ -359,3 +367,4 @@ bindings"> (the channel range may change at some point). +{% children %} diff --git a/_manual/22_using-control-surfaces/03_midi-binding-maps/01_working-with-encoders.html b/_manual/22_using-control-surfaces/03_midi-binding-maps/01_working-with-encoders.html new file mode 100644 index 00000000..91eea219 --- /dev/null +++ b/_manual/22_using-control-surfaces/03_midi-binding-maps/01_working-with-encoders.html @@ -0,0 +1,56 @@ +--- +layout: default +title: Working With Encoders in Ardour +menu_title: Working With Encoders +--- + ++ 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 working. Ardour has implemented 4 of the more common ways of + sending encoder information. +
++ Encoders that send the same continuous values as a pot would are not + discussed here as they work the same. +
++ Encoders as this page talks about them send direction and offset that the + DAW will add to or subtract from the current value. +
++ The 4 kinds of encoder supported are: +
++ 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. +
++ Many controllers have more than one choice as well, check the manual for + the surface. +