X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=_manual%2F22_using-control-surfaces%2F04_midi-learn.html;h=bc409128c4f821ed9ef979b1fdcc900c76d05dd0;hb=8107428bfa2744f6b1178ebbbe81cb6908dc5917;hp=bab46be6d50c7ca76534e3fe95d77d89fdf14085;hpb=b386ec9a704966da7db41c2a1db1d9d4d20fe0ed;p=ardour-manual diff --git a/_manual/22_using-control-surfaces/04_midi-learn.html b/_manual/22_using-control-surfaces/04_midi-learn.html index bab46be..bc40912 100644 --- a/_manual/22_using-control-surfaces/04_midi-learn.html +++ b/_manual/22_using-control-surfaces/04_midi-learn.html @@ -7,9 +7,7 @@ title: MIDI Learn

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. +users to prefer quite different mappings.

On every platform that Ardour runs on, there are excellent @@ -26,22 +24,24 @@ QJackctl, aconnect, Patchage, and more.

Basics

    -
  1. Enable Generic MIDI control: Options -> Control Surfaces -> Generic MIDI
  2. -
  3. Connect Ardour's MIDI port named "control" to whatever hardware or software you want (using a MIDI patchbay app)
  4. -
  5. Ctrl-middleclick on whatever on-screen fader, plugin parameter control, button etc. that you want to control
  6. +
  7. Enable Generic MIDI control: Edit > Preferences + > Control Surfaces > Generic MIDI
  8. +
  9. Connect Ardour's MIDI port named control to whatever + hardware or software you want (using a MIDI patchbay app)
  10. +
  11. Middle-click on whatever on-screen + fader, plugin parameter control, button etc. you want to control
  12. A small window appears that says "Operate Controller now"
  13. Move the hardware knob or fader, or press the note/key.
  14. The binding is complete. Moving the hardware should control the Ardour fader etc.

Avoiding work in the future

-

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 +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". +of a mixer strip and select Save as Template.