OSC more personal monitoring changes

[ardour-manual] / include / osc58-personal-monitoring-control.html

diff --git a/include/osc58-personal-monitoring-control.html b/include/osc58-personal-monitoring-control.html
index 109397c2835c8107e227ecb7b80df0354ad7a658..65239dee93c9636346aa72b21021ff6da296bb87 100644 (file)
--- a/include/osc58-personal-monitoring-control.html
+++ b/include/osc58-personal-monitoring-control.html
@@ -50,11 +50,33 @@
        Most phone OSC applets (TouchOSC, Control) require manual port to be set.
        There are certainly more controls than needed. Using send enables for
        example, may lead to wasted time discovering why a send has no sound.
-       A good easy to use controler that fits on most phones while still
+       A good easy to use controller that fits on most phones while still
        being controllable even with big fingers might look like:
 </p>
-<img alt="TouchOSC Screenshot"
-     src="/images/osc-cue-screen">
+<table>
+ <tr>
+  <td>
+       <figure>
+       <img alt="TouchOSC Screenshot"
+       src="/images/osc-cue-touchosc.jpg">
+    <figcaption>Personal Monitor controller using TouchOSC</figcaption>
+       </figure>
+  </td>
+  <td>
+       <figure>
+       <img alt="Control Screenshot"
+       src="/images/osc-cue-control.jpg">
+    <figcaption>Personal Monitor controller using Control</figcaption>
+       </figure>
+  </td>
+ </tr>
+</table>
+
+<p>
+       Ardour is not limited to talking to one personal monitor controller
+       at a time, but is able to deal with many simultaneously, each controlling
+       it's own Aux bus.
+</p>
 <p class="note">
        The send controls and feedback all have the send id (1 to n) in line
        as part of the OSC path. So the path for the second send would be