that handles audio input and output. Up to release 3.5, that means
that all MIDI I/O takes place via JACK. JACK itself uses the
native MIDI support of the operating system to receive and send
- MIDI data. These are:
+ MIDI data. The native MIDI support provides device drivers for MIDI
+ hardware and libraries needed by software applications that want to
+ work with MIDI.
</p>
-<h3>OS X</h3>
-<p>
- <dfn>CoreMIDI</dfn> is the standard MIDI framework on OSX systems.
- It provides drivers for MIDI hardware and libraries needed by MIDI
- software clients.
-</p>
-
-<h3>Linux</h3>
-<p>
+<dl>
+<dt>OS X</dt>
+<dd> <dfn>CoreMIDI</dfn> is the standard MIDI framework on OSX systems.
+</dd>
+<dt>Linux</dt>
+<dd>
<dfn><abbr title="Advanced Linux Sound API">ALSA</abbr> MIDI</dfn>
- is the standard MIDI framework on Linux systems. It provides drivers
- for MIDI hardware and libraries needed by MIDI software clients.
-</p>
+ is the standard MIDI framework on Linux systems.
+</dd>
+</dl>
<p class="note">
- NoteThe <dfn>QJackCtl</dfn> control software displays ALSA MIDI
+ On Linux systems, <dfn>QJackCtl</dfn> control software displays ALSA MIDI
ports under its "ALSA" tab (it does not currently display CoreMIDI
ports). By contrast, JACK MIDI ports show up under
the <kbd class="menu">MIDI</kbd> tab in QJackCtl.