X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fgeneric-midi-binding-maps.html;h=144e2e9e2e31978d3730dc237a09e45aa58b9d0f;hb=df028d8ec186a46c814800a14e68ae13c137dad1;hp=c8c49c2b7405b5dfe2e03a14f4e2e4426972da0f;hpb=7be4f507991a0b87174a0e78831a4e7e9e96bcbe;p=ardour-manual diff --git a/include/generic-midi-binding-maps.html b/include/generic-midi-binding-maps.html index c8c49c2..144e2e9 100644 --- a/include/generic-midi-binding-maps.html +++ b/include/generic-midi-binding-maps.html @@ -53,8 +53,7 @@ remote control ID. 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. See - + remote control IDs for more information. You just need to know that there is a "first track" and its remote control ID is 1, and so on. @@ -74,11 +73,8 @@ bindings"> So, to start, create a file with that as the initial contents.
- On OS X, Ardour loads midi maps from its binary-bundle folder in
- Ardour-<version>/midi_maps/
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
- ~/.config/ardour3/midi_maps/
.
+ The file should be located in the midi_maps sub directory located in
+ the Ardour configuration directory
- <Binding channel="1" ctl="13" ….
+ <Binding channel="1" ctl="13" …
This defines a binding for a MIDI Continuous Controller message involving @@ -136,6 +132,21 @@ bindings"> Learn more about working with encoders )
++
<Binding channel="1" enc-r="13" …
<Binding channel="1" enc-l="13" …
<Binding channel="1" enc-2="13" …
<Binding channel="1" enc-b="13" …
enc-*
value is the CC number used by the encoder.
+ Encoders only work with CC messages.
+
++ 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. +
You can also bind sysex messages:
@@ -178,6 +189,9 @@ bindings"> A control address defines what the binding will actually control. There are quite a few different things that can be specified here: ++ Enable Feeback applies to these "Control Addresses" only. +
/route/gain | the gain control ("fader") for the track/bus |
---|
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:
a number, eg. "1" + | |
---|---|
a number, e.g. "1" | identifies a track or bus by its remote control ID |
+ It is not possible to have feedback available for actions because + these represent keyboard shortcuts which are input only. +
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 + href="@@list-of-menu-actions"> list of actions shows all available values of action-name.
To create a binding between an arbitrary MIDI message (we'll use a @@ -371,6 +392,9 @@ bindings"> <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"/>