First shot at docs for bundled plugins

[ardour-manual] / include / osc58-feedback-and-strip-types-values.html

diff --git a/include/osc58-feedback-and-strip-types-values.html b/include/osc58-feedback-and-strip-types-values.html
index 8785ae89230c67718d2416ffc50a7ffbd0713d39..f1a44555b1aa824356ef33cb089203788365f9bf 100644 (file)
--- a/include/osc58-feedback-and-strip-types-values.html
+++ b/include/osc58-feedback-and-strip-types-values.html
@@ -43,7 +43,7 @@
                64: Monitor.
        </li>
        <li>
-               128: Audio Aux.
+               128: FoldbackBusses.
        </li>
        <li>
                256: Selected.
@@ -107,24 +107,9 @@
                Making a user selected strip list.</a>
                <kbd class="osc">/strip/custom/mode 1</kbd>
          </li>
-  
+
   </ul>
 </p>
-<p class="note">
-  Audio Aux? say what? I am sure most people will have noticed that they
-  can find no <em>Aux</em> strips in the Ardour mixer. There are none.
-  There are busses that can be used a number of ways. From analog days,
-  in OSC, a bus is something that gets used as a sub mix before ending up
-  going to Master. An auxiliary bus is used like a separate mixer and
-  its output goes outside the program or computer to be used as:
-  a monitor mix, a back up recording, or what have you. In OSC where
-  controller strips may be limited, it may be useful not to use up a
-  strip for an aux that is not really a part of the mix. It is also
-  useful to get a list of only aux busses if the control surface is a
-  phone used to provide talent monitor mix control on stage. Each
-  performer would be able to mix their own monitor. The user is free
-  to enable both busses and auxes if they would prefer.
-</p>
 <h3 id="hidden">Using hidden strips</h3>
 <p>
        Ardour allows any of it's strips to be hidden so that they do not show