From c37b2ffd6eddf5ec4f30348dff557edc0388c723 Mon Sep 17 00:00:00 2001 From: Len Ovens Date: Fri, 27 Jan 2017 09:34:40 -0800 Subject: [PATCH] MCP fix directory mess made by last few commits --- ...es-using-mackielogic-control-protocol.html | 67 ----- ...r-devices-in-mackielogic-control-mode.html | 262 ------------------ .../02_ssl-nucleus.html | 219 --------------- .../03_mackie-control-setup-on-linux.html | 20 -- .../04_devices-not-listed.html | 18 -- .../05_working-with-extenders.html | 49 ---- .../02_mackie-control-protocol.html | 0 .../01_mackie-control-configure.html | 0 .../02_ssl-nucleus.html | 0 ...r-devices-in-mackielogic-control-mode.html | 0 .../04_devices-not-listed.html | 0 .../05_working-with-extenders.html | 0 12 files changed, 635 deletions(-) delete mode 100644 _manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html delete mode 100644 _manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/01_behringer-devices-in-mackielogic-control-mode.html delete mode 100644 _manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/02_ssl-nucleus.html delete mode 100644 _manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/03_mackie-control-setup-on-linux.html delete mode 100644 _manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices-not-listed.html delete mode 100644 _manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working-with-extenders.html rename _manual/{23_using-control-surfaces => 25_using-control-surfaces}/02_mackie-control-protocol.html (100%) rename _manual/{23_using-control-surfaces => 25_using-control-surfaces}/02_mackie-control-protocol/01_mackie-control-configure.html (100%) rename _manual/{23_using-control-surfaces => 25_using-control-surfaces}/02_mackie-control-protocol/02_ssl-nucleus.html (100%) rename _manual/{23_using-control-surfaces => 25_using-control-surfaces}/02_mackie-control-protocol/03_behringer-devices-in-mackielogic-control-mode.html (100%) rename _manual/{23_using-control-surfaces => 25_using-control-surfaces}/02_mackie-control-protocol/04_devices-not-listed.html (100%) rename _manual/{23_using-control-surfaces => 25_using-control-surfaces}/02_mackie-control-protocol/05_working-with-extenders.html (100%) diff --git a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html b/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html deleted file mode 100644 index 55fe0b6..0000000 --- a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol.html +++ /dev/null @@ -1,67 +0,0 @@ ---- -layout: default -title: Devices using Mackie/Logic Control Protocol -menu_title: Mackie/Logic Control Devices ---- - -

- 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, - and Steinberg CMC devices. -

- -

Enabling Mackie Control in Ardour

-

- Navigate to Edit > Preferences > Control Surfaces. - Double-click on Mackie Control to see the setup dialog: -

-Mackie Control Setup Dialog -

- 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 - on the enable checkbox for "Mackie Control". -

- -

Connecting control surface and Ardour MIDI ports

-

- 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 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 - for you in the future, as long as you leave Mackie Control enabled. -

- -

Customizing your control surface

-

- Every possible Mackie Control button can be bound to any action present - in Ardour's GUI. Please check your control surface page for suggestions. -

- -

Preparing your device for use with Ardour

-

- 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. -

- -{% children %} diff --git a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/01_behringer-devices-in-mackielogic-control-mode.html b/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/01_behringer-devices-in-mackielogic-control-mode.html deleted file mode 100644 index 39d0ce5..0000000 --- a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/01_behringer-devices-in-mackielogic-control-mode.html +++ /dev/null @@ -1,262 +0,0 @@ ---- -layout: default -title: Behringer devices in Mackie/Logic Control Mode -menu_title: Behringer devices ---- - -

Behringer BCF-2000 Faders Controller

-

- Digramatic Image of the BCF2000 -

-

- The Behringer BCF-2000 Fader Controller is a control surface with 8 motorized - faders, 8 rotary encoders and 30 push buttons. The device is a class - compliant USB Midi Interface and also has standard Midi DIN IN/OUT/THRU ports. - The device has included a Mackie/Logic Control Emulation Mode since firmware v1.06. - If you're devices firmware is older than v1.06 it will require an update before - Mackie Control Emulation will work as described here. -

-

- Digramatic Image of the BCF2000 in Edit Global Mode -

- -

