7 The Nucleus, from Solid State Logic, is a 16 fader Mackie Control
8 device that includes many buttons, separate meters, two LCD displays
9 and other features. The device is not cheap (around US$5000 at the
10 time of writing), and has some <a href="#design">design features</a>
11 (or lack thereof) which some Ardour developers find
12 questionable. Nevertheless, it is a very flexible device, and makes
13 a nice 16 fader surface without the need to somehow attach an
14 extender to your main surface.
17 <h2>Pre-configuring the Nucleus</h2>
20 Your Nucleus comes complete with a number of "profiles" for a few
21 well-known DAWs. At the time of writing it does not include one for
22 Ardour (or related products such as Harrison Mixbus). This is
23 unfortunate because although Ardour could easily be used with any of
24 the existing profiles, one thing they all have in common is a
25 remarkably large of buttons not assigned to Mackie Control
26 functions. This means that using one of them will "waste" the
27 buttons, a resource that the Nucleus is not particularly rich in
28 (compared with some other Mackie Control devices).
31 <h2>Connecting the Nucleus</h2>
34 Unlike most Mackie Control devices, the Nucleus uses an ethernet
35 connection to send and receive the MIDI messages that make up the
36 Mackie Control protocol. Specifically, it uses a technology called
37 "ipMIDI" which essentially "broadcasts" MIDI messages on a local
38 area network, so that any connected devices (computers, control
39 surfaces, tablets etc.) can participate.
42 All other DAWs so far that support the Nucleus have chosen to do so
43 by using a 3rd party MIDI driver called "ipMIDI", which creates a
44 number of "virtual" MIDI ports on your computer. You, the user,
45 tells the DAW which ports to connect to, and ipMIDI takes care of
49 Ardour has builtin ipMIDI support, with no need of any 3rd party
50 packages, and no need to identify the "ports" to connect to in order
51 to communicate with the Nucleus. This makes setting it up a bit
52 easier than most other systems.
55 Unless ... you already installed the ipMIDI driver in order to use
56 some other DAW with your Nucleus. If ipMIDI is configured to create
57 any "ports", it is not possible for Ardour's own ipMIDI support to
58 function. We decided to offer both methods of communicating with
59 your Nucleus. If you regularly use other DAWs, and appreciate having
60 ipMIDI permanently set up to communication with the Nucleus - that's
61 OK, you can tell Ardour to use the ipMIDI driver you already
62 have. But if you're not using other DAWs with the Nucleus (and thus
63 have not installed the ipMIDI driver), then you can ignore the
64 ipMIDI driver entirely, and let Ardour connect directly with no
68 <h3>Connecting via Ardour's own ipMIDI support</h3>
70 <p class="alert alert-info">
71 This is usable only on computers with no 3rd party ipMIDI
72 driver software installed and configured. If you have the OS X or
73 Windows ipMIDI driver from nerds.de, it <strong>MUST</strong> be
74 configured to offer <strong>ZERO</strong> ports before using this
79 Open <code>Preferences > Control Surfaces</code>. Ensure that the
80 Mackie protocol is enabled, then double-click on it to open the
81 Mackie Control setup dialog.
84 Ensure that the device selected is "SSL Nucleus". The dialog should
85 show a single numerical selector control below it, defining the
86 ipMIDI port number to use (it should almost always be left at the
87 default value of 21928).
90 Communication is automatically established with the Nucleus and you
94 If this does not work, then make sure your network cables are
95 properly connected, and that you are <strong>not</strong> running
96 other ipMIDI software on the computer.
99 <h3>Connecting via 3rd party ipMIDI support</h3>
101 <p class="alert alert-info">
102 This is usable only on computers with 3rd party ipMIDI
103 driver software installed and configured for (at least) 2 ports.
107 Open <code>Preferences > Control Surfaces</code>. Ensure that the
108 Mackie protocol is enabled, then double-click on it to open the
109 Mackie Control setup dialog.
112 Ensure that the device selected is "SSL Nucleus (via platform MIDI)". The dialog should
113 show four combo/dropdown selectors, labelled (respectively):
116 <li><code>Main Surface receives via</code></li>
117 <li><code>Main Surface sends via</code></li>
118 <li><code>1st extender receives via</code></li>
119 <li><code>1st extender sends via</code></li>
122 You should choose "ipMIDI port 1", "ipMIDI port 1", "ipMIDI port 2"
123 and "ipMIDI port 2" for each of the 4 combo/dropdown selectors.
126 Communication should be automatically established with the Nucleus.
129 If this does not work, then make sure your network cables are
130 properly connected, and that you are running the approprate ipMIDI
131 driver and have configured it for 2 (or more) ports.
134 <h2><a name="design">Nucleus Design Discussion</a></h2>
137 You might be reading this part of the manual seeking some guidance
138 on whether the Nucleus would make a suitable control surface for
139 your workflows. We don't want to try to answer that question
140 definitively, since the real answer depends on the very specific
141 details of your workflow and situation, but we would like to point
142 out a number of design features of the Nucleus that might change
148 <dt>No Master Faster</dt>
149 <dd>It is not possible to control the level of the Master bus or
150 Monitor section. Really don't know what SSL was thinking here.</dd>
151 <dt>No dedicated rec-enable buttons</dt>
152 <dd>You have to press the "Rec" button and convert the per-strip
153 "Select" buttons into rec-enables</dd>
154 <dt>No dedicated automation buttons</dt>
155 <dd>You have to press the "Auto" button and convert the first 4
156 vpots into 4 automation-related buttons, losing your current view
158 <dt>No buttons with Mackie-defined "Marker" functionality</dt>
159 <dd>Mackie's design intentions for the interoperation of the
160 Marker, rewind and ffwd buttons requires profile editing in order
161 to function properly.
163 <dt>No "Dyn" button</dt>
164 <dd>This is hard to assign in an edited profile. To be fair, other
165 Mackie Control devices also lack this button.
171 <dt>Single cable connectivity</dt>
172 <dd>No need for multiple MIDI cables to get 16 faders</dd>
173 <dt>Broadcast connectivity</dt>
174 <dd>Connecting to multiple computers does not require recabling</dd>
175 <dt>15 faders from a single box</dt>
176 <dd>No need to figure out how to keep extenders together</dd>
177 <dt>Meters separated from displays</dt>
178 <dd>Contrast with the Mackie Control Universal Pro, where meters
179 interfere with the display
181 <dt>DAW profiles</dt>
182 <dd>Easy to flip profiles for use by different DAWs.</dd>
188 <dt>Ability to make buttons generate USB keyboard events</dt>
189 <dd>The extent to which this is useful reflects the target DAWs
190 inability to manage all of its functionality via Mackie Control
192 <dt>Sophisticated "profile" editing</dt>
193 <dd>It is nice to be able to reassign the functionality of most
194 buttons, but this is only necessary because of the relatively few
195 global buttons on the surface.
197 <dt>Builtin analog signal path</dt>
198 <dd>SSL clearly expects users to route audio back from their
199 computer via the Nucleus' own 2 channel output path, and maybe even
200 use the input path as well. They take up a significant amount of
201 surface space with the controls for this signal path, space that
202 could have been used for a master fader or more Mackie Control
203 buttons. The USB audio device requires a proprietary driver, so
204 Linux users can't use this, and OS X/Windows users will have to
205 install a device driver (very odd for a USB audio device these
206 days). The analog path also no doubt adds notable cost to the
207 Nucleus. There's nothing wrong with this feature for users that
208 don't already have a working analog/digital signal path for their
209 computers. But who is going to spend $5000 on a Nucleus that
210 doesn't have this already?</dd>