OSC Integration

Available

Open Sound Control (OSC) is a protocol for communication between computers, lighting desks, media servers, and other show equipment. CueForge supports OSC in both directions: OSC Cues send messages out, and Control Mapping receives OSC to fire cues and show actions.

Sending OSC from CueForge

An OSC Cue sends a message when it fires in the show:

• Target Profile (with a Manual fallback), Host, Port, and Address
• Typed arguments — integer, float, string, boolean
• A Test Send button in the cue editor fires the message immediately, so you can verify against real receiving equipment during rehearsal

Typical targets: lighting desks, media servers, QLab, Resolume, custom OSC receivers.

Receiving OSC into CueForge

CueForge receives OSC through Control Mapping. Enable the OSC listener in Settings → Triggers & Control (choose the port), then open Window → Control Mapping to author mappings from incoming OSC messages to cue actions or global show actions. Unassigned incoming messages appear in the Trigger Inbox for triage.

Note: Receiving OSC is verified with real software senders: messages are matched by address (and arguments where configured), and each message executes exactly once.

See Control Mapping and the Trigger Inbox for the full authoring workflow.

Requirements

• For sending: target device or software with OSC input enabled, its IP address and port, and a shared network or direct connection
• For receiving: the OSC listener enabled in Settings → Triggers & Control, and the sending device pointed at CueForge’s port

Test procedure

1. For sending: monitor with a tool such as Protokol or OSCulator, create a test OSC Cue, and use its Test Send button.
2. For receiving: enable the listener, send from the external device, then map the source from Sources or the Trigger Inbox’s Approve (Learn is MIDI-only in this beta) — or use the Trigger Inbox’s Test on a proposal.
3. Only after both directions behave, connect production targets.

Show safety notes

• UDP delivery is not guaranteed. Verify critical commands during rehearsal; do not rely on OSC alone for safety-critical functions.
• Verify IP addresses and ports after every network change.
• Use descriptive address patterns that are easy to debug.
• Document every OSC target in your show file.