- In order to put the controller into Mackie/Logic control mode turn on the - unit while holding third button from the left in the top most row - of buttons (under the rotary encoder row). Hold the button down until EG - or edit global mode is displayed on the LCD screen of the unit. The global parameters - can then be edited using the 8 rotary encoders in the top row. -

- -

- To exit the EG mode press the Exit button. The device is now - ready to use with Ardour. -

- -

Modes of Operation

-

- Digramatic Image of the BCF2000 Control Modes -

-

- The four buttons arranged in a rectangle and located under the Behringer logo - are the mode selection buttons in Logic Control Emulation Mode, - currently Ardour has implemented support for two of these modes. -

-

-The surface can be broken into 8 groups of controls. -

- -
    -
  1. The rotary encoders at the top of the device
    2. -
  2. The first row of buttons under the encoders
    3. -
  3. The second row of buttons under the encoders
    4. -
  4. The row of motorized faders
  5. -
  6. - The group of 4 buttons at the top right that will be - referred to here as the Shift Group -
    7. -
  7. - The group of 4 buttons under the Shift Group - referred to here as the Mode Group -
    8. -
  8. - The group of 2 buttons under the Mode Group - referred to here as the Select Group -
    9. -
  9. - The group of 4 buttons under the Select Group - referred to here as the Transport Group -
    10. -
- -

Mixer Pan Mode

-

- Digramatic Image of the BCF2000 Control Modes -

-

- This is the standard work mode that organizes the control surface to emulate - a standard mixer layout where controls for each track/bus are arranged vertically. - The order of the faders is either controlled by the order of the tracks in the - mixer or can be set manually by the user. -

-
-
Encoders
-
Mixer Pans. The red LEDs show the amount of pan left or right
-
First Row of Buttons
-
Mixer Mutes. The button led lights if the track is currently muted
-
Second Row of Buttons
-
Select Active Track/Bus. Currently selected track/bus is indicated by the button led
-
Faders
-
Mixer Gains
-
Shift Group
-
- The top and bottom left buttons are the simply shifts to change the function of other buttons -
-
- The top right is the Fine Control button that allows the increment values sent by - by rotary encoders and faders to be a small value for more precise editing. This button - can also act as a shift button. -
-
- The bottom right is the Global Shift button that allows you to change back to the - standard Mixer Pan view from other views and modes. This button can also act as a shift button. -
-
Mode Group
-
The top two buttons functions are not currently implemented in Ardour.
-
The bottom left button sets the device to Pan mode and should currently be lit
-
- The bottom right button sets the device to Send mode but will only allow the switch - if the currently selected track/bus has a send or sends to control. -
-
Select Group
-
- In this mode they function as bank select left and right. If your session has more than 8 tracks - the next set of 8 tracks is selected with the right button and the faders will move to match the - current gain settings of that bank of 8 tracks/busses. If the last bank contains less than 8 - tracks/busses the unused faders will move to the bottom and the pan lights will all turn - off. An unlimited amount of tracks can be controlled with the device. -
-
Transport Group
-
The upper left button controls Rewind. -
The upper right button controls Fast Foreword -
The lower left button controls stop
-
The lower right button controls play
-
-

Send Mode

-

- Digramatic Image of the Send Mode -

-

- Send mode allows for the top row of encoders to control the sends for a selected channel. - One interesting option is to flip the controls from the encoders to the faders by pressing - the shift 1 button and the global view button at the same time. -

-
-
Encoders
-
- In send mode, the encoders control sends from left to right instead of mixer pans. - If there are less than 8 sends the behavior of the encoder will be to continue controlling - the mixer pan. Visually it's indicated by the change in the LED from originating at the 12 - o'clock position to originating at the 7 o'clock position. If FLIP is pressed - the encoder will control the mixer gain for the selected track/bus. -
-
First row of buttons
-
No Change
-
Second row of buttons
-
No Change.
-
Faders
-
- No change unless FLIPis pressed then it controls the send for the selected track/bus. -
-
Shift Group
-
No Change
-
Select Group
-
No Change
-
Transport Group
-
No Change
-
-

Mixer Pan While Holding Shift 1

-

- Digramatic Image of the Mixer Mode while holding down shift 1 -

-

- The operations of various buttons change while holding down the Shift 1 button -

