From 7cbfd88cb4bbabef6e78c681b96260ff6a87376a Mon Sep 17 00:00:00 2001
From: Shamus Hammons
- If you are using a device like the SSL Nucleus that uses ipMIDI,
- no set up is required other than to ensure that your control surface
- and computer are both connected to the same network.
-
- Before attempting to use a Mackie Control device that communicates via
- a standard MIDI cable or a USB cable, you should ensure that
- your Linux
- MIDI environment is setup.
-
+ Since Mackie and Logic made the first Logic Control Surface, Mackie
+ and other surface manufactures have been making control surfaces that
+ use the same protocol to communicate with a DAW. Ardour supports the
+ MCP and will
+ work with all these control surfaces.
+
- This will walk you through the process of configuring and using
+ This will walk you through the process of configuring and using
a MIDI control surface with Ardour that uses the Mackie Control
- protocol (MCP) or Logic Control protocol. Devices that
- have been tested and are known to work include the SSL Nucleus, Mackie
- Control Pro (plus extenders), Behringer devices in Mackie/Logic mode,
+ protocol (MCP) or Logic Control protocol. Devices that
+ have been tested and are known to work include the SSL Nucleus, Mackie
+ Control Pro (plus extenders), Behringer devices in Mackie/Logic mode,
and Steinberg CMC devices.
Devices using ipMIDI
-Devices using conventional MIDI
-
- From the selector at the top, choose the type of device you are using. + From the selector at the top, choose the type of device you are using. ( What to do if your device is not listed).
- Once your setup is complete, click "OK" to close the dialog. Now click + Once your setup is complete, click "OK" to close the dialog. Now click on the enable checkbox for "Mackie Control".
- -- If you are using a device that uses ipMIDI, such as the SSL Nucleus, no - MIDI port connections are required — Ardour and your control - surface will be able to talk to each other automatically. + If you are using a device that uses ipMIDI, such as the SSL Nucleus, no + MIDI port connections are required — Ardour and your control + surface will be able to talk to each other automatically so long as + your control surface and computer are both connected to the same network.
+- If you are using a device that uses normal MIDI (via a standard MIDI or - USB cable), you need to connect Ardour's Mackie Control in and out ports + Before attempting to use a Mackie Control device that communicates via + a standard MIDI cable or a USB cable, you should ensure that + your Linux + MIDI environment is setup. + If you are using a device that uses normal MIDI (via a standard MIDI or + USB cable), you need to connect Ardour's Mackie Control in and out ports to the MIDI ports leading to and coming from the control surface.
- When you have made these connections once, Ardour will recreate them + When you have made these connections once, Ardour will recreate them for you in the future, as long as you leave Mackie Control enabled.
- Every possible Mackie Control button can be bound to any action present - in Ardour's GUI. Please check your control surface page for suggestions. + Every possible global Mackie Control button can be bound to any + action present in Ardour's GUI. Please check your control surface + page for suggestions.
- Most interfaces will require some configuration to send and respond to + Most interfaces will require some configuration to send and respond to MCP. -
+When setting up the control surface, do not use "Pro Tools" mode. Pro Tools is the only DAW that still requires HUI. The rest of - world uses Mackie Control Protocol. Ardour does not support HUI. + world uses Mackie Control Protocol. Ardour does not support HUI at + this time.
- -{% children %} diff --git a/_manual/23_using-control-surfaces/02_devices-using-mackielogic-control-protocol/02_ssl-nucleus.html b/_manual/23_using-control-surfaces/02_mackie-control-protocol/02_ssl-nucleus.html similarity index 100% rename from _manual/23_using-control-surfaces/02_devices-using-mackielogic-control-protocol/02_ssl-nucleus.html rename to _manual/23_using-control-surfaces/02_mackie-control-protocol/02_ssl-nucleus.html diff --git a/_manual/23_using-control-surfaces/02_devices-using-mackielogic-control-protocol/01_behringer-devices-in-mackielogic-control-mode.html b/_manual/23_using-control-surfaces/02_mackie-control-protocol/03_behringer-devices-in-mackielogic-control-mode.html similarity index 100% rename from _manual/23_using-control-surfaces/02_devices-using-mackielogic-control-protocol/01_behringer-devices-in-mackielogic-control-mode.html rename to _manual/23_using-control-surfaces/02_mackie-control-protocol/03_behringer-devices-in-mackielogic-control-mode.html diff --git a/_manual/23_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices-not-listed.html b/_manual/23_using-control-surfaces/02_mackie-control-protocol/04_devices-not-listed.html similarity index 100% rename from _manual/23_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices-not-listed.html rename to _manual/23_using-control-surfaces/02_mackie-control-protocol/04_devices-not-listed.html diff --git a/_manual/23_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working-with-extenders.html b/_manual/23_using-control-surfaces/02_mackie-control-protocol/05_working-with-extenders.html similarity index 68% rename from _manual/23_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working-with-extenders.html rename to _manual/23_using-control-surfaces/02_mackie-control-protocol/05_working-with-extenders.html index 661d67d..9f0fe73 100644 --- a/_manual/23_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working-with-extenders.html +++ b/_manual/23_using-control-surfaces/02_mackie-control-protocol/05_working-with-extenders.html @@ -5,21 +5,35 @@ 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 + 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. + The best way is to start with the *.device file that matches your + master device 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: + The three lines of interest are:
+ <Name value="Device name"/> <Extenders value="0"/> <MasterPosition value="0"/>
- Add these two lines if they are not present. The Extenders
+ Add any lines that are not present.
+
+ The Name
value should be a unique name so it is obvious
+ in the list of devices.
+
+ The Extenders
value is the number of extenders used and should not include the master in
that number.