xtouch mini osculator to atem midi template

Xtouch mini osculator to atem midi template full#
Xtouch mini osculator to atem midi template software#

For the purposes of the video, a 0.1 second post-wait has been added to all the cues to make it easier to follow visually. Here’s a video of the Network cues in QLab, triggered by incoming MIDI CC messages.

Xtouch mini osculator to atem midi template full#

The full table would have all 128 rows this just shows the first, middle, and last rows. In actual table form, it might look like this: Cue Slider level in dB = round(minimum + ( step value * controller value))Īs an example, if the knob is turn to a value of 50, we calculate the level of the slider like this:Įffectively, we’ve created a lookup table inside QLab consisting of 128 Network cues, each responding to a single specific level from the incoming MIDI CC value and sending a single specific dB level to the selected cue in QLab. In this case, a 70 dB range results in a step value of 0.551181102362, which is 70 divided by 127.Ī resolution of 1 dB is adequate, so we can create a rounded value for the slider using this formula: The step value = (the maximum - the minimum) / 127 The conversion between each increment of the MIDI value to a corresponding change in dB can be calculated with this formula: If the minimum audio level of the workspace is set to the default -60 dB and the maximum is the default 10 dB, that equates to a 70 dB range across the 128 possible MIDI controller values. Each Network cue outputs an OSC message setting the master audio level slider in the selected Audio cue to the equivalent level in dB. So, one Network cue is created for each possible controller value, with the MIDI trigger for each cue set to the corresponding value. The knob on the MIDI controller can send 128 possible values, as defined by the MIDI specification.

The Network cues send OSC messages such as this one to QLab: The workspace acquires MIDI data from the controller and processes it into QLab slider values by using MIDI triggers assigned to Network cues. The Akai LPD8 is set up like this:Ī configuration file for the Akai editor is included in the example download. 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.

Xtouch mini osculator to atem midi template 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.