-
-
Encoders
-
No Change
-
First row of buttons
-
These now control the Soloing of each track/bus in the current bank
-
Second row of buttons
-
These now control the Enable Record for each track
-
Faders
-
No Change
-
Shift Group
-
No change
-
Mode Group
-
No Change
-
Select Group
-
- These now change the current bank of tracks being controlled over by - one. So if you where controlling tracks 1-8 a push the right - button the surface would now control tracks 2-9 pressing the left - would then shift back to controlling tracks 1-8. -
-
Transport Group
-
The upper left now controls turning on and off Loop mode.
-
- The upper right now toggles - Click. -
-
The lower left toggles Replace.
-
- The lower right toggles - Global Record. -
-
-

Mixer Pan While Holding Shift 2

-

- Digramatic Image of the Mixer Mode while holding down shift 2 -

-

- The operations of various buttons change while holding down the Shift 2 button -

-
-
Encoders
-
No Change
-
First row of buttons
-
FIX ME
-
Second row of buttons
-
These now control setting up different Views. See bellow for more info
-
Faders
-
No Change
-
Shift Group
-
No change
-
Mode Group
-
No Change
-
Select Group
-
Left button controls Undo(NEEDS VERIFIED)
-
Transport Group
-
FIX ME
-
FIX ME
-
FIX ME
-
FIX ME
-
-

Views

-

- Digramatic Image of the LED display for different Views -

-

- FIX ME -

\ No newline at end of file diff --git a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/02_ssl-nucleus.html b/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/02_ssl-nucleus.html deleted file mode 100644 index 83c98e2..0000000 --- a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/02_ssl-nucleus.html +++ /dev/null @@ -1,219 +0,0 @@ ---- -layout: default -title: SSL Nucleus ---- - -

- The Nucleus, from Solid State Logic, is a 16 fader Mackie Control - device that includes many buttons, separate meters, two LCD displays - and other features. The device is not cheap (around US$5000 at the - time of writing), and has some design features - (or lack thereof) which some Ardour developers find - questionable. Nevertheless, it is a very flexible device, and makes - a nice 16 fader surface without the need to somehow attach an - extender to your main surface. -

- -

Pre-configuring the Nucleus

- -

- Your Nucleus comes complete with a number of "profiles" for a few - well-known DAWs. At the time of writing it does not include one for - Ardour (or related products such as Harrison Mixbus). -

-

- We have prepared a profile in which as many buttons as possible send - Mackie Control messages, which makes the device maximally useful - with Ardour (and Mixbus). You can - download the - profile - and load it to your Nucleus using the Edit Profiles - button in SSL's Nucleus Remote application. Be sure to select it for - the active DAW layer in order to make Ardour work as well as - possible. Note: unfortunately, the Nucleus Remote application - only runs on OS X or Windows, so Linux users will need access to - another system to load the profile. We will provide notes on the - profile settings at a future time. -

- -

Connecting the Nucleus

- -

- Unlike most Mackie Control devices, the Nucleus uses an ethernet - connection to send and receive the MIDI messages that make up the - Mackie Control protocol. Specifically, it uses a technology called - "ipMIDI" which essentially "broadcasts" MIDI messages on a local - area network, so that any connected devices (computers, control - surfaces, tablets etc.) can participate. -

-

- All other DAWs so far that support the Nucleus have chosen to do so - by using a 3rd party MIDI driver called "ipMIDI", which creates a - number of "virtual" MIDI ports on your computer. You, the user, - tells the DAW which ports to connect to, and ipMIDI takes care of - the rest. -

-

- Ardour has builtin ipMIDI support, with no need of any 3rd party - packages, and no need to identify the "ports" to connect to in order - to communicate with the Nucleus. This makes setting it up a bit - easier than most other systems. -

-

- Unless ... you already installed the ipMIDI driver in order to use - some other DAW with your Nucleus. If ipMIDI is configured to create - any "ports", it is not possible for Ardour's own ipMIDI support to - function. We decided to offer both methods of communicating with - your Nucleus. If you regularly use other DAWs, and appreciate having - ipMIDI permanently set up to communication with the Nucleus - that's - OK, you can tell Ardour to use the ipMIDI driver you already - have. But if you're not using other DAWs with the Nucleus (and thus - have not installed the ipMIDI driver), then you can ignore the - ipMIDI driver entirely, and let Ardour connect directly with no - configuration. -

