X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fgeneric-midi-binding-maps.html;h=3757a1dd4cff5fb7ea9758e648a6ad00c10e3d38;hb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;hp=43d56a115ba267885d37d376bc021ba3597f3bf8;hpb=e6123839d20de4f903ed74820cc087fc8401f625;p=ardour-manual diff --git a/include/generic-midi-binding-maps.html b/include/generic-midi-binding-maps.html index 43d56a1..3757a1d 100644 --- a/include/generic-midi-binding-maps.html +++ b/include/generic-midi-binding-maps.html @@ -106,8 +106,8 @@ bindings"> A track/bus binding has one of two basic structures
- <Binding msg specification uri="... control address ..."/>
- <Binding msg specification function="... function name ..."/>
+ <Binding msg specification uri="… control address …"/>
+ <Binding msg specification function="… function name …"/>
- <Binding channel="1" ctl="13" ....
+ <Binding channel="1" ctl="13" ….
This defines a binding for a MIDI Continuous Controller message involving @@ -140,8 +140,8 @@ bindings"> You can also bind sysex messages:
- <Binding sysex="f0 0 0 e 9 0 5b f7" ....
- <Binding sysex="f0 7f 0 6 7 f7" ....
+ <Binding sysex="f0 0 0 e 9 0 5b f7" ….
+ <Binding sysex="f0 7f 0 6 7 f7" ….
The string after the sysex=
part is the sequence of MIDI bytes,
@@ -150,8 +150,8 @@ bindings">
Finally, you can bind a totally arbitrary MIDI message:
- <Binding msg="f0 0 0 e 9 0 5b f7" ....
- <Binding msg="80 60 40" ....
+ <Binding msg="f0 0 0 e 9 0 5b f7" ….
+ <Binding msg="80 60 40" ….
The string after the msg=
part is the sequence of MIDI bytes, as
@@ -228,7 +228,7 @@ bindings">
One additional feature: for solo and mute bindings, you can also add
momentary="yes"
after the control address. This is useful
- primarily for NoteOn bindings — when Ardour gets the NoteOn it
+ primarily for NoteOn bindings—when Ardour gets the NoteOn it
will solo or mute the targetted track or bus, but then when a NoteOff
arrives, it will un-solo or un-mute it.