manual/include/midi-on-os-x.html
Shamus Hammons 7a4c28bd86 Rearrangement and cleanup of Part I.
This includes rewriting out all of the "you" language that was peppered
throughout, fixing inconsistencies in layout, and removing <br>s
wherever they were misused and unnecessary (which was quite a lot).
2017-02-24 23:30:29 -06:00

29 lines
923 B
HTML

<p>
In order for CoreMIDI to work with Jack MIDI, a CoreMIDI-to-JACK-MIDI
<dfn>bridge</dfn>
is required. This feature is available on versions equal to or great than
version 0.89 of JackOSX.
</p>
<h2>Routing MIDI</h2>
<h3>Inside Ardour</h3>
<p>
MIDI ports show up in Ardour's MIDI connection matrix in multiple
locations. Bridged CoreMIDI ports as well as JACK MIDI ports that have
been created by other software clients will show up under the "Other" tab.
Bridged CoreMIDI hardware ports show up under the "Hardware" tab.
</p>
<h3>External Applications</h3>
<p>
There are multiple options for connecting MIDI ports outside of Ardour.
</p>
<ul>
<li><a href="http://www.snoize.com/MIDIMonitor/">MIDI Monitor</a> is a handy
tool for doing various MIDI-related tasks.</li>
<li><a href="http://notahat.com/midi_patchbay/">MIDI Patchbay</a> lets you
connect ports and filters MIDI data.</li>
</ul>