From 326ed5b2805b9512c7b60428e8c75f3e4d48f5cb Mon Sep 17 00:00:00 2001 From: Len Ovens Date: Sun, 22 Jan 2017 16:01:29 -0800 Subject: [PATCH] Reorganize control surfaces generic midi --- .../03_generic-midi.html | 18 ++ .../01_midi-binding-maps.html} | 157 +++++++++--------- .../02_midi-learn.html} | 12 +- .../03_working-with-encoders.html} | 3 +- ...erPort.html => 04_Presonus_FaderPort.html} | 0 ...leton_Push2.html => 05_Ableton_Push2.html} | 0 6 files changed, 103 insertions(+), 87 deletions(-) create mode 100644 _manual/23_using-control-surfaces/03_generic-midi.html rename _manual/23_using-control-surfaces/{03_midi-binding-maps.html => 03_generic-midi/01_midi-binding-maps.html} (88%) rename _manual/23_using-control-surfaces/{04_midi-learn.html => 03_generic-midi/02_midi-learn.html} (92%) rename _manual/23_using-control-surfaces/{03_midi-binding-maps/01_working-with-encoders.html => 03_generic-midi/03_working-with-encoders.html} (96%) rename _manual/23_using-control-surfaces/{05_Presonus_FaderPort.html => 04_Presonus_FaderPort.html} (100%) rename _manual/23_using-control-surfaces/{06_Ableton_Push2.html => 05_Ableton_Push2.html} (100%) diff --git a/_manual/23_using-control-surfaces/03_generic-midi.html b/_manual/23_using-control-surfaces/03_generic-midi.html new file mode 100644 index 00000000..d548b087 --- /dev/null +++ b/_manual/23_using-control-surfaces/03_generic-midi.html @@ -0,0 +1,18 @@ +--- +layout: default +title: Generic Midi Surface Control +--- + +

+ Generic Midi allows synthesizers and other devices communicate with + Ardour. MIDI devices can send commands relating to playback (such as + play or stop), performance (such as volume, play, stop, and almost any + other function (such as Edit, or Undo). +

+

+ Many MIDI control surfaces use predefined MIDI protocols such as the + "Mackie Control Protocol". In such cases it is best to use Ardour's + implementation of that protocol as it is likely more feature complete. +

+ +{% children %} diff --git a/_manual/23_using-control-surfaces/03_midi-binding-maps.html b/_manual/23_using-control-surfaces/03_generic-midi/01_midi-binding-maps.html similarity index 88% rename from _manual/23_using-control-surfaces/03_midi-binding-maps.html rename to _manual/23_using-control-surfaces/03_generic-midi/01_midi-binding-maps.html index 2b6d1ac1..5ea01bfb 100644 --- a/_manual/23_using-control-surfaces/03_midi-binding-maps.html +++ b/_manual/23_using-control-surfaces/03_generic-midi/01_midi-binding-maps.html @@ -1,18 +1,18 @@ --- layout: default -title: MIDI Binding Maps ---- +title: Generic MIDI Binding Maps +---

- Ardour 2.X supported - MIDI learning + Ardour 2.X supported + MIDI learning for more or less any control. This was a nice feature that quite a few other DAWs are providing by now, 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 + 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. + controls with anything inside Ardour that can be controlled.

Currently (August 2016), we have presets for the following devices/modes: @@ -45,28 +45,27 @@ title: MIDI Binding Maps At this time, new binding maps need to be created with a text editor.

MIDI binding maps are accessible by double-clicking Edit - > Preferences > Control Surfaces > Generic MIDI. Ardour will + > Preferences > Control Surfaces > Generic MIDI. Ardour will retain your selection after you choose one.

Creating new MIDI maps

The Basic Concept

- Since the beginning of time (well, sometime early in the 2.X series), - Ardour has had the concept of identifying each track and bus with a - remote control ID. This ID uniquely identifies a track or bus - so that when messages arrive from elsewhere via MIDI or OSC , we can determine - which track or bus they are intended to control. Ardour has a + Since the beginning of time (well, sometime early in the 2.X series), + Ardour has had the concept of identifying each track and bus with a + remote control ID. This ID uniquely identifies a track or bus + so that when messages arrive from elsewhere via MIDI or OSC , we can determine + which track or bus they are intended to control. See number - of ways of assigning remote control IDs, but they don't really matter - very much when creating MIDI binding maps, so we won't discuss that here. - You just need to know that there is a "first track" and its remote control + href="/working-with-tracks/controlling-track-ordering/track-ordering-and-remote-control-ids/"> + remote control IDs for more information. + You just need to know that there is a "first track" and its remote control ID is 1, and so on.

Getting Started

- MIDI bindings are stored in files with the suffix ".map" attached to their + MIDI bindings are stored in files with the suffix ".map" attached to their name. The minimal content looks like this: 

@@ -79,31 +78,31 @@ bindings">
   So, to start, create a file with that as the initial contents.
 

 

-  On OS X, Ardour loads midi maps from its binary-bundle folder in 
-  Ardour-<version>/midi_maps/ and checks 
-  various other locations as well (defined by the ARDOUR_MIDIMAPS_PATH 
-  environment variable). On GNU/Linux the easiest is to save the file to 
+  On OS X, Ardour loads midi maps from its binary-bundle folder in
+  Ardour-<version>/midi_maps/ and checks
+  various other locations as well (defined by the ARDOUR_MIDIMAPS_PATH
+  environment variable). On GNU/Linux the easiest is to save the file to
   ~/.config/ardour3/midi_maps/.
 

 
 
Finding out what your MIDI control surface sends

 

-  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 
-  gmidimon and kmidimon, 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 
+  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
+  gmidimon and kmidimon, 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.)
 

 
Types of Bindings

 

