OSC: more gain changes...

[ardour-manual-diverged] / _manual / 22_using-control-surfaces / 05_Presonus_FaderPort.html

diff --git a/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html b/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html
index a07687beb56d39ab2ab1bd63a6b911ccc3de7d40..9acf3747576df763a6cbe27099bb45197b574830 100644 (file)
--- a/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html
+++ b/_manual/22_using-control-surfaces/05_Presonus_FaderPort.html
@@ -21,7 +21,7 @@ menu_title: Presonus Faderport
   behaviour with the device. This issue might get fixed by Presonus in
   the future.
 </p>
   behaviour with the device. This issue might get fixed by Presonus in
   the future.
 </p>

-<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
   device to be in the correct mode. In native mode, the Faderport
   Ardour uses the Faderport in what Presonus calls "native" mode. You
   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


@@ -43,7 +43,10 @@ menu_title: Presonus Faderport
   two dropdown selectors that will allow you to identify the MIDI
   ports where your Faderport is connected.
 </p>
   two dropdown selectors that will allow you to identify the MIDI
   ports where your Faderport is connected.
 </p>

-<img alt="the Faderport configuration dialog" src="images/faderport_dialog.png">
+<p>
+<img alt="the Faderport configuration dialog"
+     src="/images/faderport_dialog.png">
+</p>

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


@@ -84,15 +87,30 @@ menu_title: Presonus Faderport
   The transport buttons all work as you would expect.
   <dl>
     <dt>Rewind</dt>
   The transport buttons all work as you would expect.
   <dl>
     <dt>Rewind</dt>

-    <dd>Starts the transport moving backwards. Successive presses
+    <dd>
+      <p>
+      When pressed on its own, starts the transport moving backwards. Successive presses

       speed up the "rewind" behaviour.
       speed up the "rewind" behaviour.

-      <br>
-      If pressed while also holding the Stop button, the playhead will
-      return to the zero position on the timeline.
+      </p>
+      <p>
+       If pressed while also holding the Stop button, the playhead will
+       return to the zero position on the timeline.
+      </p>
+      <p>
+       If pressed while also holding the Shift button, the playhead will
+       move to the session start marker.
+      </p>

     </dd>
     <dt>Fast Forward</dt>
     </dd>
     <dt>Fast Forward</dt>

-    <dd>Starts the transport moving faster than normal. Successive presses
-      speed up the "fast forward" behaviour.
+    <dd>
+      <p>
+       When pressed on its own, starts the transport moving faster than normal. Successive presses
+       speed up the "fast forward" behaviour.
+      </p>
+      <p>
+       If pressed while also holding the Shift button, the playhead
+       will move to the session end marker.
+      </p>

     </dd>
     <dt>Stop</dt>
     <dd>
     </dd>
     <dt>Stop</dt>
     <dd>


@@ -114,13 +132,13 @@ menu_title: Presonus Faderport
 
 <h3>Other Global Controls</h3>
 <p>
 
 <h3>Other Global Controls</h3>
 <p>

-  The Mix, Proj, Trns buttons have no "obvious" functionality
-  that they correspond to in Ardour. We have therefore allowed users
-  to choose from a carefully curated set of possible actions that seem
-  related to the button labels in some clear way. This can be done via
-  the Faderport configuration dialog accessed via <code>Preferences
-  &gt; Control Surfaces</code>. Each button has 3 possible actions
-  associated with it:
+  The Mix, Proj, Trns buttons do not obviously correspond any
+  particular functions or operations in Ardour. We have therefore
+  allowed users to choose from a carefully curated set of possible
+  actions that seem related to the button labels in some clear
+  way. This can be done via the Faderport configuration dialog
+  accessed via <code>Preferences &gt; Control Surfaces</code>. Each
+  button has 3 possible actions associated with it:

   <ul>
     <li>Plain Press: action to be taken when the button is pressed on
       its own.</li>
   <ul>
     <li>Plain Press: action to be taken when the button is pressed on
       its own.</li>


@@ -145,7 +163,8 @@ menu_title: Presonus Faderport
       <p>
        Possible actions include:
        <ul>
       <p>
        Possible actions include:
        <ul>

-         <li></li>
+         <li>Toggle Editor &amp; Mixer visibility</li>
+         <li>Show/Hide the Editor mixer strip</li>

        </ul>
       </p>
     </dd>
        </ul>
       </p>
     </dd>


@@ -154,7 +173,12 @@ menu_title: Presonus Faderport
       <p>
        Possible actions include:
        <ul>
       <p>
        Possible actions include:
        <ul>

-         <li></li>
+         <li>Toggle Meterbridge visibility</li>
+         <li>Toggle Session Summary visibility</li>
+         <li>Toggle Editor Lists visibility</li>
+         <li>Zoom to session</li>
+         <li>Zoom in</li>
+         <li>Zoom out</li>

        </ul>
       </p>
    </dd>
        </ul>
       </p>
    </dd>


@@ -163,7 +187,10 @@ menu_title: Presonus Faderport
       <p>
        Possible actions include:
        <ul>
       <p>
        Possible actions include:
        <ul>

-         <li></li>
+         <li>Toggle Locations window visibility</li>
+         <li>Toggle Metronome</li>
+         <li>Toggle external sync</li>
+         <li>Set Playhead at current pointer position</li>

        </ul>
       </p>
     </dd>
        </ul>
       </p>
     </dd>


@@ -175,20 +202,39 @@ menu_title: Presonus Faderport
     </dd>
     <dt>Punch</dt>
     <dd>
     </dd>
     <dt>Punch</dt>
     <dd>

-      Toggles punch recording. If there is no punch range set for the
-      session, this will do nothing.
+      <p>
+       When pressed on its own, toggles punch recording. If there is no
+       punch range set for the session, this will do nothing.
+      </p>
+      <p>
+       When pressed in conjunction with the Shift button, this moves
+       the playhead to the previous Marker
+      </p>

     </dd>
     <dt>User</dt>
     <dd>
     </dd>
     <dt>User</dt>
     <dd>

-      See above. Any and all GUI-initiated actions can be driven with
-      this button.
+      <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. 
+      </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>
     </dd>
     <dt>Loop</dt>
     <dd>

-      Toggles loop playback. If the Ardour  preference "Loop-is-mode" is
-      enabled, this does nothing to the current transport state. If
-      that preference is disabled, then engaging loop playback will
-      also start the transport.
+      <p>
+       When pressed on its own, this toggles loop playback. If the
+       Ardour preference "Loop-is-mode" is enabled, this does nothing
+       to the current transport state. If that preference is disabled,
+       then engaging loop playback will also start the transport.
+      </p>
+      <p>
+       When pressed in conjunction with the Shift button, this will
+       create a new (unnamed) marker at the current playhead
+       position.
+      </p>

     </dd>
   </dl>
 </p>
     </dd>
   </dl>
 </p>