<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">
Calculating Feedback and Strip-types Values.</a>
</p>
<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>.
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>
-