X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmidi-on-linux.html;h=fd1d64d55edd159386df228afe098acf25618d42;hb=a61fbacdfcb7a76fe425fada61f49fc85751e47a;hp=3da4652f631c2e46925192b5152b94496c6aa8ee;hpb=fc55149168a9d75cf6760d96558d63cbdbbbc5df;p=ardour-manual diff --git a/include/midi-on-linux.html b/include/midi-on-linux.html index 3da4652..fd1d64d 100644 --- a/include/midi-on-linux.html +++ b/include/midi-on-linux.html @@ -1,4 +1,12 @@ +

+ It is no longer nessessary to use jackd as a backend for Ardour in Linux. + In fact with the spread of LV2 plugins, almost all workflows in Ardour work + well with the ALSA backend. When using the ALSA backend for Ardour, Ardour + will see all MIDI ports that ALSA sees without any user setup. However, should jackd + need to be used, the rest of this page is valid. +

+

The right approach for using MIDI on Linux depends on which version of JACK is in use. The world divides into: @@ -6,13 +14,13 @@ - -
Systems using JACK 1, versions 0.124 or laterOn these systems, simply start JACK with the -X alsa_midi + On these systems, JACK must be started with the -X alsa_midi server argument. To support legacy control applications, the -X seq argument to the ALSA backend of JACK can also be used to get the exact same results.
All othersUse a2jmidid to act as a bridge between ALSA MIDI and JACK. Do not use - the -X seq or -X raw arguments—the timing and + Using a2jmidid acts as a bridge between ALSA MIDI and JACK. The -X seq + or -X raw arguments should not be used—the timing and performance of these options is unacceptable.
@@ -26,28 +34,28 @@

First it must be ensured that there is no ALSA sequencer support enabled in - JACK. To check that, open QJackCtl's Setup window. - Set Settings > MIDI Driver to none. Then uncheck the Misc > - Enable ALSA Sequencer support option. Now restart the jack server + JACK. To check that, one must open QJackCtl's Setup window + and set Settings > MIDI Driver to none, then uncheck the Misc > + Enable ALSA Sequencer support option. The jack server must then be restarted before going on.

-

Check for a2jmidid availability

+

Checking for a2jmidid availability

- Next, check whether a2jmidid is already installed. After starting the JACK - server, go to the command line and type: + Next, it must be checked whether a2jmidid is already installed. This is done + by starting the JACK server, then going to the command line and typing:

a2jmidid -e

- If a2jmidid does not exist, install it with the software manager of the - Linux distribution in use and try again. + If a2jmidid does not exist, it must be installed with the software manager of the + Linux distribution in use until this command responds.

-

Check available MIDI ports

+

Checking available MIDI ports

If JACK is correctly configured for MIDI, then the MIDI ports should appear @@ -62,12 +70,11 @@

-