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=d0beff0473ab8d813313e58e9fd2d85d2c977639;hb=9b7e5ba52fa3a4325daf4631b7b564595e1a710f;hp=86aa53d606aea71e1ec2642e6f6febdf6cf7881c;hpb=d5f9c86810c4854f0e9eea0b85171e4a034c1cfe;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 86aa53d..d0beff0 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 @@ -9,7 +9,7 @@ JACK you use. The world divides into:
Systems using JACK 1, versions 0.124 or later
On these systems, just start JACK with - the -X alsa_midi server argument. To support legacy control + the -X alsa_midi server 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.
All others
@@ -49,18 +49,25 @@ JACK you use. The world divides into:

-

Check MIDI ports

+

Check availaibility MIDI ports

If you have correctly configured JACK for MIDI, then your MIDI ports should appear in - qjackctl under Connections > MIDI > a2j. + qjackctl under Connections > MIDI .

Making it automatic

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, +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 whatever technique you use +to start JACK. +

+ +

+For other versions of JACK, add a2jmidid -e as an "after start-up" script in the Setup > Options tab of QJackCtl, so that it is started automatically whenever you start JACK.