-  There are two basic kinds of bindings you can make between a MIDI message 
-  and something inside Ardour. The first is a binding to a specific parameter 
-  of a track or bus. The second is a binding to a function that will change 
+  There are two basic kinds of bindings you can make between a MIDI message
+  and something inside Ardour. The first is a binding to a specific parameter
+  of a track or bus. The second is a binding to a function that will change
   Ardour's state in some way.
 

 
Binding to Track/Bus controls

@@ -118,17 +117,17 @@ bindings">
 
Message specifications

 

   You can create a binding for either 3 types of channel messages, or for a
-  system exclusive ("sysex") message.  A channel message specification looks 
+  system exclusive ("sysex") message.  A channel message specification looks
   like this:
 

 
    <Binding channel="1" ctl="13" ....
 
 

-  This defines a binding for a MIDI Continuous Controller message involving 
-  controller 13, arriving on channel 1. There are 16 MIDI channels, numbered 
-  1 to 16. Where the example above says ctl, you can alternatively 
-  use note (to create binding for a Note On message) or 
+  This defines a binding for a MIDI Continuous Controller message involving
+  controller 13, arriving on channel 1. There are 16 MIDI channels, numbered
+  1 to 16. Where the example above says ctl, you can alternatively
+  use note (to create binding for a Note On message) or
   pgm  (to create a binding for a Program Change message).
 

 

@@ -137,7 +136,7 @@ bindings">
   offsets rather than values. These accept Continuous Controller messages
   but treat them as offsets. These are good for banked controls as they are
   always at the right spot to start adjusting. (
-   
+   
    Learn more about working with encoders
    )
 

@@ -149,7 +148,7 @@ bindings">
   <Binding sysex="f0 7f 0 6 7 f7" ....
 
 

-  The string after the sysex= part is the sequence of MIDI bytes, 
+  The string after the sysex= part is the sequence of MIDI bytes,
   as hexadecimal values, that make up the sysex message.
 

 

@@ -159,9 +158,9 @@ bindings">
   <Binding msg="80 60 40" ....
 
 

-  The string after the msg= part is the sequence of MIDI bytes, as 
-  hexadecimal values, that make up the message you want to bind. Using this is 
-  slightly less efficient than the other variants shown above, but is useful for 
+  The string after the msg= part is the sequence of MIDI bytes, as
+  hexadecimal values, that make up the message you want to bind. Using this is
+  slightly less efficient than the other variants shown above, but is useful for
   some oddly designed control devices.
 

 
@@ -180,7 +179,7 @@ bindings">
 
 
Control address

 

