X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F03_setting-up-your-system%2F05_setting-up-midi.html;h=4172ba99ce0ea804d68a51127f7a6274b0df6c92;hb=7a9da70647ce4d4c48e042f93e05b89dd983399e;hp=84d718a8ef4cc576577f52eeb1fe4206bece1870;hpb=2f43552d28a1afe2b31c5d0f2702f8dee2336486;p=ardour-manual

diff --git a/_manual/03_setting-up-your-system/05_setting-up-midi.html b/_manual/03_setting-up-your-system/05_setting-up-midi.html
index 84d718a..4172ba9 100644
--- a/_manual/03_setting-up-your-system/05_setting-up-midi.html
+++ b/_manual/03_setting-up-your-system/05_setting-up-midi.html
@@ -17,12 +17,7 @@ title: Setting Up MIDI
 <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. The native MIDI support  provides device drivers for MIDI
-  hardware and libraries needed by software applications that want to
-  work with MIDI.
+  that handles audio input and output. 
 </p>
 
 <dl>
@@ -34,10 +29,16 @@ title: Setting Up MIDI
   <dfn><abbr title="Advanced Linux Sound API">ALSA</abbr> MIDI</dfn>
   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.