From 64c34bcf922881a9490d2a6a7d40165a9e594751 Mon Sep 17 00:00:00 2001
From: Paul Davis
- Ardour does not include a synthesis engine to produce audio
- from MIDI data, but relies on plugins or external hard- and software
- for the task. This can be a stumbling block for first time users who
- expect MIDI input to result in audio output by default.
- Please see the section on working with plug-ins for more information on
- turning MIDI data into audio output.
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: + native MIDI support of the operating system to receive and send + MIDI data. These are:
- 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 + +
+ NoteThe 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.
-By default, JACK will not automatically detect and use existing MIDI +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