<h2>MIDI Handling Frameworks</h2>
<p>
MIDI input and output for Ardour are handled by the same "engine"
- 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:
+ that handles audio input and output.
</p>
<dl>
<dt>OS X</dt>
<dd> <dfn>CoreMIDI</dfn> is the standard MIDI framework on OSX systems.
- It provides drivers for MIDI hardware and libraries needed by MIDI
- software clients.
</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.
+ is the standard MIDI framework on Linux systems.
</dd>
+<dt>Windows</dt>
+<dd>
+ <dfn>There is no single standard MIDI framework on Windows,
+ but Ardour can work with ASIO and others.
+</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.