fix up some details on the setting up midi page

[ardour-manual] / _manual / 03_setting-up-your-system / 05_setting-up-midi.html

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 fc5faa42dc7009cffba879add1612b07c80f891b..8fb4083a3fafa85cde1a2cb3623cb21e63f9e897 100644 (file)
--- 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,31 @@
 layout: default
 title: Setting Up MIDI
 ---                        
+ <h2>MIDI Handling Frameworks</h2>
+<h4>CoreMIDI</h4>
+
+<p> 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</p>
+
+<h4>ALSA MIDI</h4>
+
+<p> 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</p>
+
+<h4> JACK MIDI</h4>
+
+<p> 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.
+</p>
     
+<p>
+Various ways of "bridging" between the native MIDI framework
+(e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections
+below.
+</p>
+
 {% children %}