2013-03-14 16:58:12 -04:00
|
|
|
|
|
2014-02-02 17:16:21 -05:00
|
|
|
|
<h2>Philosophy</h2>
|
2013-03-14 16:58:12 -04:00
|
|
|
|
<p>
|
|
|
|
|
There are no "best" ways to map an arbitrary MIDI controller for
|
|
|
|
|
controlling Ardour. There may be very legitimate reasons for different
|
2017-01-22 19:01:29 -05:00
|
|
|
|
users to prefer quite different mappings.
|
2013-03-14 16:58:12 -04:00
|
|
|
|
</p>
|
|
|
|
|
|
2014-02-02 17:16:21 -05:00
|
|
|
|
<h2>Basics</h2>
|
2013-03-14 16:58:12 -04:00
|
|
|
|
|
|
|
|
|
<ol>
|
2014-02-05 18:59:35 -05:00
|
|
|
|
<li>Enable Generic MIDI control: <kbd class="menu">Edit > Preferences
|
2014-02-06 19:50:36 -05:00
|
|
|
|
> Control Surfaces > Generic MIDI</kbd></li>
|
2017-01-22 19:01:29 -05:00
|
|
|
|
<li>Connect Ardour's MIDI port named <samp>control</samp> to whatever
|
2014-02-05 18:59:35 -05:00
|
|
|
|
hardware or software you want (using a MIDI patchbay app)</li>
|
2017-01-22 19:01:29 -05:00
|
|
|
|
<li><kbd class="mod1 mouse">Middle</kbd>-click on whatever on-screen
|
2014-02-05 18:59:35 -05:00
|
|
|
|
fader, plugin parameter control, button etc. you want to control</li>
|
2013-03-14 16:58:12 -04:00
|
|
|
|
<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>
|
|
|
|
|
|
2021-02-23 13:01:44 -05:00
|
|
|
|
<p>
|
|
|
|
|
There's a complication to this story, however. You cannot use MIDI
|
|
|
|
|
learn with the GUI provided by the plugin. This is true no matter what
|
|
|
|
|
the plugin format or platform is. When we refer to "whatever on-screen
|
|
|
|
|
fader ..." above, we are referring to an “Ardour-owned” control of
|
|
|
|
|
some sort. You can get access to that in one of 3 ways:
|
|
|
|
|
|
|
|
|
|
<ul>
|
|
|
|
|
<li>right click on the processor element in the mixer strip, and choose “Edit with Generic GUI”</li>
|
|
|
|
|
<li>right click on the processor element in the mixer strip, and from “Controls”, make the desired parameter visible inline in the mixer strip</li>
|
|
|
|
|
<li>in the editor, click on the “A” (automation) button for the
|
|
|
|
|
track, find the desired parameter. This will make the automation
|
|
|
|
|
lane for that parameter visible, and it comes with a fader you can
|
|
|
|
|
use for MIDI learn.</li>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
You can’t just “click the GUI” because the plugin owns the GUI, and
|
|
|
|
|
cannot (and should not) be a part of the MIDI learn process.
|
|
|
|
|
</p>
|
|
|
|
|
|
2017-06-06 14:29:38 -04:00
|
|
|
|
<h2>Cancelling a Learned MIDI Binding</h2>
|
|
|
|
|
|
|
|
|
|
<p>
|
|
|
|
|
To unlearn a learned MIDI binding, <kbd class="mod1 mouse">Middle</kbd>-click
|
|
|
|
|
on the control in the same way as you did to learn it in the first place, but
|
|
|
|
|
click on the popup to cancel it.
|
|
|
|
|
</p>
|
|
|
|
|
|
2014-02-02 17:16:21 -05:00
|
|
|
|
<h2>Avoiding work in the future</h2>
|
2013-03-14 16:58:12 -04:00
|
|
|
|
<p>
|
|
|
|
|
If you want the bindings you set up to be used automatically in every
|
2014-02-05 18:59:35 -05:00
|
|
|
|
session, the simplest thing to do is to use <kbd class="menu">Session > Save
|
|
|
|
|
Template</kbd>. Then, when creating new sessions, select that template and
|
2016-01-02 06:28:11 -05:00
|
|
|
|
all the bindings will be automatically set up for you.
|
2013-03-14 16:58:12 -04:00
|
|
|
|
</p>
|
2017-02-13 14:53:37 -05:00
|
|
|
|
|