</p>
<p>
If this does not work, then make sure your network cables are
- properly connected, and that you are running the approprate ipMIDI
+ properly connected, and that you are running the appropriate ipMIDI
driver and have configured it for 2 (or more) ports.
</p>
</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
+<table class="dl">
+ <tr><th>No Master Faster</th>
+ <td>It is not possible to control the level of the Master bus or
+ Monitor section. Really don't know what SSL was thinking here.</td></tr>
+ <tr><th>No dedicated rec-enable buttons</th>
+ <td>You have to press the "Rec" button and convert the per-strip
+ "Select" buttons into rec-enables</td></tr>
+ <tr><th>No dedicated automation buttons</th>
+ <td>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
+ of the session.</td></tr>
+ <tr><th>No buttons with Mackie-defined "Marker" functionality</th>
+ <td>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
+ </td></tr>
+ <tr><th>No "Dyn" button</th>
+ <td>This is hard to assign in an edited profile. To be fair, other
Mackie Control devices also lack this button.
- </dd>
-</dl>
+ </td></tr>
+</table>
<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
+<table class="dl">
+ <tr><th>Single cable connectivity</th>
+ <td>No need for multiple MIDI cables to get 16 faders</td></tr>
+ <tr><th>Broadcast connectivity</th>
+ <td>Connecting to multiple computers does not require recabling</td></tr>
+ <tr><th>16 faders from a single box</th>
+ <td>No need to figure out how to keep extenders together</td></tr>
+ <tr><th>Meters separated from displays</th>
+ <td>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>
+ </td></tr>
+ <tr><th>DAW profiles</th>
+ <td>Easy to flip profiles for use by different DAWs.</td></tr>
+</table>
<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
+<table class="dl">
+ <tr><th>Ability to make buttons generate USB keyboard events</th>
+ <td>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
+ </td></tr>
+ <tr><th>Sophisticated "profile" editing</th>
+ <td>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
+ </td></tr>
+ <tr><th>Builtin analog signal path</th>
+ <td>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
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>
+ doesn't have this already?</td></tr>
+</table>
projects / ardour-manual / blobdiff