<p>
The Faderport comes with a single USB socket on the back. Connect a
suitable USB cable from there to a USB port on your computer. As of
- the end of 2015, you should avoid USB3 ports - these cause erratic
+ the end of 2015, you should avoid USB3 ports—these cause erratic
behaviour with the device. This issue might get fixed by Presonus in
the future.
</p>
<p class="well">
Ardour uses the Faderport in what Presonus calls "native" mode. You
- do not need to do anything to enable this - Ardour will set the
+ do not need to do anything to enable this—Ardour will set the
device to be in the correct mode. In native mode, the Faderport
sends and receives ordinary MIDI messages to/from the host, and the
host understands the intended meaning of these messages. We note
this detail to avoid speculation about whether Ardour supports the
- device via the HUI protocol - it does not.
+ device via the HUI protocol—it does not.
<p>
The Faderport will be automatically recognized by your operating
system, and will appear in any of the lists of possible MIDI ports
ports where your Faderport is connected.
</p>
<p>
-<img alt="the Faderport configuration dialog"
- src="/images/faderport_dialog.png">
-</p>
+
+<figure>
+ <img src="/images/faderport_dialog.png" alt="The Faderport configuration dialog">
+ <figcaption>
+ The Faderport configuration dialog
+ </figcaption>
+</figure>
+
<p>
Once you select the input and output port, Ardour will initialize
the Faderport and it will be ready to use. You only need do this
once: once these ports are connected and your session has been
saved, the connections will be made automatically in this and other
future sessions.
+</p>
<p>
You do not need to use the power supply that comes with the
Faderport but without it, the fader will not be motorized. This
The Faderport's controls can be divided into three groups:
<ol>
<li>Global controls such as the transport buttons</li>
-
+
<li>Controls which change the settings for particular track or
bus</li>
-
+
<li>Controls which alter which track or bus is modified by the
per-track/bus controls.</li>
</ol>
<h3>Transport Buttons</h3>
<p>
The transport buttons all work as you would expect.
- <dl>
- <dt>Rewind</dt>
- <dd>
+ <table class="dl">
+ <tr><th>Rewind</th>
+ <td>
<p>
When pressed on its own, starts the transport moving backwards. Successive presses
speed up the "rewind" behaviour.
If pressed while also holding the Shift button, the playhead will
move to the session start marker.
</p>
- </dd>
- <dt>Fast Forward</dt>
- <dd>
+ </td></tr>
+ <tr><th>Fast Forward</th>
+ <td>
<p>
When pressed on its own, starts the transport moving faster than normal. Successive presses
speed up the "fast forward" behaviour.
If pressed while also holding the Shift button, the playhead
will move to the session end marker.
</p>
- </dd>
- <dt>Stop</dt>
- <dd>
+ </td></tr>
+ <tr><th>Stop</th>
+ <td>
Stops the transport. Also used in combination with the Rewind
button to "return to zero".
- </dd>
- <dt>Play</dt>
- <dd>
+ </td></tr>
+ <tr><th>Play</th>
+ <td>
Starts the transport. If pressed while the transport is
already rolling at normal speed, causes the playhead to jump to
the start of the last "roll" and continue rolling ("Poor man's
looping").
- </dd>
- <dt>Record Enable</dt>
- <dd>Toggles the global record enable setting
- </dd>
- </dl>
+ </td></tr>
+ <tr><th>Record Enable</th>
+ <td>Toggles the global record enable setting
+ </td></tr>
+ </table>
</p>
<h3>Other Global Controls</h3>
confusing and it can be hard to find what you're looking
for. However, all possible actions are there, so keep looking!
<p>
- <dl>
- <dt>Mix</dt>
- <dd>
+ <table class="dl">
+ <tr><th>Mix</th>
+ <td>
<p>
Possible actions include:
<ul>
<li>Show/Hide the Editor mixer strip</li>
</ul>
</p>
- </dd>
- <dt>Proj</dt>
- <dd>
+ </td></tr>
+ <tr><th>Proj</th>
+ <td>
<p>
Possible actions include:
<ul>
<li>Zoom out</li>
</ul>
</p>
- </dd>
- <dt>Trns</dt>
- <dd>
+ </td></tr>
+ <tr><th>Trns</th>
+ <td>
<p>
Possible actions include:
<ul>
<li>Set Playhead at current pointer position</li>
</ul>
</p>
- </dd>
- <dt>Undo/Redo</dt>
- <dd>
+ </td></tr>
+ <tr><th>Undo/Redo</th>
+ <td>
Undo Causes the last operation carried out in the editor to be
- undone. When pressed in conjuction with the Shift button, it
- causes the most recent undone operation to be re-done.
- </dd>
- <dt>Punch</dt>
- <dd>
+ undone. When pressed in conjunction with the Shift button, it
+ causes the most recent undone operation to be re-done.
+ </td></tr>
+ <tr><th>Punch</th>
+ <td>
<p>
When pressed on its own, toggles punch recording. If there is no
punch range set for the session, this will do nothing.
When pressed in conjunction with the Shift button, this moves
the playhead to the previous Marker
</p>
- </dd>
- <dt>User</dt>
- <dd>
+ </td></tr>
+ <tr><th>User</th>
+ <td>
<p>
See above. Any and all GUI-initiated actions can be driven with
- by pressing this button on its own, or with a "long" press.
+ by pressing this button on its own, or with a "long" press.
</p>
<p>
When pressed in conjunction with the Shift button, this will move
the playhead to the next marker.
</p>
- </dd>
- <dt>Loop</dt>
- <dd>
+ </td></tr>
+ <tr><th>Loop</th>
+ <td>
<p>
When pressed on its own, this toggles loop playback. If the
Ardour preference "Loop-is-mode" is enabled, this does nothing
create a new (unnamed) marker at the current playhead
position.
</p>
- </dd>
- </dl>
+ </td></tr>
+ </table>
</p>
-
+
<h3>Per-track Controls</h3>
<p>
- <dl>
- <dt>Mute</dt>
- <dd>
+ <table class="dl">
+ <tr><th>Mute</th>
+ <td>
This toggles the mute setting of the currently controlled
track/bus. The button will be lit if the track/bus is muted.
- </dd>
- <dt>Solo</dt>
- <dd>
+ </td></tr>
+ <tr><th>Solo</th>
+ <td>
This toggles the solo (or listen) setting of the currently
controlled track/bus. The button will be lit if the track/bus is
soloed (or set to listen mode).
- </dd>
- <dt>Rec</dt>
- <dd>
+ </td></tr>
+ <tr><th>Rec</th>
+ <td>
This toggles the record-enabled setting of the currently
controlled track/bus. The button will be lit if the track is
record-enabled. This button will do nothing if the Faderport is
controlling a bus.
- </dd>
- <dt>Fader</dt>
- <dd>
+ </td></tr>
+ <tr><th>Fader</th>
+ <td>
The fader controls the gain applied to the currently controlled
track/bus. If the Faderport is powered, changing the gain in
Ardour's GUI or via another control surface, or via automation,
- will result in the fader moving under its own control.
- </dd>
- <dt>Knob/Dial/Encoder</dt>
- <dd>
+ will result in the fader moving under its own control.
+ </td></tr>
+ <tr><th>Knob/Dial/Encoder</th>
+ <td>
<p>
The knob controls 1 or 2 pan settings for the current
controlled track/bus. When used alone, turning the knob controls
in order to modify the input gain for the currently controlled
track.
</p>
- </dd>
- <dt>Read</dt>
- <dd>
+ </td></tr>
+ <tr><th>Read</th>
+ <td>
Enables playback/use of fader automation data by the controlled track/bus.
- </dd>
- <dt>Write</dt>
- <dd>
+ </td></tr>
+ <tr><th>Write</th>
+ <td>
Puts the fader for the controlled track/bus into automation
write mode. While the transport is rolling, all fader changes
will be recorded to the fader automation lane for the relevant track/bus.
- </dd>
- <dt>Touch</dt>
- <dd>
+ </td></tr>
+ <tr><th>Touch</th>
+ <td>
Puts the fader for the controlled track/bus into automation
touch mode. While the transport is rolling, touching the fader
will initiate recording all fader changes until the fader is
released. When the fader is not being touched, existing
automation data will be played/used to control the gain level.
- </dd>
- <dt>Off</dt>
- <dd>
+ </td></tr>
+ <tr><th>Off</th>
+ <td>
This disables all automation modes for the currently controlled
track/bus. Existing automation data will be left unmodified by
any fader changes, and will not be used for controlling gain.
- </dd>
- </dl>
+ </td></tr>
+ </table>
</p>
<h3>Track Selection Controls</h3>
track and <em>only</em> that track/bus.
</p>
<p>
- <dl>
- <dt>Left (arrow)</dt>
- <dd>
+ <table class="dl">
+ <tr><th>Left (arrow)</th>
+ <td>
This causes the Ardour GUI to select the previous track/bus
(using the current visual order in the editor window), which
will in turn cause the Faderport to control that track. If there
is no previous track/bus, the selected track/bus is left
unchanged, and the Faderport continues to control it.
- </dd>
- <dt>Right (arrow)</dt>
- <dd>
+ </td></tr>
+ <tr><th>Right (arrow)</th>
+ <td>
This causes the Ardour GUI to select the next track/bus
(using the current visual order in the editor window), which
will in turn cause the Faderport to control that track. If there
is no next track/bus, the selected track/bus is left
unchanged, and the Faderport continues to control it.
- </dd>
- <dt>Output</dt>
- <dd>
+ </td></tr>
+ <tr><th>Output</th>
+ <td>
<p>
Pressing the Output button causes the Faderport to control
the fader, pan, mute and solo settings of the Master bus. If
your session does not contain a Master bus, it does nothing.
- This is a toggle button - pressing it again returns Faderport
+ This is a toggle button—pressing it again returns Faderport
to controlling whichever track/bus was selected before the
first press of the Output button.
</p>
where it is no longer apparent what is being controlled and
what will happen if you try to change it.
</p>
- </dd>
- <dt>Bank</dt>
- <dd>
+ </td></tr>
+ <tr><th>Bank</th>
+ <td>
The "Bank" button is currently not used by Ardour
- </dd>
- </dl>
+ </td></tr>
+ </table>
</p>
projects / ardour-manual / blobdiff