text tweaks

[ardour-manual-diverged] / _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 04bc3c509d5039a0e4c820d494c0a6ed775d3707..8925eb73bde2c437981a240d4f9faa8909362fe0 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,12 +2,54 @@
 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 "MIDI" tab in qjackctl</p>
-<h4> JACK MIDI</h4>
-<p> 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</p>
-    
+
+<h2>What Can Ardour Do With MIDI?</h2>
+<p>
+  <dfn><abbr title="Musical Instrument Digital
+  Interface">MIDI</abbr></dfn> is a way to describe musical
+  performances and to control music hardware and software.
+</p> 
+<p>Ardour can import and record MIDI data, and perform a variety of
+  editing operations on it. Furthermore, MIDI can be used to control
+  various functions of Ardour.
+</p>
+
+<h2>MIDI Handling Frameworks</h2>
+<p>
+  MIDI input and output for Ardour are handled by the same "engine"
+  that handles audio input and output. Up to release 3.5, that means
+  that all MIDI I/O takes place via JACK. JACK itself uses the 
+  native MIDI support of the operating system to receive and send
+  MIDI data. The native MIDI support  provides device drivers for MIDI
+  hardware and libraries needed by software applications that want to
+  work with MIDI.
+</p>
+
+<dl>
+<dt>OS X</dt>
+<dd>  <dfn>CoreMIDI</dfn> is the standard MIDI framework on OSX systems. 
+</dd>
+<dt>Linux</dt>
+<dd>
+  <dfn><abbr title="Advanced Linux Sound API">ALSA</abbr> MIDI</dfn>
+  is the standard MIDI framework on Linux systems.
+</dd>
+</dl>
+
+<p class="note">
+  On Linux systems, <dfn>QJackCtl</dfn> control software displays ALSA MIDI
+  ports under its "ALSA" tab (it does not currently display CoreMIDI
+  ports).  By contrast, JACK MIDI ports show up under
+  the <kbd class="menu">MIDI</kbd> tab in QJackCtl.
+</p>
+   
+<h2>JACK MIDI Configuration</h2>
+<p>
+By default, JACK will <strong>not</strong> automatically detect and use existing MIDI
+ports on your system. You must choose one of several ways
+of <dfn>bridging</dfn> between the native MIDI frameworks
+(e.g. CoreMIDI or ALSA) and JACK MIDI, as described in the sections
+below.
+</p>
+
 {% children %}