- -

Connecting via Ardour's own ipMIDI support

- -

- This is usable only on computers with no 3rd party ipMIDI - driver software installed and configured. If you have the OS X or - Windows ipMIDI driver from nerds.de, it MUST be - configured to offer ZERO ports before using this - method. -

- -

- Open Preferences > Control Surfaces. Ensure that the - Mackie protocol is enabled, then double-click on it to open the - Mackie Control setup dialog. -

-

- Ensure that the device selected is "SSL Nucleus". The dialog should - show a single numerical selector control below it, defining the - ipMIDI port number to use (it should almost always be left at the - default value of 21928). -

-

- Communication is automatically established with the Nucleus and you - need do nothing more. -

-

- If this does not work, then make sure your network cables are - properly connected, and that you are not running - other ipMIDI software on the computer. -

- -

Connecting via 3rd party ipMIDI support

- -

- This is usable only on computers with 3rd party ipMIDI - driver software installed and configured for (at least) 2 ports. -

- -

- Open Preferences > Control Surfaces. Ensure that the - Mackie protocol is enabled, then double-click on it to open the - Mackie Control setup dialog. -

-

- Ensure that the device selected is "SSL Nucleus (via platform MIDI)". The dialog should - show four combo/dropdown selectors, labelled (respectively): -

- -

- You should choose "ipMIDI port 1", "ipMIDI port 1", "ipMIDI port 2" - and "ipMIDI port 2" for each of the 4 combo/dropdown selectors. -

-

- Communication should be automatically established with the Nucleus. -

-

- If this does not work, then make sure your network cables are - properly connected, and that you are running the approprate ipMIDI - driver and have configured it for 2 (or more) ports. -

- -

Nucleus Design Discussion

- -

- You might be reading this part of the manual seeking some guidance - on whether the Nucleus would make a suitable control surface for - your workflows. We don't want to try to answer that question - definitively, since the real answer depends on the very specific - details of your workflow and situation, but we would like to point - out a number of design features of the Nucleus that might change - your opinion. -

- -

Cons

-
-
No Master Faster
-
It is not possible to control the level of the Master bus or - Monitor section. Really don't know what SSL was thinking here.
-
No dedicated rec-enable buttons
-
You have to press the "Rec" button and convert the per-strip - "Select" buttons into rec-enables
-
No dedicated automation buttons
-
You have to press the "Auto" button and convert the first 4 - vpots into 4 automation-related buttons, losing your current view - of the session.
-
No buttons with Mackie-defined "Marker" functionality
-
Mackie's design intentions for the interoperation of the - Marker, rewind and ffwd buttons requires profile editing in order - to function properly. -
-
No "Dyn" button
-
This is hard to assign in an edited profile. To be fair, other - Mackie Control devices also lack this button. -
-
- -

Pros

-
-
Single cable connectivity
-
No need for multiple MIDI cables to get 16 faders
-
Broadcast connectivity
-
Connecting to multiple computers does not require recabling
-
16 faders from a single box
-
No need to figure out how to keep extenders together
-
Meters separated from displays
-
Contrast with the Mackie Control Universal Pro, where meters - interfere with the display -
-
DAW profiles
-
Easy to flip profiles for use by different DAWs.
-
- - -

Ambiguous

-
-
Ability to make buttons generate USB keyboard events
-
The extent to which this is useful reflects the target DAWs - inability to manage all of its functionality via Mackie Control -
-
Sophisticated "profile" editing
-
It is nice to be able to reassign the functionality of most - buttons, but this is only necessary because of the relatively few - global buttons on the surface. -
-
Builtin analog signal path
-
SSL clearly expects users to route audio back from their - computer via the Nucleus' own 2 channel output path, and maybe even - use the input path as well. They take up a significant amount of - surface space with the controls for this signal path, space that - could have been used for a master fader or more Mackie Control - buttons. The USB audio device requires a proprietary driver, so - Linux users can't use this, and OS X/Windows users will have to - install a device driver (very odd for a USB audio device these - days). The analog path also no doubt adds notable cost to the - Nucleus. There's nothing wrong with this feature for users that - don't already have a working analog/digital signal path for their - computers. But who is going to spend $5000 on a Nucleus that - doesn't have this already?
-
diff --git a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/03_mackie-control-setup-on-linux.html b/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/03_mackie-control-setup-on-linux.html deleted file mode 100644 index e155e5a..0000000 --- a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/03_mackie-control-setup-on-linux.html +++ /dev/null @@ -1,20 +0,0 @@ ---- -layout: default -title: Mackie Control Setup on Linux ---- - -

