ardour/manual
13
0
Fork 0
Code Pull Requests Releases Activity

try to explain the connection and difference between function and action bindings in a binding map

Browse Source
This commit is contained in:
Paul Davis 2020-08-17 13:18:47 -06:00
parent 9221af9b1d
commit 838f726821
1 changed files with 21 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
include/generic-midi-binding-maps.html
View File

@ -102,16 +102,18 @@ bindings">
<p> <p>
There are two basic kinds of bindings you can make between a MIDI message 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 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 of a track or bus. The second is a binding to something that will change
Ardour's state in some way. Ardour's state in some way (the "something" could either be called a
function or an action, see below).
</p> </p>
<h4>Binding to Track/Bus controls</h4> <h4>Binding to Track/Bus controls</h4>
<p> <p>
A track/bus binding has one of two basic structures A track/bus binding has one of three basic structures
</p> </p>
<code> <code>
&lt;Binding <em>msg specification</em> uri="<em>&hellip; control address &hellip;</em>"/&gt;</br> &lt;Binding <em>msg specification</em> uri="<em>&hellip; control address &hellip;</em>"/&gt;</br>
&lt;Binding <em>msg specification</em> function="<em>&hellip; function name &hellip;</em>"/&gt; &lt;Binding <em>msg specification</em> function="<em>&hellip; function name &hellip;</em>"/&gt;
&lt;Binding <em>msg specification</em> action="<em>&hellip; action name &hellip;</em>"/&gt;
</code> </code>
<h4>Message specifications</h4> <h4>Message specifications</h4>
@ -280,19 +282,28 @@ bindings"&gt;
<h4>Bindings to Ardour "functions"</h4> <h4>Bindings to Ardour "functions"</h4>
<p class="note"> <p class="note">
There is currently no feedback available for functions. There is currently no feedback available for functions.
</p> </p>
<p> <p>
Rather than binding to a specific track/bus control, it may be useful to 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. A have a MIDI controller able to alter some part of Ardour's
binding definition that does this looks like this: 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:
</p> </p>
<code> <code>
&lt;Binding channel="1" note="13" function="transport-roll"/&gt; &lt;Binding channel="1" note="13" function="transport-roll"/&gt;
</code> </code>
<p> <p>
In this case, a NoteOn message for note number 13 (on channel 1) will 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.
</p>
<p>
Note that a much greater number of operations are possible using
actions, described below.
</p>
<p>
The following function names are available:
</p> </p>
<table class="dl"> <table class="dl">
<tr><th> <tr><th>
@ -349,8 +360,8 @@ bindings"&gt;
<h4>Binding to Ardour "actions"</h4> <h4>Binding to Ardour "actions"</h4>
<p class="note"> <p class="note">
It is not possible to have feedback available for actions because It is not possible to have feedback available for actions because
these represent keyboard shortcuts which are input only. these represent keyboard shortcuts which are input only.
</p> </p>
<p> <p>
You can also bind a sysex or arbitrary message to any of the items You can also bind a sysex or arbitrary message to any of the items