Binding Popup Windows

Bindings are defined through a set of popup dialog windows. The windows for

binding MIDI events, computer keyboard keys, and plugin parameters all share some components. The following image shows the binding window for MIDI events.

Example Binding Window

The binding windows for MIDI events, keyboard events, and plugin parameters all use this style of user interface with a few differences that are described in later sections.

4.1.1 Binding Set Selector

At the top are the Binding Set Selector components. These are displayed only in the MIDI binding window. The components here allow you to create several sets of bindings which may be activated at different times. The MIDI Bindings section describes these components in more detail.

4.1.2 Bindings List

On the left is the Bindings panel. This lists all of the bindings that are defined. The first column will have the name of the target, the second text representation of the trigger. The third arguments column contains the optional binding arguments.

4.1.3 Selecting Targets

On the upper right is the Targets panel where you select a target for binding. This is a tabbed panel with each tab containing the names of one type of target.

The Functions tab will have a list of all built-in functions arranged in alphabetical order. Function names that begin with Sustain are Sustain Functions and are normally bound to a trigger that has both a "down" and an "up" state such as MIDI notes.

Function Targets

The Scripts tab will have a list of all loaded scripts. If you have not added any script files or directories from the Scripts configuration window then this tab will be empty.

The Controls tab will have a list of all the built-in track controls. See Using Controls for more information on what these do. Control targets are almost always bound to MIDI continuous controllers.

Control Targets

The Parameters tab will have a list of all the built-in loop and track parameters.

Global parameters are not on this list.

Parameter Targets

Parameter bindings are relatively uncommon, but one use for them is to bind a MIDI continuous controller to a parameter with a fixed set of values such as Quantize Mode. The MIDI controller range will be divided by the number of values in the parameter. With the MIDI controller at zero the first parameter value is selected, with the MIDI controller at 127 the last parameter value is selected. Other parameter values are selected as the MIDI controller sweeps between 0 and 127.

The Configurations tab will have a list of all the user-defined presets, setups, and extended MIDI bindings.

Configuration Targets

The name of the configuration will be prefixed with Preset:, Setup:, or Bindings: to indicate what it is. The example above shows a few of each type. If you are running Mobius for the first time, you should see only one preset and one setup in the list named "Default".

Configurations are commonly bound to MIDI program changes though MIDI notes and computer keys may also be used. When this trigger is received the preset, setup, or binding set is made active.

4.1.4 Selecting a Scope

The Scope selector restricts the target to a particular track or track group. When the scope is Global the binding is performed in currently selected track, this is the most common binding scope. The scopes Track 1 through Track 8 force the binding to be performed in a specific track no matter which is currently selected. The scopes Group A through Group D force the binding to be performed on all tracks in one of the track groups.

Scope Selector

The most common use for scoping is to assign different MIDI continuous controllers to specific track Controls such as Output Level. This is typically done with control surfaces that have groups of faders and knobs similar to a mixing console. Each group of faders and knobs can be scoped to a specific Mobius Track.

When you are just getting started we recommend you only use Global scope. The Advanced Control section of the Exploring Mobius manual has more detail on the use of binding scopes.

4.1.5 Binding Arguments

The Arguments text field is used to enter one or more words and numbers that can change the way the binding operates. This is an advanced topic covered in the Binding Arguments section of the Exploring Mobius manual.

The Mysterious Arguments

4.1.6 Trigger Binding Fields

Between the Scope selector and Arguments are fields that define the binding trigger.

These will change depending on the trigger type and are discussed in more detail in the sections below. This example shows the trigger fields for MIDI bindings.

MIDI Trigger Fields

4.1.7 Command Buttons

Under the Bindings panel are the Command Buttons which are used to create new bindings, update existing bindings, and delete bindings.

Command Buttons

To create a new binding select a target, scope, and trigger and click New, a new binding will be added to the list. To delete a binding select it in the binding list and click Delete. To modify a binding select it in the binding list and notice that the target, scope, and trigger components change to have the values for the selected binding.

Now change the target, scope, or trigger and click the Update button. The previous binding is changed to have the new values.