2013-04-01 13:06:45 -04:00
|
|
|
---
|
|
|
|
layout: default
|
|
|
|
title: Setting Up MIDI
|
|
|
|
---
|
2013-04-19 12:18:13 -04:00
|
|
|
|
2014-02-03 19:33:51 -05:00
|
|
|
<h2>What Can Ardour Do With MIDI?</h2>
|
|
|
|
<p>
|
|
|
|
<dfn><abbr title="Musical Instrument Digital Interface">MIDI</abbr></dfn>
|
|
|
|
is a way to describe music data and to control music hardware and
|
|
|
|
software. Ardour can import and record MIDI data, and perform a
|
|
|
|
variety of editing operations on it. Furthermore, MIDI can be used to
|
|
|
|
control various functions of Ardour.
|
|
|
|
</p>
|
|
|
|
<p class="note">
|
|
|
|
Ardour does not include a <dfn>synthesis engine</dfn> 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.<br />
|
|
|
|
Please see the section on working with plug-ins for more information on
|
|
|
|
turning MIDI data into audio output.</p>
|
2013-04-19 12:18:13 -04:00
|
|
|
|
2014-02-03 19:33:51 -05:00
|
|
|
<h2>MIDI Handling Frameworks</h2>
|
|
|
|
<p>
|
2014-06-28 08:33:27 -04:00
|
|
|
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:
|
2014-02-03 19:33:51 -05:00
|
|
|
</p>
|
2013-04-16 23:40:12 -04:00
|
|
|
|
2014-06-28 08:33:27 -04:00
|
|
|
<h3>OS X : CoreMIDI</h3>
|
2014-02-03 19:33:51 -05:00
|
|
|
<p>
|
|
|
|
<dfn>CoreMIDI</dfn> is the standard MIDI framework on OSX systems.
|
|
|
|
It provides drivers for MIDI hardware and libraries needed by MIDI
|
|
|
|
software clients.
|
|
|
|
</p>
|
2013-04-16 23:40:12 -04:00
|
|
|
|
2014-06-28 08:33:27 -04:00
|
|
|
<h3>Linux : ALSA MIDI</h3>
|
2014-02-03 19:33:51 -05:00
|
|
|
<p>
|
|
|
|
<dfn><abbr title="Advanced Linux Sound API">ALSA</abbr> MIDI</dfn>
|
|
|
|
is the standard MIDI framework on Linux systems. It provides drivers
|
|
|
|
for MIDI hardware and libraries needed by MIDI software clients.
|
|
|
|
</p>
|
|
|
|
<p>
|
2014-06-28 08:33:27 -04:00
|
|
|
The <dfn>QJackCtl</dfn> control software displays ALSA MIDI ports
|
2014-02-03 19:33:51 -05:00
|
|
|
under its "ALSA" tab (it does not currently display CoreMIDI ports).
|
2014-06-28 08:33:27 -04:00
|
|
|
By contrast, JACK MIDI ports show up under
|
|
|
|
the <kbd class="menu">MIDI</kbd> tab in QJackCtl.
|
2014-02-03 19:33:51 -05:00
|
|
|
</p>
|
2014-06-28 08:33:27 -04:00
|
|
|
|
|
|
|
<h2>JACK MIDI Configuration</h2>
|
2013-04-16 23:40:12 -04:00
|
|
|
<p>
|
2014-06-28 08:33:27 -04:00
|
|
|
By default, JACK will not automatically detect and use existing MIDI
|
|
|
|
ports on your system. You must choose one of several ways
|
|
|
|
of <dfn>bridging</dfn> between the native MIDI frameworks
|
|
|
|
(e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections
|
|
|
|
below.
|
2013-04-16 23:40:12 -04:00
|
|
|
</p>
|
|
|
|
|
2013-04-01 13:06:45 -04:00
|
|
|
{% children %}
|