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%2F02_midi-on-linux.html;h=1d550d534e60f64b32f2900fc9b5d9ff89b7654f;hb=cda977cf9407b3a63e7c51e02151974a2ddf6dd6;hp=adaed743acb1fe9efd131590df0f460d0a942327;hpb=9ab3009544de388b1e564dab28839462bef96df9;p=ardour-manual

diff --git a/_manual/03_setting-up-your-system/05_setting-up-midi/02_midi-on-linux.html b/_manual/03_setting-up-your-system/05_setting-up-midi/02_midi-on-linux.html
index adaed74..1d550d5 100644
--- a/_manual/03_setting-up-your-system/05_setting-up-midi/02_midi-on-linux.html
+++ b/_manual/03_setting-up-your-system/05_setting-up-midi/02_midi-on-linux.html
@@ -2,6 +2,22 @@
 layout: default
 title: MIDI on Linux
 ---                        
+
+The right approach for using MIDI on Linux depends on which version of
+JACK you use. The world divides into:
+
+<dl>
+<dt>Systems using JACK 1, versions 0.124 or later</dt>
+<dd>On these systems, just start JACK with 
+ the <code>-X alsa_midi server</code> argument. To support legacy control
+ applications, you can also use the -X seq argument to the ALSA
+ backend of JACK and get the exact same results.</dd>
+<dl>All others</dl>
+<dd>Use a2jmidid to act as a bridge between ALSA MIDI and JACK. Do
+  not use the -X seq or -X raw arguments - the timing and performance
+  of these options is not acceptable.
+</dd>
+</ul>
   
 <h2>a2jmidid</h2>
 <p>
@@ -32,13 +48,21 @@ title: MIDI on Linux
   Linux distribution and try again.
 </p>
 
-<h3>Check surface control MIDI ports</h3>
+
+<h2>Check MIDI ports</h2>
 <p>
-  After starting a2jmidid, your control surface MIDI ports should appear in
+  If you have correctly configured JACK for MIDI, then your MIDI ports should appear in
   qjackctl under <kbd class="menu">Connections &gt; MIDI &gt; a2j</kbd>.
 </p>
+
+<h3>Making it automatic</h3>
 <p>
-  You can now add <kbd class="input">a2jmidid -e</kbd> as an "after start-up" script in the <kbd
-  class="menu">Setup &gt; Options</kbd> tab of QJackCtl, so that it is
-  started automatically whenever you start JACK.
+Once you've verified that the ports appear in JACK as expected, you
+can make this happen whenever you start JACK. If you use a newer
+version of JACK 1, just make sure the -X alsa_midi or -X seq options
+are enabled. For other versions of JACK,
+add <kbd class="input">a2jmidid -e</kbd> as an "after start-up" script
+in the <kbd class="menu">Setup &gt; Options</kbd> tab of QJackCtl, so
+that it is started automatically whenever you start JACK.
 </p>
+