From: Len Ovens <len@ovenwerks.net>
Date: Thu, 23 Jul 2015 02:05:02 +0000 (-0700)
Subject: Add extender documentation and clarification to Surfaces.
X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1257b9b4b1e36da5a0085433dbdca6255d13d2e9;p=ardour-manual-diverged

Add extender documentation and clarification to Surfaces.
---

diff --git a/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html b/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html
index 550b671..9417268 100644
--- a/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html
+++ b/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html
@@ -21,7 +21,9 @@ menu_title: Mackie/Logic Control Devices
 <img src="" alt="Mackie Control Setup Dialog" />
 <p>
   From the selector at the top, choose the type of device you are using. 
-  (<a href="/missing">What do do if your device is not listed</a>).
+  (<a
+  href="devices-using-mackielogic-control-protocol/devices_not_listed.html">
+  What do do if your device is not listed</a>).
 </p>
 <p>
   Once your setup is complete, click "OK" to close the dialog. Now click 
diff --git a/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices_not_listed.html b/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices_not_listed.html
new file mode 100644
index 0000000..bfb9136
--- /dev/null
+++ b/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices_not_listed.html
@@ -0,0 +1,18 @@
+---
+layout: default
+title: What to if your Device is not Listed
+menu_title: Unlisted devices
+---                        
+
+<p>
+  All Mackie Control devices are based on the original Logic Control and the
+  documentation in the user manual that came with it. The Mackie Control and
+  the Mackie Control Pro and so on, all use this same protocol. Any units
+  from other manufactures will also use the same encoding as best the
+  hardware will allow. If the unit in use has more than one Mackie Control
+  option, it is best to choose Logic Control or LC. Any Templates for the
+  buttons should be chosen the same way as the Function key Editor uses these
+  button names. The "Mackie Control" option should be considered default and
+  should be tried with any unlisted device before attemping to create a
+  custom definition file.
+</p>
diff --git a/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working_with_extenders.html b/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working_with_extenders.html
new file mode 100644
index 0000000..e89c94f
--- /dev/null
+++ b/_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working_with_extenders.html
@@ -0,0 +1,36 @@
+---
+layout: default
+title: Working With Extenders
+menu_title: Working With Extenders
+---                        
+
+<p>
+  Extenders will require a custom file as there are no combinations listed
+  at this time. The best way is to start with the mc.device file and copy it
+  to a new name such as xt+mc.device and then edit that file. It is best to
+  name the file with the order the devices are expected to be used in as
+  the position of the master device is specified in this file.
+</p>
+<p>
+  The two lines of interest are:
+<p>
+<pre>
+ &gt;Extenders value="0"/&gt;
+ &gt;MasterPosition value="0"/&gt;
+</pre>
+<p>
+  Add these two lines if they are not present. The <code>Extenders</code>
+  value is the number of extenders used and should not include the master in
+  that number. That is, it should be the total number of units minus 1. The
+  <code>MasterPosition</code> value is the position from left to right where
+  the master unit (with the master fader) is, starting at 0. So if there are
+  three surfaces, <code>MasterPosition</code> with value 0 would be master
+  on the left, <code>MasterPosition</code> with value 1 would be master in
+  the middle and <code>MasterPosition</code> with value 2 would be master on
+  the right.
+</p>
+<p>
+  If the <code>MasterPosition</code> value does not properly match the
+  physcal position and MIDI port, the master fader and global controls will
+  not work. The master unit will act like an extender.
+</p>
diff --git a/_manual/22_using-control-surfaces/03_midi-binding-maps.html b/_manual/22_using-control-surfaces/03_midi-binding-maps.html
index dde7a63..8282862 100644
--- a/_manual/22_using-control-surfaces/03_midi-binding-maps.html
+++ b/_manual/22_using-control-surfaces/03_midi-binding-maps.html
@@ -138,6 +138,13 @@ bindings"&gt;
   some oddly designed control devices.
 </p>
 
+<h5>Note:<h5>
+<p>
+  The <code>sysex=</code> and <code>msg=</code> bindings will only work with
+  <code>function=</code> or <code>action=</code> control addresses. They
+  will <em>not</em> work with the <code>uri=</code> control addresses.
+</p>
+
 <h4>Control address</h4>
 <p>
   A <dfn>control address</dfn> defines what the binding will actually control.