Below is a list of various MIDI Frameworks for getting MIDI data into and out of Ardour in order to work with MIDI aware software/hardware.
CoreMIDI is the standard MIDI framework to comunicate with MIDI hardware on OSX systems. It provides drivers and libraries needed by MIDI clients. These ports do not show up in qjackctl
+ +CoreMIDI is the standard MIDI framework to comunicate with MIDI +hardware on OSX systems. It provides drivers and libraries needed by +MIDI clients. These ports do not show up in qjackctl
+ALSA MIDI is the standard MIDI framework to comunicate with MIDI hardware on Linux systems. It provides drivers and libraries needed by MIDI clients. These ports show up under the "MIDI" tab in qjackctl
+ +ALSA MIDI is the standard MIDI framework to comunicate with MIDI +hardware on Linux systems. It provides drivers and libraries needed by +MIDI clients. These ports show up under the "ALSA" tab in qjackctl
+JACK MIDI is a framework used to comunicate between JACK MIDI software clients. On OSX JACK MIDI provides 0 jitter and a fixed latency of 1 period MIDI routing. On Linux JACK MIDI provides zero latency, except when there is a midi loop where the latency would fixed at 1 perioud, and zero jitter MIDI routing. These ports show up under the "JACK MIDI" tab in qjackctl
+ +JACK MIDI is a framework used to comunicate between JACK MIDI +software clients. It provides zero jitter and a fixed latency of 1 +"period" (the same latency that exists for audio). These ports show up +under the "MIDI" tab in qjackctl. +
++Various ways of "bridging" between the native MIDI framework +(e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections +below. +
+ {% children %}