-  A control address defines what the binding will actually control. 
+  A control address defines what the binding will actually control.
   There are quite a few different things that can be specified here:
 

 

@@ -220,31 +219,31 @@ bindings">
 
 

 

-  For send/insert/plugin controls, the address consists of a track/bus 
-  address (as just described) followed by a number identifying the plugin/send 
-  (starting from 1). For plugin parameters, there is an additional third 
+  For send/insert/plugin controls, the address consists of a track/bus
+  address (as just described) followed by a number identifying the plugin/send
+  (starting from 1). For plugin parameters, there is an additional third
   component: a number identifying the plugin parameter number (starting from
   1).
 

 

-  One additional feature: for solo and mute bindings, you can also add 
-  momentary="yes" after the control address. This is useful 
-  primarily for NoteOn bindings — when Ardour gets the NoteOn it 
-  will solo or mute the targetted track or bus, but then when a NoteOff 
+  One additional feature: for solo and mute bindings, you can also add
+  momentary="yes" after the control address. This is useful
+  primarily for NoteOn bindings — when Ardour gets the NoteOn it
+  will solo or mute the targetted track or bus, but then when a NoteOff
   arrives, it will un-solo or un-mute it.
 

 
 
Bindings to Ardour "functions"

 

-  Rather than binding to a specific track/bus control, it may be useful to 
-  have a MIDI controller able to alter some part of Ardour's state. A 
+  Rather than binding to a specific track/bus control, it may be useful to
+  have a MIDI controller able to alter some part of Ardour's state. A
   binding definition that does this looks like this:
 

 
   <Binding channel="1" note="13" function="transport-roll"/>
 
 

-  In this case, a NoteOn message for note number 13 (on channel 1) will 
+  In this case, a NoteOn message for note number 13 (on channel 1) will
   start the transport rolling. The following function names are available:
 

 

@@ -303,54 +302,54 @@ bindings">
 
Binding to Ardour "actions"

 

   You can also bind a sysex or arbitrary message to any of the items
-  that occur in Ardour's main menu (and its submenus).  The best place 
-  to look for the (long) list of how to address each item is in your 
+  that occur in Ardour's main menu (and its submenus).  The best place
+  to look for the (long) list of how to address each item is in your
   keybindings file, which will contain lines that look like this:
 

 
 (gtk_accel_path "<Actions>/Editor/temporal-zoom-in" "equal")
 
 

