OSC: add /scrub

[ardour-manual] / include / newopen-session-dialog.html

diff --git a/include/newopen-session-dialog.html b/include/newopen-session-dialog.html
index 10244a5008fd06587bcfcc4aa0fb90e46218b3a0..f14e80ea14b04f9f028f8b9b5670fe81436e056a 100644 (file)
--- a/include/newopen-session-dialog.html
+++ b/include/newopen-session-dialog.html
@@ -40,26 +40,29 @@
   the number of physical outputs used, as above.
 </p>
 
   the number of physical outputs used, as above.
 </p>
 

-<h3>Audio/MIDI Setup</h3>
+<h2>Audio/MIDI Setup</h2>

 
 

-<img class="right" src="/images/Audio-MIDI_Setup.png" alt="The Audio+MIDI
-Setup Dialog"/>
+<figure>
+  <img src="/images/Audio-MIDI_Setup.png" alt="The Audio+MIDI Setup Dialog"/>
+  <figcaption>
+    The Audio+MIDI Setup Dialog
+  </figcaption>
+</figure>

 
 <p>
 
 <p>

-  This page is not displayed if <abbr title="JACK Audio Connection
-  Kit">JACK</abbr> is already running when you start
-  Ardour. It provides a simple interface to configure JACK, which
-  will then be started by Ardour. For more control and options regarding
-  JACK, it is recommended that you start JACK before using Ardour, via a
-  JACK control application such as QJackCtl (sometimes called "Jack
-  Control"), JackPilot, etc.
+  This window exposes the different audio options to be used by Ardour for the
+  current work session, for hardware and software and is made of:

 </p>
 </p>

-<dl>
-  <dt>Audio System</dt>
-  <dd>Currently, the only option here is <kbd class="menu">JACK</kbd>. In the future, native
-  hardware access may be supported.</dd>
-  <dt>Driver</dt>
-  <dd>
+
+<table class="dl">
+  <tr><th>Audio System</th>
+  <td>Depending on the operating system, Ardour can possibly use different audio
+    systems, e.g. on Linux, both <abbr title="Advanced Linux Sound Architecture">
+    ALSA</abbr> and <abbr title="JACK Audio Connection Kit">JACK</abbr> are
+    available.
+ </td></tr>
+  <tr><th>Driver</th>
+  <td>

     On Mac OS X this will typically be <kbd class="menu">CoreAudio</kbd>. On Linux usually
     this will be either <kbd class="menu"><abbr title="Free Firewire Audio Driver fOr
     linux">FFADO</abbr></kbd>
     On Mac OS X this will typically be <kbd class="menu">CoreAudio</kbd>. On Linux usually
     this will be either <kbd class="menu"><abbr title="Free Firewire Audio Driver fOr
     linux">FFADO</abbr></kbd>


@@ -67,9 +70,9 @@ Setup Dialog"/>
     Architecture">ALSA</abbr></kbd>, depending on whether or not you are
     utilizing a firewire device. Advanced users on all platforms may also
     use <kbd class="menu">NetJack</kbd> which provides network audio I/O.
     Architecture">ALSA</abbr></kbd>, depending on whether or not you are
     utilizing a firewire device. Advanced users on all platforms may also
     use <kbd class="menu">NetJack</kbd> which provides network audio I/O.

-  </dd>
-  <dt>Device</dt>
-  <dd>The selector should show all availiable interfaces provided by the
+  </td></tr>
+  <tr><th>Device</th>
+  <td>The selector should show all availiable interfaces provided by the

   driver above and which are capable of duplex operation.
   <p class="warning">
     If you are using an Intel Mac running OS X and the builtin audio
   driver above and which are capable of duplex operation.
   <p class="warning">
     If you are using an Intel Mac running OS X and the builtin audio


@@ -78,32 +81,32 @@ Setup Dialog"/>
     its separate input and output devices into a single "aggregate
     device"</a> before Ardour will be able to use it.
    </p>
     its separate input and output devices into a single "aggregate
     device"</a> before Ardour will be able to use it.
    </p>

-  </dd>
-  <dt>Sample Rate</dt>
-  <dd>
+  </td></tr>
+  <tr><th>Sample Rate</th>
+  <td>

     The selector will allow you to select from any sample rate
     supported by the device selected above it.
     The selector will allow you to select from any sample rate
     supported by the device selected above it.

-  </dd>
-  <dt>Buffer Size</dt>
-  <dd>
+  </td></tr>
+  <tr><th>Buffer Size</th>
+  <td>

     You can adjust the size of the buffer used by your audio interface
     to allow for either lower latency, or lower CPU usage and higher
     latency.
     You can adjust the size of the buffer used by your audio interface
     to allow for either lower latency, or lower CPU usage and higher
     latency.

-  </dd>
-  <dt>Input/Output Channels</dt>
-  <dd>
+  </td></tr>
+  <tr><th>Input/Output Channels</th>
+  <td>

     Here you can specify the number of hardware channels to use. The
     Here you can specify the number of hardware channels to use. The

-    default is <kbd class="menu">all available channels</kbd>.</dd>
-  <dt>Hardware Input/Output Latency</dt>
-  <dd>Specify the hardware delay in samples for precise latency compensation.</dd>
-  <dt>Calibrate</dt>
-  <dd>
+    default is <kbd class="menu">all available channels</kbd>.</td></tr>
+  <tr><th>Hardware Input/Output Latency</th>
+  <td>Specify the hardware delay in samples for precise latency compensation.</td></tr>
+  <tr><th>Calibrate</th>
+  <td>

     This button guides you through a semi-automated process to obtain
     This button guides you through a semi-automated process to obtain

-    precise hardware latency measurements for the above option.</dd>
-  <dt>MIDI System</dt>
-  <dd>
+    precise hardware latency measurements for the above option.</td></tr>
+  <tr><th>MIDI System</th>
+  <td>

     Select the MIDI driver to use. On Mac OS X, this will be <kbd
     class="menu">CoreMIDI</kbd>. On Linux, you can change between two legacy
     Select the MIDI driver to use. On Mac OS X, this will be <kbd
     class="menu">CoreMIDI</kbd>. On Linux, you can change between two legacy

-    ALSA drivers or the (preferred) new JACK+ALSA implementation.</dd>
-</dl>
+    ALSA drivers or the (preferred) new JACK+ALSA implementation.</td></tr>
+</table>