

Any MIDI controller with rotary controls can be used in the same way.Ī cue is played and its master audio level slider is controlled with an external MIDI controller. In this video, the rotary control is configured to send control change 1 messages on MIDI channel 11. The Akai LPD8 is a simple controller, with eight fixed-travel rotary controls (i.e. Example 1: Akai LPD8 controlling the master audio level of the selected cue It goes on to explore MIDI control of other cue parameters. It then develops this technique to control the master audio level using an endless-travel encoder, and shows an example of a MIDI device controlling stems of a multitrack audio cue. This method is then expanded upon so that the controller will pick up the QLab slider only when the controller value matches the equivalent slider level, avoiding level jumps. It begins with a simple method for controlling the master audio level slider of a selected cue using fixed-travel rotary MIDI controls. This chapter describes a method for controlling audio level sliders in Audio and Fade cues using standard MIDI control surfaces an no additional software. For example, you could configure OSCulator to translate MIDI control change 1 to a /cue/1/sliderLevel command, allowing the MIDI controller to adjust the master audio level of cue 1. To use these controllers but still claim the benefits of OSC, third-party tools like OSCulator can accept MIDI messages and convert them to arguments in OSC messages.
#NATIVE INSTRUMENTS CONTROLLER EDITOR SCRIPTS SOFTWARE#
Unfortunately, although there are many ways to produce OSC messages using software with virtual faders and switches, most hardware controllers still use MIDI, not OSC.


Through pattern matching, wildcards, and special QLab addresses such as selected and active, control can be directed precisely where it is required. OSC is far more suitable for external control of QLab parameters. The methods that other programs use to bind MIDI controllers to software parameters would be difficult to incorporate in a way that would be applicable for every use. QLab has a whole audio mixer in every Audio cue, and many parameters across all cue types. QLab allows some use of MIDI controls, but it’s limited to several specific areas and is not comprehensive. Many digital audio workstations (DAWs) and audio performance tools like MainStage or Live use MIDI to allow you to bind a hardware control like button, fader, or knob to a particular software control like a volume slider or an on/off button for an effects bus.
