OSC Remote Control
CueCollab can be controlled remotely via OSC (Open Sound Control) messages.
This allows integration with external tools, consoles, and automation systems.
As per OSC standard, please mind the order of arguments when sending messages.
For example, if a message expects a string followed by an integer, sending them in reverse order may lead to unexpected behavior.
Quick Reference
Section titled “Quick Reference”Announcement
Section titled “Announcement”| Address | Arguments | Description |
|---|---|---|
/announcement/show | message, type, scope, showDuration, autoClose, allowClose | Send an announcement |
/announcement/clear | — | Dismiss current announcement |
Environment
Section titled “Environment”| Address | Arguments | Description |
|---|---|---|
/environment/scene | name | Set current scene name |
Notepad
Section titled “Notepad”| Address | Arguments | Description |
|---|---|---|
/notepad/create | text, author, list, timecode, scene | Create a notepad entry |
Recording
Section titled “Recording”| Address | Arguments | Description |
|---|---|---|
/recording/start | — | Start recording |
/recording/stop | — | Stop recording |
/recording/autopilot | enabled | Enable or disable Recording Autopilot |
/recording/schedule | enabled | Enable or disable Recording Schedule |
/recording/autostart | enabled |
Timecode
Section titled “Timecode”| Address | Arguments | Description |
|---|---|---|
/timecode/jump | timecode | Jump to a timecode |
/timecode/trigger | timecode | Trigger a timecode |
Announcement
Section titled “Announcement”/announcement/show
Section titled “/announcement/show”Sends an announcement to all connected clients. The announcement appears as an overlay on the targeted views and can be configured to auto-close or require manual dismissal.
| # | Name | Type | Required | Default | Description |
|---|---|---|---|---|---|
| 1 | message | string | yes | — | The announcement message text |
| 2 | type | string | no | "blue" | Color style: blue, green, yellow, or red |
| 3 | scope | string | no | "user,admin,displays" | Comma-separated list of targets: user, admin, displays, recording |
| 4 | showDuration | number | no | 300 | How long the announcement remains active, in seconds |
| 5 | autoClose | number | no | 0 | Auto-dismiss after this many seconds on the client (0 = no auto-close) |
| 6 | allowClose | boolean | no | true | Whether the user can manually close the announcement |
/announcement/clear
Section titled “/announcement/clear”Dismisses the currently active announcement on all connected clients immediately.
Environment
Section titled “Environment”/environment/scene
Section titled “/environment/scene”Sets the current scene name.
| # | Name | Type | Required | Default | Description |
|---|---|---|---|---|---|
| 1 | name | string | yes | — | The name of the current scene |
Notepad
Section titled “Notepad”/notepad/create
Section titled “/notepad/create”Creates a new notepad entry with the given text and optional metadata.
| # | Name | Type | Required | Default | Description |
|---|---|---|---|---|---|
| 1 | text | string | yes | — | The content of the notepad entry |
| 2 | author | string | no | "" | The author of the entry |
| 3 | list | string | no | "" | The list to add the entry to |
| 4 | timecode | string | no | "?" | Timecode in HH:MM:SS:FF format, "" for generic, or "?" to use current |
| 5 | scene | string | no | "?" | Scene name, "" for empty, or "?" to use current |
Recording
Section titled “Recording”/recording/start
Section titled “/recording/start”Starts the recording.
/recording/stop
Section titled “/recording/stop”Stops the recording.
/recording/autopilot
Section titled “/recording/autopilot”Enables or disables the Recording Autopilot. When enabled, recording starts and stops automatically based on timecode.
| # | Name | Type | Required | Default | Description |
|---|---|---|---|---|---|
| 1 | enabled | boolean | yes | — | true or 1 to enable, false or 0 to disable |
/recording/schedule
Section titled “/recording/schedule”Enables or disables the Recording Schedule. When enabled, all configured schedules are active and will trigger start/stop at their configured times.
| # | Name | Type | Required | Default | Description |
|---|---|---|---|---|---|
| 1 | enabled | boolean | yes | — | true or 1 to enable, false or 0 to disable |
/recording/autostart
Section titled “/recording/autostart”/recording/autostartEnables or disables the auto-start recording feature.
| # | Name | Type | Required | Default | Description |
|---|---|---|---|---|---|
| 1 | enabled | boolean | yes | — | true or 1 to enable, false or 0 to disable |
Timecode
Section titled “Timecode”/timecode/jump
Section titled “/timecode/jump”Jumps to a specific timecode position (including selecting the range) without triggering it.
This updates the current timecode display but does not trigger any other action like recording or callsheet jumps.
This command will only be executed if no other timecode source is currently active. If a timecode source is active, this command will be ignored to prevent conflicts.
| # | Name | Type | Required | Default | Description |
|---|---|---|---|---|---|
| 1 | timecode | string | yes | — | Timecode in HH:MM:SS:FF format |
/timecode/trigger
Section titled “/timecode/trigger”The equivalent to playing a single-frame timecode at the specified position.
This will trigger recording if configured and a jump in the callsheet.
This command will only be executed if no other timecode source is currently active. If a timecode source is active, this command will be ignored to prevent conflicts.
| # | Name | Type | Required | Default | Description |
|---|---|---|---|---|---|
| 1 | timecode | string | yes | — | Timecode in HH:MM:SS:FF format |