OSC cues allow QLab to send messages using the Open Sound Control protocol; a flexible, extensible, network-based messaging system designed as a sort of successor to MIDI.

When an OSC cue is selected, two tabs will appear in the Inspector:

• Basics
• Settings

Basics

Please refer to the section on the inspector in the Getting Started section of this documentation.

Settings

Destination. This drop-down menu shows the sixteen OSC patches, or destinations, to which QLab can send OSC messages. You can edit this list in OSC Settings.

Message Type. Select which type of message you want to send.

• QLab OSC Message. For convenience when using OSC cues to communicate with another computer running QLab, this option provides a very simple interface for sending several commonly used commands. Enter a cue number below, and choose a command to send to the remote copy of QLab.
• Custom OSC Message. This option gives you a text field to enter any OSC command. For example, to tell a remote copy of QLab to GO, enter the command /go. Multiple arguments in a custom OSC message are separated by spaces, like this:

/my/groovy/message 2 10 12

That sends message message to address /my/groovy with three integers, 2, 10, and 12, as separate arguments.

• Raw UDP String. This option allows you to send strings over UDP which will not be encoded as OSC by QLab on the way out. Some software, such as Medialon Manager, can accept commands as plaintext strings over UDP, and while this isn’t technically OSC, we use the OSC cue as the place to achieve this.

Send Message. Click this button to test-send your message.

Broken Cues

OSC cues can become broken for the following reasons:

Invalid network destination.

Assign a valid network destination in the Settings tab of the inspector. You may also need to visit the OSC section of Settings and specify a valid destination address and port for the desired patch.

Missing QLab cue number.

Fill in a valid cue number in the Settings tab of the inspector. This is only relevant for OSC cues set to the QLab OSC message type.

Invalid command parameters.

Fill in valid parameters in the Settings tab of the inspector. This is only relevant for OSC cues set to the QLab OSC message type.

No OSC message specified.

Fill in a valid OSC message in the Settings tab of the inspector. This is only relevant for OSC cues set to the Custom OSC message type.

Invalid OSC message.

Fill in a valid OSC message in the Settings tab of the inspector. This is only relevant for OSC cues set to the Custom OSC message type.

No UDP message specified.

Fill in a valid UDP string in the Settings tab of the inspector. This is only relevant for OSC cues set to the Raw UDP string type.

A license is required to reactivate this saved cue.

You’ll need to install a license in order to use this cue.