manual/include/midi-on-os-x.html
Shamus Hammons dfec6899ef Initial cleanup of manual content.
This includes fixing em-dashes, badly spaced colons, various
misspellings, removal of spurious {% %} constructs, conversion of <br />
to <br> (still too many <br>s kicking around), and initial light cleanup
of a few sections that caught my eye.
2017-02-14 09:18:56 -06:00

29 lines
927 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>