X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fmidi-on-os-x.html;h=47442131bec7b04dc50733a3c3931efe46e7af7f;hb=53168d99209b770d9894692b820f06393a63abb5;hp=985e5230db517012841531d1578b400f321bc596;hpb=7a4c28bd8605e90876ebee619de364ab7001e405;p=ardour-manual diff --git a/include/midi-on-os-x.html b/include/midi-on-os-x.html index 985e523..4744213 100644 --- a/include/midi-on-os-x.html +++ b/include/midi-on-os-x.html @@ -1,28 +1,31 @@

In order for CoreMIDI to work with Jack MIDI, a CoreMIDI-to-JACK-MIDI - bridge - is required. This feature is available on versions equal to or great than - version 0.89 of JackOSX. + bridge is required. This feature is available on versions equal to + or greater than version 0.89 of JackOSX.

Routing MIDI

+

Inside Ardour

+

- 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. + 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.

External Applications

+

There are multiple options for connecting MIDI ports outside of Ardour.

+