From the selector at the top, choose the type of device you are using. - (What do do if your device is not listed). + ( + What do do if your device is not listed).
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 00000000..bfb9136b --- /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 +--- + +
+ 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. +
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 00000000..e89c94f1 --- /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 +--- + ++ 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. +
++ The two lines of interest are: +
+
+ >Extenders value="0"/> + >MasterPosition value="0"/> ++
+ Add these two lines if they are not present. The Extenders
+ 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
+ MasterPosition 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, MasterPosition with value 0 would be master
+ on the left, MasterPosition with value 1 would be master in
+ the middle and MasterPosition with value 2 would be master on
+ the right.
+
+ If the MasterPosition 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.
+
+ The sysex= and msg= bindings will only work with
+ function= or action= control addresses. They
+ will not work with the uri= control addresses.
+
A control address defines what the binding will actually control.