From cb3d445ef7ad90137e024a2df04bf5f647d431a8 Mon Sep 17 00:00:00 2001 From: PipeManMusic Date: Mon, 1 Apr 2013 17:21:58 +0000 Subject: [PATCH] Added information about the different midi framworks and what they do on various systems. --- _manual/03_setting-up-your-system/05_setting-up-midi.html | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/_manual/03_setting-up-your-system/05_setting-up-midi.html b/_manual/03_setting-up-your-system/05_setting-up-midi.html index fc5faa42..04bc3c50 100644 --- a/_manual/03_setting-up-your-system/05_setting-up-midi.html +++ b/_manual/03_setting-up-your-system/05_setting-up-midi.html @@ -2,5 +2,12 @@ layout: default title: Setting Up MIDI --- +

MIDI Handling Frameworks

+

CoreMIDI

+

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

+

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

+

JACK MIDI

+

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

{% children %}