X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fosc58-querying-ardour.html;h=c94ec1009810981b6beec4a83cc4d69253bc033f;hb=a61fbacdfcb7a76fe425fada61f49fc85751e47a;hp=7e59c24cae7aac4c7dc638b0dc3caab80e129370;hpb=88d6f39b5f8b0f791b6833bb1512aa774b59d4f8;p=ardour-manual

diff --git a/include/osc58-querying-ardour.html b/include/osc58-querying-ardour.html
index 7e59c24..c94ec10 100644
--- a/include/osc58-querying-ardour.html
+++ b/include/osc58-querying-ardour.html
@@ -25,6 +25,8 @@
   <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>
+  <tr><th><kbd class="osc">/surface/list</kbd></th>
+  <td>Print a list of known surfaces and Link Sets to the log window.</td></tr>
 </table>
 
 <h3>A list of strips</h3>
@@ -40,7 +42,7 @@
 		<li>MT - MIDI Track</li>
 		<li>B - Audio Bus</li>
 		<li>MB - MIDI bus</li>
-		<li>AX - Aux bus</li>
+		<li>FB - Foldback bus</li>
 		<li>V - VCA</li>
     </ul>
     <li>Strip name</li>
@@ -70,7 +72,7 @@
   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.
+  surface know that its 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
@@ -181,4 +183,21 @@
 	access to plug-ins, the /select/plugin/ set of commands will handle most
 	needs.
 </p>
+<h3>Obtaining a list of surfaces Ardour knows about</h3>
+<p>
+	Ardour can work with more than one OSC control surface at a time.
+	Sometimes it is useful to know the information stored about all
+	surfaces. Sending <code>/surface/list</code> from any surface or selecting:
+	<kbd class="menu">Print surface information to Log window</kbd> from
+	the <kbd class="menu">Debug</kbd> dropdown in the OSC setup dialog,
+	will list all the information Ardour uses to calculate the feedback
+	it sends. The Log window can be opened from the menu with
+	<kbd class="option">Window &gt; Log</kbd>.
+	This would be useful information to include with any OSC
+	related Bug report. The output is printed in this format:
+</p>
+<p>
+<img alt="Surface Output"
+     src="/images/osc-surface-log.png">
+</p>