diff --git a/include/generic-midi-binding-maps.html b/include/generic-midi-binding-maps.html index 7966cfed..f7d6ad51 100644 --- a/include/generic-midi-binding-maps.html +++ b/include/generic-midi-binding-maps.html @@ -102,16 +102,18 @@ bindings">
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 function="… function name …"/>
+ <Binding msg specification action="… action name …"/>
- 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:
@@ -349,8 +360,8 @@ bindings">
Binding to Ardour "actions"- It is not possible to have feedback available for actions because - these represent keyboard shortcuts which are input 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 |
---|