X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=include%2Fgeneric-midi-binding-maps.html;h=f7d6ad515a2f57086f29c3ecd4da75d8b1675610;hb=838f7268217de24d10c4462936250963bb84472e;hp=52f7ad8e3c82860443cdc901a7cdbcbdafbc2376;hpb=a14fc093fddf2000f690869d131c5f7475a79ab3;p=ardour-manual diff --git a/include/generic-midi-binding-maps.html b/include/generic-midi-binding-maps.html index 52f7ad8..f7d6ad5 100644 --- a/include/generic-midi-binding-maps.html +++ b/include/generic-midi-binding-maps.html @@ -14,28 +14,36 @@ Currently (August 2016), we have presets for the following devices/modes:
There are two basic kinds of bindings you can make between a MIDI message and something inside Ardour. The first is a binding to a specific parameter - of a track or bus. The second is a binding to a function that will change - Ardour's state in some way. + of a track or bus. The second is a binding to something that will change + Ardour's state in some way (the "something" could either be called a + function or an action, see below).
- A track/bus binding has one of two basic structures + A track/bus binding has one of three basic structures
- <Binding msg specification uri="… control address …"/>
+ <Binding msg specification uri="… control address …"/>
<Binding msg specification function="… function name …"/>
+ <Binding msg specification action="… action name …"/>
note
(to create binding for a Note On message) or
pgm
(to create a binding for a Program Change message).
++ 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: +
++
note
with the momentary
parameter set)note
)
As of Ardour 4.2, enc-r
, enc-l
, enc-2
and
enc-b
may be used for surfaces that have encoders that send
@@ -151,7 +184,7 @@ bindings">
You can also bind sysex messages:
- <Binding sysex="f0 0 0 e 9 0 5b f7" ….
+ <Binding sysex="f0 0 0 e 9 0 5b f7" ….
<Binding sysex="f0 7f 0 6 7 f7" ….
@@ -161,7 +194,7 @@ bindings">
Finally, you can bind a totally arbitrary MIDI message:
- <Binding msg="f0 0 0 e 9 0 5b f7" ….
+ <Binding msg="f0 0 0 e 9 0 5b f7" ….
<Binding msg="80 60 40" ….
@@ -249,19 +282,28 @@ bindings">
- There is currently no feedback available for functions. + There is currently no feedback available for functions.
- 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 - binding definition that does this looks like this: + Rather than binding to a specific track/bus/plugin control, it may be useful to + have a MIDI controller able to alter some part of Ardour's + state. Ardour's Generic MIDI support provides a small number of + easily-used "functions" to do the most common operations, using a + binding that looks like this:
<Binding channel="1" note="13" function="transport-roll"/>
In this case, a NoteOn message for note number 13 (on channel 1) will - start the transport rolling. The following function names are available: + start the transport rolling. +
++ Note that a much greater number of operations are possible using + actions, described below. +
++ The following function names are available:
@@ -318,8 +360,8 @@ bindings">
Binding to Ardour "actions"- It is not possible to have feedback available actions because these - represent keyboard shortcuts which are send only. + 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 |
---|