Added info on MIDI to help new users understand why they can't hear audio by default

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..d76ba5f1ad6a2e9f64d7c1a307cc0ab81d10628e 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,7 +2,12 @@
 layout: default
 title: Setting Up MIDI
 ---                        
+
+ <h2>What Can Ardour Do With MIDI?</h2>
+<p>MIDI is a way of both describing musical data and controlling musical hardware\software. MIDI doesn't actually create any audio but rather describes the audio in order to control hardware/software. Ardour can import MIDI data, record MIDI data and allow MIDI data to be edited in a variety of ways. Also, MIDI can be used to control various things withing Ardour. This allows for the most flexible work flow with regards to MIDI. What Ardour doesn't have is any built in synthesis to turn the MIDI data into audio. Rather, this is handled through the use of plug-ins and external hardware/software. While this makes MIDI a powerful tool it can also  be a stumbling block for first time users who expect MIDI input to result in audio output by default. Please see the section on working with plug-ins for more information on turning MIDI data into audio output with Ardour.</p>
+
  <h2>MIDI Handling Frameworks</h2>
+<p>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.</p>
 <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>