Feedback from the Ardour to the the control surface is very useful for
a number of things. Motor faders need to know where the the track
they have been attached to is at before they were assigned otherwise
- they will jump to where the local fader is. Likewise, the buttons on
- each strip need to know what there value is so they can light there LED
- correctly. Transport controls should let you know if they are active
- too. This is what feedback is all about.
+ the DAW fader will jump to where the controller fader is. Likewise,
+ the buttons on each strip need to know what their value is so they can
+ light their LED correctly. Transport controls should let you know if
+ they are active too. This is what feedback is all about.
</p>
<p>
Ardour does feedback by sending the same path back that is used to
<p>
The feedback does not have the same meaning as the control message.
- Rather, the feedback will be:
+ Where the button release sent to Ardour will be ignored and has no
+ meaning. Both states have meaning in feedback to the controller.
+ The feedback will be:
</p>
<dl class="bindings">
That is with pan width at 100% (or -100%) there is no pan position
movement available.
</p>
+<p>
+ It may come as a surprise, but feedback often generates more network
+ traffic than control itself does. Some things are more obvious like
+ head position or meters. But even a simple button push like transport
+ start sends not only a signal to turn on the play LED, but also one to
+ turn off the stop LED, the Rewind LED, the Fast Forward LED and the
+ Loop LED. That is still minor, think instead of a surface refresh
+ such as happens when the surface is first connected and then most of
+ that happens every time the fader strips are banked. This is why
+ feedback is enabled in sections so that as little feedback as is
+ actually needed is sent. This is also a consideration if the surface
+ is connected via wifi.
+</p>
<h2>List of OSC feedback messages</h2>
<h3>Feedback only</h3>
See strip section below for info about ssid and wrapping it into the
path. Also /master and /monitor support what the /strip does.
</p>
+<p>
+ In the case where Gainmode is set to position, the track name will
+ show the dB value while values are changing.
+</p>
<dl class="bindings">
<dt><kbd class="osc">/strip/name <em>ssid</em> <em>track_name</em></kbd></dt>
<dd>where <em>track_name</em> is a string representing the name of the track</dd>
<dt><kbd class="osc">/strip/gain <em>ssid</em> <em>gain</em></kbd></dt>
<dd>where <em>gain</em> is a float ranging from -193 to 6 representing the actual gain of the track in dB.</dd>
<dt><kbd class="osc">/strip/fader <em>ssid</em> <em>position</em></kbd></dt>
- <dd>where <em>position</em> is an int ranging from 0 to 1023 representing the actual gain of the track in dB.</dd>
+ <dd>where <em>position</em> is an float ranging from 0 to 1 representing the actual fader position of the track.</dd>
<dt><kbd class="osc">/strip/trimdB <em>ssid</em> <em>trim_db</em></kbd></dt>
<dd>where <em>trim_db</em> is a float ranging from -20 to 20 representing the actual trim of the track in dB.</dd>
<dt><kbd class="osc">/strip/pan_stereo_position <em>ssid</em> <em>position</em></kbd></dt>
<dt><kbd class="osc">/select/polarity <em>invert</em></kbd></dt>
<dd>where <em>invert</em> is a bool/int representing the actual polarity of the track</dd>
<dt><kbd class="osc">/select/pan_stereo_width <em>width</em></kbd></dt>
- <dd>where <em>width</em> is a float ranging from -1 to 1 representing the actual pan width of the track</dd>
+ <dd>where <em>width</em> is a float ranging from 0 to 1 representing the actual pan width of the track</dd>
<dt><kbd class="osc">/select/send_gain", <em>sendid</em> <em>send_gain</em></kbd></dt>
<dd>where <em>sendid</em> = nth_send, <em>send_gain</em>is a float
ranging from -193 to +6 representing the actual gain in dB for the send</dd>
<dt><kbd class="osc">/select/send_fader", <em>sendid</em> <em>send_gain</em></kbd></dt>
<dd>where <em>sendid</em> = nth_send, <em>send_gain</em>is a float
- ranging from 0 to 1023 representing the actual position for the send as a fader</dd>
+ ranging from 0 to 1 representing the actual position for the send as a fader</dd>
<dt><kbd class="osc">/select/send_name <em>sendid</em> <em>send_name</em></kbd></dt>
<dd>where <em>send_name</em> is a string representing the name of the buss
this send goes to.</dd>