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. 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.
