Compare commits
3 Commits
2bd09dfcec
...
431f0bfadb
Author | SHA1 | Date | |
---|---|---|---|
|
431f0bfadb | ||
|
a61fbacdfc | ||
|
b770e56505 |
@ -26,25 +26,16 @@
|
|||||||
<td><dfn><abbr title="Advanced Linux Sound API">ALSA</abbr> MIDI</dfn> is the
|
<td><dfn><abbr title="Advanced Linux Sound API">ALSA</abbr> MIDI</dfn> is the
|
||||||
standard MIDI framework on Linux systems.</td></tr>
|
standard MIDI framework on Linux systems.</td></tr>
|
||||||
<tr><th>Windows</th>
|
<tr><th>Windows</th>
|
||||||
<td>There is no single standard MIDI framework on Windows, but Ardour
|
<td><dfn><abbr title="Microsoft Multimedia Environment">MME</abbr></dfn> is the standard
|
||||||
can work with ASIO and others.</td></tr>
|
MIDI framework on Windows systems.</td></tr>
|
||||||
</table>
|
</table>
|
||||||
|
|
||||||
<p class="note">
|
<p class="note">
|
||||||
On Linux systems, <dfn>QJackCtl</dfn> control software displays ALSA MIDI
|
<dfn><abbr title="JACK Audio Connection Kit">JACK</abbr></dfn> is an
|
||||||
ports under its "ALSA" tab (it does not currently display CoreMIDI ports).
|
alternate audio system which Ardour can utilize for both audio and
|
||||||
By contrast, JACK MIDI ports show up under the <kbd class="menu">MIDI</kbd>
|
MIDI. JACK is used to route audio between independent applications,
|
||||||
tab in QJackCtl. However, when Ardour is using jackd for audio in and out
|
and is now considered an advanced use case which is not recommended
|
||||||
the alsa MIDI ports are not accessable. When Ardour is using ALSA for audio
|
for most users. Users with a need to use JACK for audio routing
|
||||||
in and out then only alsa MIDI ports are accessable.
|
should consult the latest documentation at
|
||||||
|
the <a href="https://jackaudio.org/">JACK website</a>.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h2>JACK MIDI Configuration</h2>
|
|
||||||
|
|
||||||
<p>
|
|
||||||
By default, JACK will <strong>not</strong> automatically detect and use
|
|
||||||
existing MIDI ports. One of several ways of <dfn>bridging</dfn> between
|
|
||||||
the native MIDI frameworks (e.g. CoreMIDI or ALSA) and JACK MIDI must be
|
|
||||||
chosen, as described in the following sections.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
|
@ -45,8 +45,7 @@
|
|||||||
<p>
|
<p>
|
||||||
Before attempting to use a Mackie Control device that communicates via
|
Before attempting to use a Mackie Control device that communicates via
|
||||||
a standard MIDI cable or a USB cable, you should ensure that
|
a standard MIDI cable or a USB cable, you should ensure that
|
||||||
<a href="@@midi-on-linux">your Linux
|
<a href="@@configuring-midi">your MIDI environment is setup</a>.
|
||||||
MIDI environment is setup</a>.
|
|
||||||
If you are using a device that uses normal MIDI (via a standard MIDI or
|
If you are using a device that uses normal MIDI (via a standard MIDI or
|
||||||
USB cable), you need to connect Ardour's Mackie Control in and out ports
|
USB cable), you need to connect Ardour's Mackie Control in and out ports
|
||||||
to the MIDI ports leading to and coming from the control surface.
|
to the MIDI ports leading to and coming from the control surface.
|
||||||
|
@ -292,22 +292,6 @@ uri: setting-up-your-system/setting-up-midi
|
|||||||
part: chapter
|
part: chapter
|
||||||
---
|
---
|
||||||
|
|
||||||
---
|
|
||||||
title: MIDI on Linux
|
|
||||||
include: midi-on-linux.html
|
|
||||||
link: midi-on-linux
|
|
||||||
uri: setting-up-your-system/setting-up-midi/midi-on-linux
|
|
||||||
part: subchapter
|
|
||||||
---
|
|
||||||
|
|
||||||
---
|
|
||||||
title: MIDI on OS X
|
|
||||||
include: midi-on-os-x.html
|
|
||||||
link: midi-on-os-x
|
|
||||||
uri: setting-up-your-system/setting-up-midi/midi-on-os-x
|
|
||||||
part: subchapter
|
|
||||||
---
|
|
||||||
|
|
||||||
---
|
---
|
||||||
title: Ardour's Interface
|
title: Ardour's Interface
|
||||||
uri: ardours-interface
|
uri: ardours-interface
|
||||||
|
Loading…
Reference in New Issue
Block a user