diff --git a/_manual/03_setting-up-your-system/05_setting-up-midi.html b/_manual/03_setting-up-your-system/05_setting-up-midi.html index ba9d6e15..e8caf248 100644 --- a/_manual/03_setting-up-your-system/05_setting-up-midi.html +++ b/_manual/03_setting-up-your-system/05_setting-up-midi.html @@ -21,44 +21,40 @@ title: Setting Up MIDI
- Ardour supports various ways of sending and receiving MIDI data: + MIDI input and output for Ardour are handled by the same "engine" + that handles audio input and output. Up to release 3.5, that means + that all MIDI I/O takes place via JACK. JACK itself uses the + native MIDI systems of the operating system to receive and send + data which are:
-CoreMIDI is the standard MIDI framework on OSX systems. It provides drivers for MIDI hardware and libraries needed by MIDI software clients.
-ALSA MIDI is the standard MIDI framework on Linux systems. It provides drivers for MIDI hardware and libraries needed by MIDI software clients.
- The QJackCtl control software displays ALSA MIDI ports + The QJackCtl control software displays ALSA MIDI ports under its "ALSA" tab (it does not currently display CoreMIDI ports). + By contrast, JACK MIDI ports show up under + the MIDI tab in QJackCtl.
- -- JACK MIDI - is a framework used to comunicate between JACK MIDI software clients. - It provides zero jitter and a fixed latency of one period, - the same latency as for JACK audio. -
+ +- JACK MIDI ports show up under the MIDI tab in - QJackCtl. -
- -- There are several ways of bridging between the native MIDI frameworks - (e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections - below. +By default, JACK will not automatically detect and use existing MIDI +ports on your system. You must choose one of several ways +of bridging between the native MIDI frameworks +(e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections +below.
{% children %} 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 adaed743..1d550d53 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 @@ -2,6 +2,22 @@ layout: default title: MIDI on Linux --- + +The right approach for using MIDI on Linux depends on which version of +JACK you 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.@@ -32,13 +48,21 @@ title: MIDI on Linux Linux distribution and try again.
-- After starting a2jmidid, your control surface MIDI ports should appear in + If you have correctly configured JACK for MIDI, then your MIDI ports should appear in qjackctl under Connections > MIDI > a2j.
+ +- You can now 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 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, +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.
+