2013-03-14 16:58:12 -04:00
|
|
|
---
|
|
|
|
|
layout: default
|
|
|
|
|
title: MIDI Learn
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
<h3>Philosophy<h3>
|
|
|
|
|
<p>
|
|
|
|
|
There are no "best" ways to map an arbitrary MIDI controller for
|
|
|
|
|
controlling Ardour. There may be very legitimate reasons for different
|
|
|
|
|
users to prefer quite different mappings. So, Ardour does not come
|
|
|
|
|
with any pre-defined mapping - we believe that users know what is best
|
|
|
|
|
for them.
|
|
|
|
|
</p>
|
|
|
|
|
<p>
|
2013-03-14 17:03:10 -04:00
|
|
|
On every platform that Ardour runs on, there are excellent
|
|
|
|
|
free-of-charge tools for making connections between MIDI hardware and
|
|
|
|
|
"virtual" MIDI ports like the ones that Ardour creates and
|
|
|
|
|
uses. Rather than waste precious developer time replicating these
|
|
|
|
|
connection/patch managers, we prefer to leverage their existence by
|
|
|
|
|
having users rely on them to actually connect Ardour to other MIDI
|
|
|
|
|
devices and software. On OS X, we recommend Pete Yandell's MIDI
|
|
|
|
|
Patchbay. On Linux, a wide variety of tools are available including
|
|
|
|
|
QJackctl, aconnect, Patchage, and more.
|
2013-03-14 16:58:12 -04:00
|
|
|
</p>
|
|
|
|
|
|
|
|
|
|
<h3>Basics<h3>
|
|
|
|
|
|
|
|
|
|
<ol>
|
|
|
|
|
<li> Enable Generic MIDI control: Options -> Control Surfaces -> Generic MIDI</li>
|
|
|
|
|
<li>Connect Ardour's MIDI port named "control" to whatever hardware or software you want (using a MIDI patchbay app)</li>
|
|
|
|
|
<li>Ctrl-middleclick on whatever on-screen fader, plugin parameter control, button etc. that you want to control</li>
|
|
|
|
|
<li>A small window appears that says "Operate Controller now"</li>
|
|
|
|
|
<li>Move the hardware knob or fader, or press the note/key.</li>
|
|
|
|
|
<li>The binding is complete. Moving the hardware should control the Ardour fader etc. </li>
|
|
|
|
|
</ol>
|
|
|
|
|
|
|
|
|
|
<h3>Avoiding work in the future<h3>
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
If you want the bindings you set up to be used automatically in every
|
|
|
|
|
session, the simplest thing to do is to use Session -> Save
|
|
|
|
|
Template. Then, when creating new sessions, select that template and
|
|
|
|
|
all the bindings will be automatically set up for you. You can also
|
|
|
|
|
save a specific track/bus configuration as a template, and use that
|
|
|
|
|
when adding new tracks or busses. Click on the track name at the top
|
|
|
|
|
of a mixer strip and select "Save as Template".
|
|
|
|
|
</p>
|
