<p>
Ardour does feedback by sending the same path back that is used to
control the same function. As such any controls that have feedback
- have a parameter that is the value of the control or it's state
+ have a parameter that is the value of the control or its state
(on or off). In the case of OSC paths listed on the main OSC page
as having no parameter, if they have feedback, they will also work
with a 1 for button press and 0 for button release. This is because
<p>
These messages are feedback only. They are sent as status from Ardour
and some of them may be enabled separately from other feedback. See:
- <a href="@@osc58-feedback-and-strip-types-values">
+ <a href="@@osc58-feedback-and-strip-types-values#feedback">
Calculating Feedback and Strip-types Values.</a>
</p>
<p class="note">
<table class="dl">
<tr><th><kbd class="osc">/strip/name <em>ssid</em> <em>track_name</em></kbd></th>
<td>where <em>track_name</em> is a string representing the name of the track</td></tr>
+ <tr><th><kbd class="osc">/strip/*/automation_name <em>ssid</em> <em>name</em></kbd></th>
+ <td>where <em>name</em> is a string representing the current automation mode for the control.
+ <a href="@@osc58-automation">See OSC Automation.</a></td></tr>
<tr><th><kbd class="osc">/session_name <em>session_name</em></kbd></th>
<td>where <em>session_name</em> is a string representing the name of the session</td></tr>
<tr><th><kbd class="osc">/strip/meter <em>ssid</em> <em>meter</em></kbd></th>
- <td>where <em>meter</em> is a value repesenting the current audio level.
+ <td>where <em>meter</em> is a value representing the current audio level.
(the exact math used is determined by the feedback bits set)</td></tr>
<tr><th><kbd class="osc">/strip/signal <em>ssid</em> <em>signal</em></kbd></th>
<td>where <em>signal</em> is a float indicating the instantaneous
<td><em>state</em> is true when transport is moving forward but not at speed 1.0</td></tr>
<tr><th><kbd class="osc">/rewind <em>state</em></kbd></th>
<td><em>state</em> is true when transport speed is less than 0.0</td></tr>
+ <tr><th><kbd class="osc">/marker <em>position</em></kbd></th>
+ <td><em>position</em> is a string in the form <kbd class="osc">previous <-> next</kbd>
+ or <kbd class="osc">current</kbd> (new Ardour 6.0)</td></tr>
<tr><th><kbd class="osc">/loop_toggle <em>state</em></kbd></th>
<td><em>state</em> is true when loop mode is true</td></tr>
<tr><th><kbd class="osc">/cancel_all_solos <em>state</em></kbd></th>
<td>Where <em>state</em> true indicates there are active solos that can be canceled.</td></tr>
+ <tr><th><kbd class="osc">/jog/mode/name <em>name</em></kbd></th>
+ <td>Where <em>name</em> is a string indicating the name of the current jog mode.</td></tr>
</table>
<h3>Recording control</h3>
below can also be sent as /strip/command/ssid param. Feedback can be
set to match this with the /set_surface/feedback <em>state</em>
command. See <a
- href="/using-control-surfaces/controlling-ardour-with-osc/calculating-feedback-and-strip-types-values/">
+ href="@@osc58-feedback-and-strip-types-values#feedback">
Calculating Feedback and Strip-types Values.</a>
</p>
<td>where <em>LED</em> is a bool that indicates another bank_up operation is possible.</td></tr>
<tr><th><kbd class="osc">/bank_down <em>LED</em></kbd></th>
<td>where <em>LED</em> is a bool that indicates another bank_down operation is possible.</td></tr>
- <tr><th><kbd class="osc">/strip/name <em>ssid</em> <em>track_name</em></kbd></th>
- <td>where <em>track_name</em> is a string representing the name of the track
- (note there is no coresponding command to set the track name)</td></tr>
+ <tr><th><kbd class="osc">/strip/name <em>ssid</em> <em>strip_name</em></kbd></th>
+ <td>where <em>strip_name</em> is a string representing the name of the strip</td></tr>
+ <tr><th><kbd class="osc">/strip/group <em>ssid</em> <em>group_name</em></kbd></th>
+ <td>where <em>group_name</em> is a string representing the name of the group the track belongs to</td></tr>
<tr><th><kbd class="osc">/strip/mute <em>ssid</em> <em>mute_st</em></kbd></th>
<td>where <em>mute_st</em> is a bool/int representing the actual mute state of the track</td></tr>
<tr><th><kbd class="osc">/strip/solo <em>ssid</em> <em>solo_st</em></kbd></th>
<td>where <em>gain</em> is a float ranging from -193 to 6 representing the actual gain of the track in dB.</td></tr>
<tr><th><kbd class="osc">/strip/fader <em>ssid</em> <em>position</em></kbd></th>
<td>where <em>position</em> is an float ranging from 0 to 1 representing the actual fader position of the track.</td></tr>
+ <tr><th><kbd class="osc">/strip/*/automation <em>ssid</em> <em>mode</em></kbd></th>
+ <td>where <em>mode</em> is an int ranging from 0 to 3 representing the actual automation mode for the control.
+ <a href="@@osc58-automation">See OSC Automation.</a></td></tr>
<tr><th><kbd class="osc">/strip/trimdB <em>ssid</em> <em>trim_db</em></kbd></th>
<td>where <em>trim_db</em> is a float ranging from -20 to 20 representing the actual trim of the track in dB.</td></tr>
<tr><th><kbd class="osc">/strip/pan_stereo_position <em>ssid</em> <em>position</em></kbd></th>
<td>where <em>position</em> is a float ranging from 0 to 1 representing the actual pan position of the track</td></tr>
</table>
-<h3>Selection Operations</h3>
+<h3>Selected Operations</h3>
<p>
Selection feedback is the same as for strips, only the path changes
from <em>/strip</em> to <em>/select</em> and there is no <em>ssid</em>.
<tr><th><kbd class="osc">/select/send_name <em>sendid</em> <em>send_name</em></kbd></th>
<td>where <em>send_name</em> is a string representing the name of the buss
this send goes to.</td></tr>
+ <tr><th><kbd class="osc">/select/group/enable <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int representing the current enable state
+ of the group the selected strip is a part of</td></tr>
+ <tr><th><kbd class="osc">/select/group/gain <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int which shows the gain sharing of the
+ group the strip belongs to. See <a href="@@track-and-bus-groups">
+ Track and Bus Groups</a> for more details</td></tr>
+ <tr><th><kbd class="osc">/select/group/relative <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int which shows relative state of thew
+ group the strip belongs to. See <a href="@@track-and-bus-groups">
+ Track and Bus Groups</a> for more details</td></tr>
+ <tr><th><kbd class="osc">/select/group/mute <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int which shows the mute sharing of the
+ group the strip belongs to. See <a href="@@track-and-bus-groups">
+ Track and Bus Groups</a> for more details</td></tr>
+ <tr><th><kbd class="osc">/select/group/solo <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int which shows the solo sharing of the
+ group the strip belongs to. See <a href="@@track-and-bus-groups">
+ Track and Bus Groups</a> for more details</td></tr>
+ <tr><th><kbd class="osc">/select/group/recenable <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int which shows the recenable sharing of the
+ group the strip belongs to. See <a href="@@track-and-bus-groups">
+ Track and Bus Groups</a> for more details</td></tr>
+ <tr><th><kbd class="osc">/select/group/select <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int which shows the select sharing of the
+ group the strip belongs to. See <a href="@@track-and-bus-groups">
+ Track and Bus Groups</a> for more details</td></tr>
+ <tr><th><kbd class="osc">/select/group/active <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int which shows the route active sharing of the
+ group the strip belongs to. See <a href="@@track-and-bus-groups">
+ Track and Bus Groups</a> for more details</td></tr>
+ <tr><th><kbd class="osc">/select/group/color <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int which shows the color sharing of the
+ group the strip belongs to. See <a href="@@track-and-bus-groups">
+ Track and Bus Groups</a> for more details</td></tr>
+ <tr><th><kbd class="osc">/select/group/monitoring <em>state</em></kbd></th>
+ <td>where <em>state</em> is an int which shows the monitoring sharing of the
+ group the strip belongs to. See <a href="@@track-and-bus-groups">
+ Track and Bus Groups</a> for more details</td></tr>
+ <tr><th><kbd class="osc">/select/vcas <em>name</em> <em>state</em> ...</kbd></th>
+ <td>where <em>name</em> is a string with the name of the VCA, and
+ <em>state</em> is an int that determines if the named VCA will control
+ this strip. Note that this lists all VCAs in a session. (Ardour 6.0)</td></tr>
</table>
<h3>Menu actions</h3>
+<p class="note">
+ There is no feedback for Menu actions.
+</p>
<p>
Every single menu item in Ardour's GUI is accessible via OSC. However,
there is no provision for returning the state of anything set this way.
This is not a bad thing as most menu items either do not have an on/off
- state or that state is quite visible. Binding that affect other parameters
+ state or that state is quite visible. Bindings that affect other parameters
that OSC does track will show on those OSC controls. Examples of this
might be track record enable for tracks 1 to 32, play or stop.
</p>
projects / ardour-manual / blobdiff