There is now no split editor/mixer ordering. Attempt to explain ordering of new track...

[ardour-manual] / _manual / 22_using-control-surfaces / 03_midi-binding-maps.html

diff --git a/_manual/22_using-control-surfaces/03_midi-binding-maps.html b/_manual/22_using-control-surfaces/03_midi-binding-maps.html
index eabaa954d8cd337993ba0b0558d7bb390987539c..f7f42d1ab2dbf3f9940208b4b7129b092a2bf849 100644 (file)
--- a/_manual/22_using-control-surfaces/03_midi-binding-maps.html
+++ b/_manual/22_using-control-surfaces/03_midi-binding-maps.html
@@ -7,7 +7,18 @@ title: MIDI Binding Maps
   
   
 <p>
-Ardour 2.X supported <a href="/generic_midi_control">MIDI learning</a> for more or less any control. This was a nice feature that quite a few other DAWs have now provided, but it didn't allow Ardour to work "out of the box" with sensible defaults for existing commercial MIDI controllers. In Ardour 3 and later versions, we have augmented the MIDI learn feature with the ability to load a MIDI binding map for a given controller, which can set up an arbitrary number of physical controls with anything inside Ardour that can be controlled. At this time, these binding maps need to be created with a text editor, but we currently have presets for </p>
+Ardour 2.X supported <a href="/using-control-surfaces/midi-learn">MIDI learning</a> for more
+or less any control. This was a nice feature that quite a few other
+DAWs have now provided, but it didn't allow Ardour to work "out of the
+box" with sensible defaults for existing commercial MIDI
+controllers. In Ardour 3 and later versions, we have augmented the
+MIDI learn feature with the ability to load a MIDI binding map for a
+given controller, which can set up an arbitrary number of physical
+controls with anything inside Ardour that can be controlled. At this
+time, these binding maps need to be created with a text editor, but we
+currently have presets for 
+</p>
+
 <ul>
 <li>Behringer BCF 2000
 </li>
@@ -42,6 +53,8 @@ MIDI bindings are stored in files with the suffix ".map" attached to their name.
 </pre>
 <p>So, to start, create a file with that as the initial contents.
 </p>
+<p>Ardour loads midi maps from its binary-bundle folder in <code>Ardour-&lt;version&gt;/midi_maps/</code> and checks various other locations as well (defined by ARDOUR_MIDIMAPS_PATH environment variable). On GNU/Linux the easiest is to save the file to <code>~/.config/ardour3/midi_maps/</code>.
+</p>
 <h2>Finding out what your MIDI control surface sends</h2>
 <p>
 This is the most complex part of the job, but its still not very hard. You need to connect the control surface to an application that will show you the information that the device sends each time you modify a knob, slider, button etc. There are a variety of such applications (notably <code>gmidimon</code> and <code>kmidimon</code>, but you can actually use Ardour for this if you want. Start Ardour in a terminal window, connect MIDI ports up, and in the Preferences window, enable "Trace Input" on the relevant MIDI port. A full trace of the MIDI data received will show up in the terminal window. (Note: in Ardour3, you get a dedicated, custom dialog for this kind of tracing)