X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fpatchbay.html;h=dbb85b14340becdc9b1f1dee5fa25901d051563c;hb=d28fa29291b40f709f5f792649ef5bd5f838956b;hp=0c0ef57841b3b25733edbb495d267233a3870f2e;hpb=a599c95d1610c895dfa7a86f63eb35345ddd0b85;p=ardour-manual

diff --git a/include/patchbay.html b/include/patchbay.html
index 0c0ef57..dbb85b1 100644
--- a/include/patchbay.html
+++ b/include/patchbay.html
@@ -1,5 +1,5 @@
 <figure class="right">
-  <img src="/images/connection-manager.png" alt="An example patchbay">
+  <img width="50%" src="/images/connection-manager.png" alt="An example patchbay">
   <figcaption>
     An example patchbay
   </figcaption>
@@ -30,18 +30,23 @@
   <tr><th>Hardware</th>
       <td>These are ports which are connected to a physical piece of hardware
       (a sound card or MIDI interface).</td></tr>
-  <tr><th>Ardour Busses</th>
-      <td>All ports belonging to busses.</td></tr>
-  <tr><th>Ardour Tracks</th>
-      <td>All ports belonging to tracks.</td></tr>
   <tr><th>Ardour Misc</th>
       <td>These are other ports that do not fit into the previous two
       categories; for example, the ports on which the metronome click
       is output, and MIDI ports for things like control surfaces and
       timecode.</td></tr>
+  <tr><th>I/O Pre</th>
+      <td>All ports of I/O Pre-Process Plugins.</td></tr>
+  <tr><th>I/O Post</th>
+      <td>All ports of I/O Post-Process Plugins.</td></tr>
+  <tr><th>Tracks</th>
+      <td>All ports belonging to tracks.</td></tr>
+  <tr><th>Busses</th>
+      <td>All ports belonging to busses.</td></tr>
   <tr><th>Other</th>
       <td>
-      If there are other JACK clients running, their ports will be found
+      If the Jack backend is being used and if there are other JACK clients
+      running, their ports will be found
       here. If there are no such ports, the tab will not exist (on one or
       both axes of the grid).</td></tr>
 </table>
@@ -63,15 +68,15 @@
   made between Foo (a MIDI output) and our busses (which are all audio-input).
 </p>
 <p>
-  The green dots in the example show that both Foo and Bar are connected
+  The green dots in the example show that both Fred and Jim are connected
   to the master bus, left to left and right to right.
 </p>
 
 <h2>Variants on the Patchbay</h2>
 <p>
   Slightly different versions of the patchbay are available from different
-  places in Ardour. A global view of all JACK audio connections is available, in
-  <kbd class="menu">Window &gt Audio Connections</kbd>, or by pressing
+  places in Ardour. A global view of all audio connections is available, in
+  <kbd class="menu">Window &gt; Audio Connections</kbd>, or by pressing
   <kbd class="mod2">P</kbd>. A corresponding MIDI Connection Manager can
   be opened using <kbd class="mod23">P</kbd>.</p>
 <p>
@@ -88,7 +93,7 @@
   opens a context menu which provides a few handy options:
 </p>
 <table class="dl">
-  <tr><th><kbd class="menu">Add audio port</kbd> and <kbd class="menu">Add MIDI port</kbd></th>
+  <tr><th><kbd class="menu">Add audio port</kbd><br> and <br><kbd class="menu">Add MIDI port</kbd></th>
   <td>
     These options add audio or MIDI ports to the clicked source, if this is
     possible. In this way, for example, tracks and busses can be extended to have
@@ -103,7 +108,8 @@
   <td>Disconnects everything from the given port.</td></tr>
   <tr><th><kbd class="menu">Rescan</kbd></th>
   <td>
-    Ardour will try to keep abreast of any changes to the JACK ports on
+    If Ardour is using the JACK backend, Ardour will try to keep abreast
+    of any changes to the JACK ports on
     the system, and reflect them in any connection managers which are open.
     If for some reason this fails, this can be used to re-scan the list of ports and
     update the manager.