X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fconfiguring-midi.html;h=c0bc0031096935a012ca9e43115b29b6450d1bcf;hb=a26b49e5c69ac38d5465c62623994e8a81f1b6b3;hp=217eee9a3e03ae1c91bb139468c7d85a44775d1e;hpb=e74c09802c2ca4038144d051c425a65661bde3ea;p=ardour-manual diff --git a/include/configuring-midi.html b/include/configuring-midi.html index 217eee9..c0bc003 100644 --- a/include/configuring-midi.html +++ b/include/configuring-midi.html @@ -26,25 +26,16 @@ ALSA MIDI is the standard MIDI framework on Linux systems. Windows - There is no single standard MIDI framework on Windows, but Ardour - can work with ASIO and others. + MME is the standard + MIDI framework on Windows systems.

- On Linux systems, 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. However, when Ardour is using jackd for audio in and out - the alsa MIDI ports are not accessable. When Ardour is using ALSA for audio - in and out then only alsa MIDI ports are accessable. + JACK is an + alternate audio system which Ardour can utilize for both audio and + MIDI. JACK is used to route audio between independent applications, + and is now considered an advanced use case which is not recommended + for most users. Users with a need to use JACK for audio routing + should consult the latest documentation at + the JACK website.

- -

JACK MIDI Configuration

- -

- By default, JACK will not automatically detect and use - existing MIDI ports. One of several ways of bridging between - the native MIDI frameworks (e.g. CoreMIDI or ALSA) and JACK MIDI must be - chosen, as described in the following sections. -

-