Merge pull request #32 from ovenwerks/master

Filenames changes, spelling and puctuation fixes, wording fixes.

_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html

@@ -22,8 +22,8 @@ menu_title: Mackie/Logic Control Devices
 <p>
   From the selector at the top, choose the type of device you are using. 
   (<a
-  href="/using-control-surfaces/devices-using-mackielogic-control-protocol/devices_not_listed.html">
+  href="/using-control-surfaces/devices-using-mackielogic-control-protocol/devices-not-listed/">
-  What do do if your device is not listed</a>).
+  What to do if your device is not listed</a>).
 </p>
 <p>
   Once your setup is complete, click "OK" to close the dialog. Now click 

_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices-not-listed.html

@@ -1,8 +1,8 @@
 ---
 layout: default
-title: What to if your Device is not Listed
+title: What to do if your Device is not Listed
 menu_title: Unlisted devices
----                        
+---
 
 <p>
   All Mackie Control devices are based on the original Logic Control and the

_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working-with-extenders.html

@@ -0,0 +1,50 @@
+---
+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>
+ &lt;Extenders value="0"/&gt;
+ &lt;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.
+</p>
+<p>
+  When an <code>Extenders</code> value of greater than 0 is used, extra midi
+  ports will appear for the extenders to be connected to. <code>mackie
+  control</code> will remain always the leftmost controller. The MIDI ports
+  for any extra controlers will be named <code>mackie control #2</code> and
+  up. The numbers will go from left to right.
+</p>
+<p>
+  The <code>MasterPosition</code> value is the number of positions from
+  left to where the master unit (with the master fader) is. So if there are
+  three surfaces, <code>&lt;MasterPosition value="1"/&gt;</code> will expect
+  the master on the left, <code>&lt;MasterPosition value="2"/&gt;</code>
+  would be master in the middle and <code>&lt;MasterPosition
+  value="3"/&gt;</code> would be master on the right. So the position
+  matches the port name.
+</p>
+<p class="note">
+  The default value of <code>&lt;MasterPosition value="0"/&gt;</code> has
+  the same effect as <code>&lt;MasterPosition value="1"/&gt;</code>.
+</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>

_manual/22_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working_with_extenders.html

@@ -1,36 +0,0 @@
----
-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>

_manual/22_using-control-surfaces/03_midi-binding-maps.html

@@ -119,8 +119,10 @@ bindings">
   <code>enc-b</code> may be used for surfaces that have encoders that send
   offsets rather than values. These accept Continuous Controller messages
   but treat them as offsets. These are good for banked controls as they are
-  always at the right spot to start adjusting. See the link at the bottom of
+  always at the right spot to start adjusting. (
-  the page for a longer explanation.
+   <a href="/using-control-surfaces/midi-binding-maps/working-with-encoders/">
+   Learn more about working with encoders
+   </a>)
 </p>
 <p>
   You can also bind sysex messages:

_manual/22_using-control-surfaces/03_midi-binding-maps/01_working-with-encoders.html

@@ -7,12 +7,12 @@ menu_title: Working With Encoders
 <p>
   Encoders are showing up more frequently on controllers. However, they use
   the same MIDI events as Continuous Controllers and they have no standard
-  way of working. Ardour has implemented 4 of the more common ways of
+  way of sending that information as MIDI events. Ardour has implemented 4 of
-  sending encoder information.
+  the more common ways of sending encoder information.
 </p>
 <p>
   Encoders that send the same continuous values as a pot would are not
-  discussed here as they work the same.
+  discussed here as they are already supported by <code>ctl</code>.
 </p>
 <P>
   Encoders as this page talks about them send direction and offset that the
@@ -23,27 +23,28 @@ menu_title: Working With Encoders
 </p>
 <ul>
 <li>
-  enc-r - On the bcr/bcf2000 this is called "Relative Signed Bit". The most
+  enc-r:  On the bcr/bcf2000 this is called "Relative Signed Bit". The most
   significant bit sets positive and the lower 6 signifcant bits are the
   offset.
 </li>
 <li>
-  enc-l - The bcr2000 calls this "Relative Signed Bit 2". The most
+  enc-l: The bcr2000 calls this "Relative Signed Bit 2". The most
   significant bit sets negative and the lower 6 signifcant bits are the
   offset. If you are using one of these two and the values are right but
   reversed, use the other. This one is the one the Mackie Control Protocol
   uses.
 </li>
 <li>
-  enc-2 - The bcr2000 calls this one "Relative 2s Complement". Positive
+  enc-2: The bcr2000 calls this one "Relative 2s Complement". Positive
   offsets are sent as normal from 1 to 64 and negative offsets are sent as
   2s complement negative numbers.
 </li>
 <li>
-  enc-b - The bcr2000 calls this one "Relative Binary Offset". Positive
+  enc-b: The bcr2000 calls this one "Relative Binary Offset". Positive
   offsets are sent as offset plus 64 and negative offsets are sent as 64
   minus offset.
 </li>
+</ul>
 <p>
   If the wrong one is chosen, either the positive or negative side will act
   incorrectly. It is not really possible to auto detect which one the