X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fconfiguring-midi.html;h=c0bc0031096935a012ca9e43115b29b6450d1bcf;hb=f8d53fa7c3f6bde67827efe1a03cffc3cd4c1de2;hp=d05d3695e3d9d4834f36cfd2068199e0d4501448;hpb=fc55149168a9d75cf6760d96558d63cbdbbbc5df;p=ardour-manual diff --git a/include/configuring-midi.html b/include/configuring-midi.html index d05d369..c0bc003 100644 --- a/include/configuring-midi.html +++ b/include/configuring-midi.html @@ -14,8 +14,9 @@

MIDI Handling Frameworks

- MIDI input and output for Ardour are handled by the same "engine" that - handles audio input and output. + MIDI input and output for Ardour are handled internally by the same "engine" that + handles audio input and output. However, Ardour can use as many MIDI devices + as the system can see as there are no syncing difficulties as there would be with audio.

@@ -25,20 +26,16 @@ - +
ALSA MIDI is the standard MIDI framework on Linux systems.
WindowsThere 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. + 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. -

-