OSC Setup Guide

What Is OSC?

OSC (Open Sound Control) is a network protocol for communicating between multimedia software and hardware. It sends structured messages over UDP (or TCP) to specific address paths — like a URL for a parameter value.

CueSync outputs OSC to control Resolume, QLab, TouchDesigner, Unreal Engine, Disguise, millumin, and any OSC-capable application.

Configuring OSC in CueSync

1. Go to Protocols → OSC.
2. Click Add Target.
3. Configure:

| Setting | Description | |---------|-------------| | IP Address | IP of the target application's machine | | Port | UDP port the target listens on | | Protocol | UDP (default) or TCP | | Address Prefix | Optional prefix prepended to all outgoing addresses |

Common OSC Target Ports

| Application | Default OSC Port | |------------|-----------------| | Resolume Arena/Avenue | 7000 | | QLab | 53000 | | TouchDesigner | 9000 | | Unreal Engine (OSC Plugin) | 8000 | | Disguise | 9001 | | millumin | 5000 | | CueSync (incoming) | 8888 |

All ports are configurable in each application's preferences. Check the target app's OSC settings if the default doesn't work.

OSC Message Format

CueSync sends standard OSC messages in the format:

/address/path  value

For example:

• /composition/layers/1/video/opacity 0.75 — set Resolume layer 1 opacity to 75%
• /cue/3/start — start QLab cue number 3
• /beat/energy 0.88 — forward CueSync's energy value to TouchDesigner

Mapping Audio Triggers to OSC

In CueSync's Routing Editor:

1. Click Add Rule.
2. Set Trigger to your audio event (Beat, Energy, BPM, Hot Cue, etc.).
3. Set Output Type to OSC.
4. Enter the Address and the Value or Value Range to send.
5. Optionally set a Minimum Interval to prevent message flooding.

Multiple OSC Targets

CueSync supports unlimited simultaneous OSC targets on every edition. Each routing rule can be sent to one or all targets independently.