-  To create a binding between an arbitrary MIDI message (we'll use a 
-  note-off on channel 1 of MIDI note 60 (hex) with release velocity 
+  To create a binding between an arbitrary MIDI message (we'll use a
+  note-off on channel 1 of MIDI note 60 (hex) with release velocity
   40 (hex)), the binding file would contain:
 

 
    <Binding msg="80 60 40" action="Editor/temporal-zoom-in"/>
 
 

-  The general rule, when taken an item from the keybindings file and 
-  using it in a MIDI binding is to simply strip the 
-  <Action> prefix of the second field in the 
+  The general rule, when taken an item from the keybindings file and
+  using it in a MIDI binding is to simply strip the
+  <Action> prefix of the second field in the
   keybinding definition.
 

 
 
Banks and Banking

 

-  Because many modern control surfaces offer per-track/bus controls 
-  for far fewer tracks & busses than many users want to control, 
-  Ardour offers the relatively common place concept of banks. Banks 
-  allow you to control any number of tracks and/or busses easily, 
-  regardless of how many faders/knobs etc. your control surface has.
 
-  To use banking, the control addresses must be specified using the 
-  bank relative format mentioned above ("B1" to identify 
-  the first track of a bank of tracks, rather than "1" to identify 
+  Because many modern control surfaces offer per-track/bus controls
+  for far fewer tracks & busses than many users want to control,
+  Ardour offers the relatively common place concept of banks. Banks
+  allow you to control any number of tracks and/or busses easily,
+  regardless of how many faders/knobs etc. your control surface has.

+  To use banking, the control addresses must be specified using the
+  bank relative format mentioned above ("B1" to identify
+  the first track of a bank of tracks, rather than "1" to identify
   the first track).
 

 

-  One very important extra piece of information is required to use 
-  banking: an extra line near the start of the list of bindings 
-  that specifies how many tracks/busses to use per bank. If the 
-  device has 8 faders, then 8 would be a sensible value to use for 
+  One very important extra piece of information is required to use
+  banking: an extra line near the start of the list of bindings
+  that specifies how many tracks/busses to use per bank. If the
+  device has 8 faders, then 8 would be a sensible value to use for
   this. The line looks like this:

 
    <DeviceInfo bank-size="8"/>
 
 

   In addition, you probably want to ensure that you bind something
-  on the control surface to the next-bank and 
-  prev-bank functions, otherwise you and other users 
-  will have to use the mouse and the GUI to change banks, which 
+  on the control surface to the next-bank and
+  prev-bank functions, otherwise you and other users
+  will have to use the mouse and the GUI to change banks, which
   rather defeats the purpose of the bindings.
 

 
A Complete (though muddled) Example

@@ -383,9 +382,9 @@ bindings">
 </ArdourMIDIBindings>

- Please note that channel, controller and note numbers are specified as - decimal numbers in the ranges 1-16, 0-127 and 0-127 respectively + Please note that channel, controller and note numbers are specified as + decimal numbers in the ranges 1-16, 0-127 and 0-127 respectively (the channel range may change at some point).

- + {% children %} diff --git a/_manual/23_using-control-surfaces/04_midi-learn.html b/_manual/23_using-control-surfaces/03_generic-midi/02_midi-learn.html similarity index 92% rename from _manual/23_using-control-surfaces/04_midi-learn.html rename to _manual/23_using-control-surfaces/03_generic-midi/02_midi-learn.html index c200bf19..74e3d83d 100644 --- a/_manual/23_using-control-surfaces/04_midi-learn.html +++ b/_manual/23_using-control-surfaces/03_generic-midi/02_midi-learn.html @@ -1,13 +1,13 @@ --- layout: default -title: MIDI Learn ---- +title: Generic MIDI Learn +---

Philosophy

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

On every platform that Ardour runs on, there are excellent @@ -18,7 +18,7 @@ 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. +QJackctl, aconnect, Patchage, and more.

Basics

@@ -26,9 +26,9 @@ QJackctl, aconnect, Patchage, and more.
  1. Enable Generic MIDI control: Edit > Preferences > Control Surfaces > Generic MIDI
    2. -
  2. Connect Ardour's MIDI port named control to whatever +
  3. Connect Ardour's MIDI port named control to whatever hardware or software you want (using a MIDI patchbay app)
    4. -
  4. Middle-click on whatever on-screen +
  5. Middle-click on whatever on-screen fader, plugin parameter control, button etc. you want to control
  6. A small window appears that says "Operate Controller now"
  7. Move the hardware knob or fader, or press the note/key.
    8. diff --git a/_manual/23_using-control-surfaces/03_midi-binding-maps/01_working-with-encoders.html b/_manual/23_using-control-surfaces/03_generic-midi/03_working-with-encoders.html similarity index 96% rename from _manual/23_using-control-surfaces/03_midi-binding-maps/01_working-with-encoders.html rename to _manual/23_using-control-surfaces/03_generic-midi/03_working-with-encoders.html index 2a949684..0f0ae75f 100644 --- a/_manual/23_using-control-surfaces/03_midi-binding-maps/01_working-with-encoders.html +++ b/_manual/23_using-control-surfaces/03_generic-midi/03_working-with-encoders.html @@ -1,7 +1,6 @@ --- layout: default -title: Working With Encoders in Ardour -menu_title: Working With Encoders +title: Generic MIDI and Encoders ---

    diff --git a/_manual/23_using-control-surfaces/05_Presonus_FaderPort.html b/_manual/23_using-control-surfaces/04_Presonus_FaderPort.html similarity index 100% rename from _manual/23_using-control-surfaces/05_Presonus_FaderPort.html rename to _manual/23_using-control-surfaces/04_Presonus_FaderPort.html diff --git a/_manual/23_using-control-surfaces/06_Ableton_Push2.html b/_manual/23_using-control-surfaces/05_Ableton_Push2.html similarity index 100% rename from _manual/23_using-control-surfaces/06_Ableton_Push2.html rename to _manual/23_using-control-surfaces/05_Ableton_Push2.html