2015-08-04 20:06:04 -04:00
|
|
|
---
|
|
|
|
layout: default
|
|
|
|
title: Working With Extenders
|
|
|
|
menu_title: Working With Extenders
|
|
|
|
---
|
|
|
|
|
|
|
|
<p>
|
2017-01-27 11:07:41 -05:00
|
|
|
There are currently 5 devices preconfigured to work with extenders.
|
|
|
|
Two of them are for one master and one extender with the master on the
|
|
|
|
right side or master on the left side. There are three presets for a
|
|
|
|
master and two extenders with the master on the left, in the center
|
|
|
|
and on the right. While these files will work for many uses there may
|
|
|
|
be cases where a custom device profile makes more sense.
|
2017-01-27 23:45:33 -05:00
|
|
|
The best way is to start with the *.device file in the <a
|
|
|
|
href="/appendix/files-and-directories/">
|
|
|
|
sytem config sub directory mcp</a> that matches your
|
|
|
|
master device and copy it to a new name such as xt+mc.device in the
|
|
|
|
<a href="/appendix/files-and-directories/">
|
|
|
|
user config sub directory mcp</a> and then edit that file. It is best to
|
2015-08-04 20:06:04 -04:00
|
|
|
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>
|
2017-01-27 11:07:41 -05:00
|
|
|
The three lines of interest are:
|
2015-08-04 20:06:04 -04:00
|
|
|
<p>
|
|
|
|
<pre>
|
2017-01-27 11:07:41 -05:00
|
|
|
<Name value="Device name"/>
|
2015-08-04 20:06:04 -04:00
|
|
|
<Extenders value="0"/>
|
|
|
|
<MasterPosition value="0"/>
|
|
|
|
</pre>
|
|
|
|
<p>
|
2017-01-27 11:07:41 -05:00
|
|
|
Add any lines that are not present.
|
|
|
|
</p>
|
|
|
|
<p>
|
|
|
|
The <code>Name</code> value should be a unique name so it is obvious
|
2017-01-27 23:45:33 -05:00
|
|
|
in the list of devices (so change it).
|
2017-01-27 11:07:41 -05:00
|
|
|
</p>
|
|
|
|
<p>
|
|
|
|
The <code>Extenders</code>
|
2015-08-04 20:06:04 -04:00
|
|
|
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
|
2015-08-22 11:02:50 -04:00
|
|
|
ports will appear for the extenders to be connected to. The MIDI ports
|
2017-01-27 23:45:33 -05:00
|
|
|
for the controllers will be named <code>mackie control in/out</code> for
|
|
|
|
the master, <code>mackie control in/out ext #*</code> where * is the
|
|
|
|
position of the extender from left to right. So for a master in the middle
|
|
|
|
with an extender on either side, the ports from left to right will be
|
|
|
|
mackie control in/out ext #1, mackie control in/out and mackie control in/out ext #3.
|
|
|
|
</p>
|
|
|
|
<p>
|
|
|
|
If using the MCP GUI to connect surfaces the top surface is the leftmost
|
|
|
|
and the bottom is the rightmost. At the time of writing the top is always
|
|
|
|
labeled as the main (master) surface even if the leftmost surface is an
|
|
|
|
extender.
|
2015-08-04 20:06:04 -04:00
|
|
|
</p>
|
|
|
|
<p>
|
2015-08-22 11:02:50 -04:00
|
|
|
The <code>MasterPosition</code> value is the port number the master unit
|
|
|
|
(with the master fader) is connected to. So if there are three surfaces,
|
|
|
|
<code><MasterPosition value="1"/></code> will expect the master on
|
|
|
|
the left, <code><MasterPosition value="2"/></code> would be master
|
|
|
|
in the middle and <code><MasterPosition value="3"/></code> would be
|
2017-01-27 23:45:33 -05:00
|
|
|
master on the right.
|
2015-08-04 20:06:04 -04:00
|
|
|
</p>
|
|
|
|
<p class="note">
|
|
|
|
The default value of <code><MasterPosition value="0"/></code> has
|
|
|
|
the same effect as <code><MasterPosition value="1"/></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>
|