Devices using ipMIDI

-

- 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. -

- -

Devices using conventional MIDI

-

- 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. -

- diff --git a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices-not-listed.html b/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices-not-listed.html deleted file mode 100644 index 579ca6e..0000000 --- a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/04_devices-not-listed.html +++ /dev/null @@ -1,18 +0,0 @@ ---- -layout: default -title: What to do 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/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working-with-extenders.html b/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working-with-extenders.html deleted file mode 100644 index 661d67d..0000000 --- a/_manual/25_using-control-surfaces/02_devices-using-mackielogic-control-protocol/05_working-with-extenders.html +++ /dev/null @@ -1,49 +0,0 @@ ---- -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. -

-

- When an Extenders value of greater than 0 is used, extra midi - ports will appear for the extenders to be connected to. The MIDI ports - for the controllers will be named mackie control #1, - mackie control #2 and up. The numbers will go from left to - right. That is, from lowest number channel to highest. -

-

- The MasterPosition value is the port number the master unit - (with the master fader) is connected to. So if there are three surfaces, - <MasterPosition value="1"/> will expect the master on - the left, <MasterPosition value="2"/> would be master - in the middle and <MasterPosition value="3"/> would be - master on the right. So the position matches the port name. -

-

- The default value of <MasterPosition value="0"/> has - the same effect as <MasterPosition value="1"/>. -

-

- 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. -

diff --git a/_manual/23_using-control-surfaces/02_mackie-control-protocol.html b/_manual/25_using-control-surfaces/02_mackie-control-protocol.html similarity index 100% rename from _manual/23_using-control-surfaces/02_mackie-control-protocol.html rename to _manual/25_using-control-surfaces/02_mackie-control-protocol.html diff --git a/_manual/23_using-control-surfaces/02_mackie-control-protocol/01_mackie-control-configure.html b/_manual/25_using-control-surfaces/02_mackie-control-protocol/01_mackie-control-configure.html similarity index 100% rename from _manual/23_using-control-surfaces/02_mackie-control-protocol/01_mackie-control-configure.html rename to _manual/25_using-control-surfaces/02_mackie-control-protocol/01_mackie-control-configure.html diff --git a/_manual/23_using-control-surfaces/02_mackie-control-protocol/02_ssl-nucleus.html b/_manual/25_using-control-surfaces/02_mackie-control-protocol/02_ssl-nucleus.html similarity index 100% rename from _manual/23_using-control-surfaces/02_mackie-control-protocol/02_ssl-nucleus.html rename to _manual/25_using-control-surfaces/02_mackie-control-protocol/02_ssl-nucleus.html diff --git a/_manual/23_using-control-surfaces/02_mackie-control-protocol/03_behringer-devices-in-mackielogic-control-mode.html b/_manual/25_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_mackie-control-protocol/03_behringer-devices-in-mackielogic-control-mode.html rename to _manual/25_using-control-surfaces/02_mackie-control-protocol/03_behringer-devices-in-mackielogic-control-mode.html diff --git a/_manual/23_using-control-surfaces/02_mackie-control-protocol/04_devices-not-listed.html b/_manual/25_using-control-surfaces/02_mackie-control-protocol/04_devices-not-listed.html similarity index 100% rename from _manual/23_using-control-surfaces/02_mackie-control-protocol/04_devices-not-listed.html rename to _manual/25_using-control-surfaces/02_mackie-control-protocol/04_devices-not-listed.html diff --git a/_manual/23_using-control-surfaces/02_mackie-control-protocol/05_working-with-extenders.html b/_manual/25_using-control-surfaces/02_mackie-control-protocol/05_working-with-extenders.html similarity index 100% rename from _manual/23_using-control-surfaces/02_mackie-control-protocol/05_working-with-extenders.html rename to _manual/25_using-control-surfaces/02_mackie-control-protocol/05_working-with-extenders.html -- 2.37.2