X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmidi-on-linux.html;h=3da4652f631c2e46925192b5152b94496c6aa8ee;hb=ed98a497411f6d6c1645307e6c40dcecb27cae55;hp=307ae5432979a97deb23baab53549c6847f18ec1;hpb=7a4c28bd8605e90876ebee619de364ab7001e405;p=ardour-manual diff --git a/include/midi-on-linux.html b/include/midi-on-linux.html index 307ae54..3da4652 100644 --- a/include/midi-on-linux.html +++ b/include/midi-on-linux.html @@ -1,71 +1,73 @@ -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: +
--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.Systems using JACK 1, versions 0.124 or later | +On these systems, simply start JACK 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 | +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 unacceptable. |
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. -
-
+ 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 it's time to restart your jack server before going on.
+ class="input">none. Then uncheck the Misc >
+ Enable ALSA Sequencer support option. Now restart the jack server
+ 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, check whether a2jmidid is already installed. After starting the JACK + server, go to the command line and type:
+ 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, install it with the software manager of the + Linux distribution in use and try again.
-- If you have correctly configured JACK for MIDI, then your 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 JACK is correctly configured for MIDI, then the MIDI ports should appear + in qjackctl under Connections > MIDI.
-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.