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>
- 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>
+
<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>
+ <dd>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.
+ </dd>
<dt>Driver</dt>
<dd>
On Mac OS X this will typically be <kbd class="menu">CoreAudio</kbd>. On Linux usually
class="menu">CoreMIDI</kbd>. On Linux, you can change between two legacy
ALSA drivers or the (preferred) new JACK+ALSA implementation.</dd>
</dl>
-