From b56aba6e2de2440ff06b09d244c328a64659bbf3 Mon Sep 17 00:00:00 2001 From: Paul Davis Date: Sat, 28 Jun 2014 08:38:05 -0400 Subject: [PATCH] text tweaks --- .../05_setting-up-midi/02_midi-on-linux.html | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) 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 86aa53d6..b00989e3 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 @@ -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.