X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmidi-on-linux.html;h=bcd770758d36bdab5d874f2b58ca96a142119a4b;hb=3c0bdbab01a9900147a5f794026960040f0f9e0c;hp=b798b7a50319bdd96e02d47ebe358e5d80c69791;hpb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;p=ardour-manual diff --git a/include/midi-on-linux.html b/include/midi-on-linux.html index b798b7a..bcd7707 100644 --- a/include/midi-on-linux.html +++ b/include/midi-on-linux.html @@ -1,71 +1,72 @@ -The right approach for using MIDI on Linux depends on which version of -JACK you use. The world divides into: +
+ The right approach for using MIDI on Linux depends on which version of JACK + is in use. The world divides into: +
+ +Systems using JACK 1, versions 0.124 or later | +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 others | +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. |
-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.a2jmidid is an application that bridges between the system MIDI ports and JACK.
+- First you should make sure that there is no ALSA sequencer support enabled - in JACK. To do that open QJackCtl's Setup window. -
-
- Set Settings > MIDI Driver to none.
- Then uncheck the Misc > Enable ALSA Sequencer
- support option.
- Now it's time to restart your jack server before going on.
+ First it must be ensured that there is no ALSA sequencer support enabled in
+ 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.
- First, check whether a2jmidid is already installed in your system. After - starting your 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 your - Linux distribution 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.
+- If you have correctly configured JACK for MIDI, then your MIDI ports should appear in - qjackctl under Connections > MIDI . + If JACK is correctly configured for MIDI, then the MIDI ports should appear + in qjackctl under Connections > MIDI.
-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 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. + Once it has been verified that the ports appear in JACK as expected, this can + be made to happen whenever JACK is started:
+-X
+ alsa_midi
or -X seq
options are enabled for whatever
+ technique is being used to start JACK.a2jmidid -e &
as an
+ "after start-up" script in the Setup > Options tab
+ of QJackCtl, so that it is started automatically whenever JACK is
+ started.