<td>Asks for a list of tracks that have sends to the strip <em>ssid</em> points to</td></tr>
<tr><th><kbd class="osc">/strip/plugin/list <em>ssid</em></kbd></th>
<td>Asks for a list of plug-ins for strip <em>ssid.</em></td></tr>
- <tr><th><kbd class="osc">/plugin/descriptor <em>ssid</em> <em>piid</em></kbd></th>
+ <tr><th><kbd class="osc">/strip/plugin/descriptor <em>ssid</em> <em>piid</em></kbd></th>
<td>Asks for a list of descriptors for plug-in <em>piid</em> on strip <em>ssid</em></td></tr>
+ <tr><th><kbd class="osc">/set_surface</kbd></th>
+ <td>Ask for the current surface setting. Reply is in the same form as setting the surface would be.</td></tr>
</table>
<h3>A list of strips</h3>
<li>Monitor section present</li>
</ul>
</p>
+<p class="note">
+ The <code>/set_surface</code> should be set before this is called. That way
+ The right set of strips will be sent in return (though the default is good
+ for most uses) and feedback will start correctly.
+</p>
+<p>
+ If the surface is using <code>/strip/list</code>, the surface needs to know
+ if the strips have changed. This would be true if a strip gets moved, created or
+ deleted. When this happens Ardour sends <code>/strip/list</code> to the surfaces
+ that have previously requested a <code>/strip/list</code>. This lets the
+ surface know that it's list of strips is no longer valid.
+</p>
<p class="note">A bus will not have a record enable and so a bus message
will have one less parameter than a track. It is the controllers
responsability to deal with this.
</p>
<p>
While this seems complex, it is really not that bad. Minimum,
- maximum and value will in most cases give you all you need.
+ maximum and value will in most cases give you all you need. For simpler
+ access to plug-ins, the /select/plugin/ set of commands will handle most
+ needs.
</p>