<dt class="sub1">Lower</dt><dd>Makes the selected region(s) one layer lower</dd>
<dt class="sub1">Lower to Bottom</dt><dd>Sends the selected region to the background</dd>
<dt>MIDI</dt>
- <dt class="sub1">Transpose...</dt><dd>On a MIDI region, shows the <a href="/editing-and-arranging/edit-midi/transpose-midi/"><kbd class="menu">Transpose MIDI</kbd> window</a>, allowing to shift the pitch of the whole MIDI region by ± <em>n</em> semitones or octaves</dd>
+ <dt class="sub1">Transpose...</dt><dd>On a MIDI region, shows the <a href="/working-with-midi/transpose-midi/"><kbd class="menu">Transpose MIDI</kbd> window</a>, allowing to shift the pitch of the whole MIDI region by ± <em>n</em> semitones or octaves</dd>
<dt class="sub1">Insert Patch Change...</dt><dd>Inserts a patch change at the Edit Point, allowing a change of patch, channel, program and/or bank</dd>
- <dt class="sub1">Quantize...</dt><dd>Shows the <a href="/editing-and-arranging/edit-midi/quantize-midi/"><kbd class="menu">Quantize</kbd> window</a>, allowing to perfectly align the MIDI notes to the musical grid</dd>
+ <dt class="sub1">Quantize...</dt><dd>Shows the <a href="/working-with-midi/quantize-midi/"><kbd class="menu">Quantize</kbd> window</a>, allowing to perfectly align the MIDI notes to the musical grid</dd>
<dt class="sub1">Legatize</dt><dd>Shortens or elongates the MIDI notes to make them perfectly sequentials, i.e. the end of a note is the start of the following one</dd>
<dt class="sub1">Remove Overlap</dt><dd>FIXME Shortens or elongates the MIDI notes to make them perfectly sequentials, i.e. the end of a note is the start of the following one</dd>
- <dt class="sub1">Transform...</dt><dd><a href="/editing-and-arranging/edit-midi/transformation-midi/"><kbd class="menu">Transform</kbd> window</a>, that allows for mathematical operations on the midi notes</dd>
+ <dt class="sub1">Transform...</dt><dd><a href="/working-with-midi/transformation-midi/"><kbd class="menu">Transform</kbd> window</a>, that allows for mathematical operations on the midi notes</dd>
<dt class="sub1">Unlink from Other copies</dt><dd>Makes the selected MIDI region independant, e.g. editing this region won't affect any other one.</dd>
<dt class="sub1">List Editor...</dt><dd>Shows the <kbd class="menu">List Editor</kbd> which sequentially lists all the MIDI events in the region, and allows for precise modifications</dd>
<dt>Gain</dt>
<dl>
<dt>Midi Panic</dt><dd>Immediately stops all midi output.</dd>
- <dt>Enable/disable Audio Click</dt><dd>Toggles (on/off) a click track (metronome) along the <a href="/tempo-meter/tempo-and-meter/">tempo</a>. Right clicking brings up the <kbd class="menu">Click</kbd> submenu from the Preferences.</dd>
+ <dt>Enable/disable Audio Click</dt><dd>Toggles (on/off) a click track (metronome) along the <a href="/working-with-tempo-and-meter/">tempo</a>. Right clicking brings up the <kbd class="menu">Click</kbd> submenu from the Preferences.</dd>
<dt>Go to Start of the Session</dt><dd>Jumps back at the beginning of the session, as defined by the <a href="/working-with-markers/">start marker</a>.</dd>
<dt>Go to End of the Session</dt><dd>Jumps forward to the end of the session, as defined by the <a href="/working-with-markers/">end marker</a>.</dd>
<dt>Play Loop Range</dt><dd>Repeats the defined <a href="/controlling-playback/">loop</a> as defined by the <a href="/working-with-markers/loop-range/">Loop range</a>, until the "Stop playback" button is pressed. Clicking the "Play loop Range" button while already active switches to normal Play mode, which exits the loop without stopping and restarting playback.</dd>
<dt><dfn>Location Markers</dfn></dt><dd>is meant to receive any kind of marker, user generated or from Ardour itself.</dd>
</dl>
-<p>Most of the operations on the markers are described in <a href="/working-with-markers/">Working with Markers</a>, while the Meter, Tempo, Bars:Beats and Timecode use are described in <a href="/tempo-meter/tempo-and-meter/">Tempo and Meter</a>.</p>
+<p>Most of the operations on the markers are described in <a href="/working-with-markers/">Working with Markers</a>, while the Meter, Tempo, Bars:Beats and Timecode use are described in <a href="/working-with-tempo-and-meter/">Tempo and Meter</a>.</p>
<p>
- See <a href="/working-with-sessions">Working with Sessions</a> for more
+ See <a href="/working-with-sessions/">Working with Sessions</a> for more
information on snapshots.
</ul>
<p class="note">
- When favorites are added with the <a href="/working-with-plugins/plugin-manager">Plugin Manager</a>, they are appended to the bottom of the list.
+ When favorites are added with the <a href="/working-with-plugins/plugin-manager/">Plugin Manager</a>, they are appended to the bottom of the list.
</p>
clicking on the piano plays the corresponding MIDI note for reference.
</p>
<p>
- To edit the contents of a MIDI track see <a href="/editing-and-arranging/edit-midi/">Edit
+ To edit the contents of a MIDI track see <a href="/working-with-midi/">Edit
MIDI</a>.
</p>
---
layout: default
-title: Edit MIDI
----
+title: Working with MIDI
+---
<p>
- Ardour's handling of <dfn>MIDI editing</dfn> differs from most other DAWs
+ Ardour's handling of <dfn>MIDI editing</dfn> differs from most other DAWs
and MIDI sequencers.
</p>
<h2>Key features of Ardour MIDI handling</h2>
<ul>
<li>
- All editing is done in-place, in-window. There is no separate piano roll
+ All editing is done in-place, in-window. There is no separate piano roll
window or pane. Edit notes right where you see them.
</li>
<li>
- All MIDI I/O is done via JACK for sample accurate timing and maximal
+ All MIDI I/O is done via JACK for sample accurate timing and maximal
efficiency when communicating with external software synthesizers.
</li>
<li>
- Every MIDI track has its own JACK MIDI port for input; it may have an
- arbitrary combination of audio and MIDI outputs, depending on the signal
- processing in the track; the full flexibility of JACK connectivity is
+ Every MIDI track has its own JACK MIDI port for input; it may have an
+ arbitrary combination of audio and MIDI outputs, depending on the signal
+ processing in the track; the full flexibility of JACK connectivity is
present for MIDI just as it is for audio.
</li>
<li>
- Full automation for MIDI tracks, integrated with the handling of all MIDI
+ Full automation for MIDI tracks, integrated with the handling of all MIDI
CC data for each track.
</li>
<li>
- Controllers (CC data) can be set to discrete or continuous modes (the
+ Controllers (CC data) can be set to discrete or continuous modes (the
latter will interpolate between control points and send additional
data).
</li>
There is a Normal and a Percussive mode for note data editing.
</li>
<li>
- The <dfn>scroomer</dfn> is a combination scroll/zoom tool for altering
+ The <dfn>scroomer</dfn> is a combination scroll/zoom tool for altering
the zoom level and range of visible MIDI data.
</li>
</ul>
time.
</li>
<li>
- By default, copying a MIDI region creates a <dfn>deep link</dfn>
- — both regions share the same data source, and edits to the contents of
- one will affect the other. To break this link, select
- <kbd class="menu">MIDI > Unlink from other copies</kbd> from the region
- context menu, after which the selected region(s) will have their own copies
- of <em>only</em> the data that they visually display on screen. You will not
- be able to trim the region back its original length after an Unlink operation,
+ By default, copying a MIDI region creates a <dfn>deep link</dfn>
+ — both regions share the same data source, and edits to the contents of
+ one will affect the other. To break this link, select
+ <kbd class="menu">MIDI > Unlink from other copies</kbd> from the region
+ context menu, after which the selected region(s) will have their own copies
+ of <em>only</em> the data that they visually display on screen. You will not
+ be able to trim the region back its original length after an Unlink operation,
and the operation cannot be undone.
</li>
</ul>
</p>
<p>
Once you have created a region, you will probably want to
- <a href="/editing-and-arranging/edit-midi/add-new-notes/">Add some notes to it</a>.
+ <a href="/working-with-midi/add-new-notes/">Add some notes to it</a>.
</p>
</dl>
<p>
Note that is also a
- <a href="/editing-and-arranging/edit-midi/step-entry/">a step entry editor</a>
+ <a href="/working-with-midi/step-entry/">a step entry editor</a>
allowing you to enter notes from a virtual keyboard and lots more besides.
</p>
---
layout: default
title: Working with Tempo and Meter
-menu_title: Tempo and Meter
+menu_title: Working with Tempo and Meter
---
<p>Tempo and meter belong together. without both, there is no way to know where a beat lies in time.</p>
--- /dev/null
+---
+layout: default
+title: Devices using Mackie/Logic Control Protocol
+menu_title: Mackie/Logic Control Devices
+---
+
+<p>
+ This will walk you through the process of configuring and using
+ a MIDI control surface with Ardour that uses the <dfn>Mackie Control
+ protocol</dfn> (MCP) or <dfn>Logic Control protocol</dfn>. 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.
+</p>
+
+<h2>Enabling Mackie Control in Ardour</h2>
+<p>
+ Navigate to <kbd class="menu">Edit > Preferences > Control Surfaces</kbd>.
+ Double-click on <kbd class="menu">Mackie Control</kbd> to see the setup dialog:
+</p>
+<img src="" alt="Mackie Control Setup Dialog" />
+<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/">
+ 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
+ on the enable checkbox for "Mackie Control".
+</p>
+
+<h2>Connecting control surface and Ardour MIDI ports</h2>
+<p>
+ 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.
+</p>
+<p>
+ 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.
+</p>
+<p>
+ When you have made these connections once, Ardour will recreate them
+ for you in the future, as long as you leave Mackie Control enabled.
+</p>
+
+<h2>Customizing your control surface</h2>
+<p>
+ Every possible Mackie Control button can be bound to any action present
+ in Ardour's GUI. Please check your control surface page for suggestions.
+</p>
+
+<h2>Preparing your device for use with Ardour</h2>
+<p>
+ Most interfaces will require some configuration to send and respond to
+ MCP.
+</p>
+
+<p class="note">
+ When setting up the control surface, do <em>not</em> 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.
+</p>
+
+{% children %}
--- /dev/null
+---
+layout: default
+title: Behringer devices in Mackie/Logic Control Mode
+menu_title: Behringer devices
+---
+
+<h2>Behringer BCF-2000 Faders Controller</h2>
+<p>
+ <img alt="Digramatic Image of the BCF2000"
+ src="/images/BCF2000.png">
+</p>
+<p>
+ 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.
+</p>
+<p>
+ <img alt="Digramatic Image of the BCF2000 in Edit Global Mode"
+ src="/images/BCF2000-EG.png">
+</p>
+
+<p>
+ 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 <dfn>EG</dfn>
+ 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.
+</p>
+ <ul>
+ <li><code>
+ Encoder #1 sets the operating mode and should be set to <dfn>U-1</dfn> or
+ USB mode 1 if using with a USB cable connection.
+ </li></code>
+ <li><code>
+ Encoder #3 sets the foot switch mode and should most likely be set to
+ <dfn>Auto</dfn> to detect how the foot switch is wired.
+ </li></code>
+ <li><code>
+ Encoder #5 sets the device id, if you are using only 1 device the id
+ should be set to <dfn>ID 1</dfn>. If you are using multiple BCF/BCR2000 each
+ device is required to be set up sequentially and one at a time.
+ </li></code>
+ <li><code>
+ Encoder #7 controls the MIDI <dfn>Dead Time</dfn> or the amount of milliseconds
+ after a move has been made that the device ignores further changes, this
+ should be set to <dfn>100</dfn>.
+ </li></code>
+ <li><code>
+ Encoder #8 controls the MIDI message <dfn>Send Interval</dfn> in milliseconds
+ and should be set to <dfn>10</dfn>
+ </li></code>
+ </ul>
+<p>
+ To exit the <dfn>EG</dfn> mode press the <dfn>Exit</dfn> button. The device is now
+ ready to use with Ardour.
+</p>
+
+<h3>Modes of Operation</h3>
+<p>
+ <img alt="Digramatic Image of the BCF2000 Control Modes"
+ src="/images/BCF2000-Modes.png">
+</p>
+<p>
+ 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.
+</p>
+<p>
+The surface can be broken into 8 groups of controls.
+</p>
+
+<ol>
+ <li>The rotary encoders at the top of the device</li>
+ <li>The first row of buttons under the encoders</li>
+ <li>The second row of buttons under the encoders</li>
+ <li>The row of motorized faders<li>
+ <li>
+ The group of 4 buttons at the top right that will be
+ referred to here as the <dfn>Shift Group</dfn>
+ </li>
+ <li>
+ The group of 4 buttons under the <dfn>Shift Group</dfn>
+ referred to here as the <dfn>Mode Group</dfn>
+ </li>
+ <li>
+ The group of 2 buttons under the <dfn>Mode Group</dfn>
+ referred to here as the <dfn>Select Group</dfn>
+ </li>
+ <li>
+ The group of 4 buttons under the <dfn>Select Group</dfn>
+ referred to here as the <dfn>Transport Group</dfn>
+ </li>
+</ol>
+
+<h3>Mixer Pan Mode</h3>
+<p>
+ <img alt="Digramatic Image of the BCF2000 Control Modes"
+ src="/images/BCF2000-Pan.png">
+</p>
+<p>
+ 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.
+</p>
+<dl>
+ <dt>Encoders</dt>
+ <dd>Mixer Pans. The red LEDs show the amount of pan left or right</dd>
+ <dt>First Row of Buttons</dt>
+ <dd>Mixer Mutes. The button led lights if the track is currently muted</dd>
+ <dt>Second Row of Buttons</dt>
+ <dd>Select Active Track/Bus. Currently selected track/bus is indicated by the button led</dd>
+ <dt>Faders</dt>
+ <dd>Mixer Gains</dd>
+ <dt>Shift Group</dt>
+ <dd>
+ The top and bottom left buttons are the simply shifts to change the function of other buttons
+ </dd>
+ <dd>
+ The top right is the <dfn>Fine Control</dfn> 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.
+ </dd>
+ <dd>
+ The bottom right is the <dfn>Global Shift</dfn> 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.
+ </dd>
+ <dt>Mode Group</dt>
+ <dd>The top two buttons functions are not currently implemented in Ardour.</dd>
+ <dd>The bottom left button sets the device to <dfn>Pan</dfn> mode and should currently be lit</dd>
+ <dd>
+ The bottom right button sets the device to <dfn>Send</dfn> mode but will only allow the switch
+ if the currently selected track/bus has a send or sends to control.
+ </dd>
+ <dt>Select Group</dt>
+ <dd>
+ 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.
+ </dd>
+ <dt>Transport Group</dt>
+ <dd>The upper left button controls <dfn>Rewind<dfn>.
+ <dd>The upper right button controls <dfn>Fast Foreword</dfn>
+ <dd>The lower left button controls stop</dd>
+ <dd>The lower right button controls play</dd>
+</dl>
+<h3>Send Mode</h3>
+<p>
+ <img alt="Digramatic Image of the Send Mode"
+ src="/images/BCF2000-Send.png">
+</p>
+<p>
+ 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.
+</p>
+<dl>
+ <dt>Encoders</dt>
+ <dd>
+ 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 <dfn>FLIP</dfn> is pressed
+ the encoder will control the mixer gain for the selected track/bus.
+ </dd>
+ <dt>First row of buttons</dt>
+ <dd>No Change</dd>
+ <dt>Second row of buttons</dt>
+ <dd>No Change.</dd>
+ <dt>Faders</dt>
+ <dd>
+ No change unless <dfn>FLIP</dfn>is pressed then it controls the send for the selected track/bus.
+ </dd>
+ <dt>Shift Group</dt>
+ <dd>No Change</dd>
+ <dt>Select Group</dt>
+ <dd>No Change</dd>
+ <dt>Transport Group</dt>
+ <dd>No Change</dd>
+</dl>
+<h3>Mixer Pan While Holding Shift 1</h3>
+<p>
+ <img alt="Digramatic Image of the Mixer Mode while holding down shift 1"
+ src="/images/BCF2000-Shift1.png">
+</p>
+<p>
+ The operations of various buttons change while holding down the <dfn>Shift 1</dfn> button
+</p>
+<dl>
+ <dt>Encoders</dt>
+ <dd>No Change</dd>
+ <dt>First row of buttons</dt>
+ <dd>These now control the Soloing of each track/bus in the current bank</dd>
+ <dt>Second row of buttons</dt>
+ <dd>These now control the Enable Record for each track</dd>
+ <dt>Faders</dt>
+ <dd>No Change</dd>
+ <dt>Shift Group</dt>
+ <dd>No change</dd>
+ <dt>Mode Group</dt>
+ <dd>No Change</dd>
+ <dt>Select Group</dt>
+ <dd>
+ 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.
+ </dd>
+ <dt>Transport Group</dt>
+ <dd>The upper left now controls turning on and off <dfn>Loop</dfn> mode.</dd>
+ <dd>
+ The upper right now toggles
+ <dfn>Click</dfn>.
+ </dd>
+ <dd>The lower left toggles <dfn>Replace</dfn>.</dd>
+ <dd>
+ The lower right toggles
+ <dfn>Global Record</dfn>.
+ </dd>
+</dl>
+<h3>Mixer Pan While Holding Shift 2</h3>
+<p>
+ <img alt="Digramatic Image of the Mixer Mode while holding down shift 2"
+ src="/images/BCF2000-Shift2.png">
+</p>
+<p>
+ The operations of various buttons change while holding down the <dfn>Shift 2</dfn> button
+</p>
+<dl>
+ <dt>Encoders</dt>
+ <dd>No Change</dd>
+ <dt>First row of buttons</dt>
+ <dd>FIX ME</dd>
+ <dt>Second row of buttons</dt>
+ <dd>These now control setting up different <dfn>Views</dfn>. See bellow for more info</dd>
+ <dt>Faders</dt>
+ <dd>No Change</dd>
+ <dt>Shift Group</dt>
+ <dd>No change</dd>
+ <dt>Mode Group</dt>
+ <dd>No Change</dd>
+ <dt>Select Group</dt>
+ <dd>Left button controls <dfn>Undo</dfn>(NEEDS VERIFIED)</dd>
+ <dt>Transport Group</dt>
+ <dd>FIX ME</dd>
+ <dd>FIX ME</dd>
+ <dd>FIX ME</dd>
+ <dd>FIX ME</dd>
+</dl>
+<h3>Views</h3>
+<p>
+ <img alt="Digramatic Image of the LED display for different Views"
+ src="/images/BCF2000-Views.png">
+</p>
+<p>
+ FIX ME
+</p>
\ No newline at end of file
--- /dev/null
+---
+layout: default
+title: SSL Nucleus
+---
+
+<p>
+ 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 <a href="#design">design features</a>
+ (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.
+</p>
+
+<h2>Pre-configuring the Nucleus</h2>
+
+<p>
+ 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).
+</p>
+<p>
+ 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 <a href="https://community.ardour.org/files/ArdourNucleusProfile.zip">the
+ profile</a>
+ and load it to your Nucleus using the <code>Edit Profiles</code>
+ 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. <em>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.</em>
+</p>
+
+<h2>Connecting the Nucleus</h2>
+
+<p>
+ 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.
+</p>
+<p>
+ 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.
+</p>
+<p>
+ 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.
+</p>
+<p>
+ 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.
+</p>
+
+<h3>Connecting via Ardour's own ipMIDI support</h3>
+
+<p class="alert alert-info">
+ 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 <strong>MUST</strong> be
+ configured to offer <strong>ZERO</strong> ports before using this
+ method.
+</p>
+
+<p>
+ Open <code>Preferences > Control Surfaces</code>. Ensure that the
+ Mackie protocol is enabled, then double-click on it to open the
+ Mackie Control setup dialog.
+</p>
+<p>
+ 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).
+</p>
+<p>
+ Communication is automatically established with the Nucleus and you
+ need do nothing more.
+</p>
+<p>
+ If this does not work, then make sure your network cables are
+ properly connected, and that you are <strong>not</strong> running
+ other ipMIDI software on the computer.
+</p>
+
+<h3>Connecting via 3rd party ipMIDI support</h3>
+
+<p class="alert alert-info">
+ This is usable only on computers with 3rd party ipMIDI
+ driver software installed and configured for (at least) 2 ports.
+</p>
+
+<p>
+ Open <code>Preferences > Control Surfaces</code>. Ensure that the
+ Mackie protocol is enabled, then double-click on it to open the
+ Mackie Control setup dialog.
+</p>
+<p>
+ Ensure that the device selected is "SSL Nucleus (via platform MIDI)". The dialog should
+ show four combo/dropdown selectors, labelled (respectively):
+</p>
+ <ul>
+ <li><code>Main Surface receives via</code></li>
+ <li><code>Main Surface sends via</code></li>
+ <li><code>1st extender receives via</code></li>
+ <li><code>1st extender sends via</code></li>
+ </ul>
+<p>
+ You should choose "ipMIDI port 1", "ipMIDI port 1", "ipMIDI port 2"
+ and "ipMIDI port 2" for each of the 4 combo/dropdown selectors.
+</p>
+<p>
+ Communication should be automatically established with the Nucleus.
+</p>
+<p>
+ 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.
+</p>
+
+<h2><a name="design">Nucleus Design Discussion</a></h2>
+
+<p>
+ 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.
+</p>
+
+<h3>Cons</h3>
+<dl>
+ <dt>No Master Faster</dt>
+ <dd>It is not possible to control the level of the Master bus or
+ Monitor section. Really don't know what SSL was thinking here.</dd>
+ <dt>No dedicated rec-enable buttons</dt>
+ <dd>You have to press the "Rec" button and convert the per-strip
+ "Select" buttons into rec-enables</dd>
+ <dt>No dedicated automation buttons</dt>
+ <dd>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.</dd>
+ <dt>No buttons with Mackie-defined "Marker" functionality</dt>
+ <dd>Mackie's design intentions for the interoperation of the
+ Marker, rewind and ffwd buttons requires profile editing in order
+ to function properly.
+ </dd>
+ <dt>No "Dyn" button</dt>
+ <dd>This is hard to assign in an edited profile. To be fair, other
+ Mackie Control devices also lack this button.
+ </dd>
+</dl>
+
+<h3>Pros</h3>
+<dl>
+ <dt>Single cable connectivity</dt>
+ <dd>No need for multiple MIDI cables to get 16 faders</dd>
+ <dt>Broadcast connectivity</dt>
+ <dd>Connecting to multiple computers does not require recabling</dd>
+ <dt>16 faders from a single box</dt>
+ <dd>No need to figure out how to keep extenders together</dd>
+ <dt>Meters separated from displays</dt>
+ <dd>Contrast with the Mackie Control Universal Pro, where meters
+ interfere with the display
+ </dd>
+ <dt>DAW profiles</dt>
+ <dd>Easy to flip profiles for use by different DAWs.</dd>
+</dl>
+
+
+<h3>Ambiguous</h3>
+<dl>
+ <dt>Ability to make buttons generate USB keyboard events</dt>
+ <dd>The extent to which this is useful reflects the target DAWs
+ inability to manage all of its functionality via Mackie Control
+ </dd>
+ <dt>Sophisticated "profile" editing</dt>
+ <dd>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.
+ </dd>
+ <dt>Builtin analog signal path</dt>
+ <dd>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?</dd>
+</dl>
--- /dev/null
+---
+layout: default
+title: Mackie Control Setup on Linux
+---
+
+<h2>Devices using ipMIDI</h2>
+<p>
+ 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.
+</p>
+
+<h2>Devices using conventional MIDI</h2>
+<p>
+ Before attempting to use a Mackie Control device that communicates via
+ a standard MIDI cable or a USB cable, you should ensure that
+ <a href="/setting-up-your-system/setting-up-midi/midi-on-linux/">your Linux
+ MIDI environment is setup</a>.
+</p>
+
--- /dev/null
+---
+layout: default
+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
+ 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.
+</p>
--- /dev/null
+---
+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>
+ <Extenders value="0"/>
+ <MasterPosition value="0"/>
+</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. The MIDI ports
+ for the controllers will be named <code>mackie control #1</code>,
+ <code>mackie control #2</code> and up. The numbers will go from left to
+ right. That is, from lowest number channel to highest.
+</p>
+<p>
+ 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
+ master on the right. So the position matches the port name.
+</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>
+++ /dev/null
----
-layout: default
-title: Working with Tempo and Meter
----
-
-{% children %}
projects / ardour-manual / commitdiff