Skip to content

Recording Config

Configures all recording devices and their automation behavior.


When enabled, recording starts automatically on all configured devices as soon as timecode begins running. Eliminates the need for an operator to manually start recording at the top of each take.

When enabled, recording stops automatically when timecode stops. The delay (seconds) setting adds a buffer after TC stops before the stop command is sent — useful to capture a few extra seconds of trailing action and to avoid stopping on a brief TC hiccup.

When enabled, if timecode jumps backward or forward by more than the threshold (seconds), the current recording is stopped and a new one immediately starts. This creates a clean file at the new TC position rather than a file with a discontinuous jump embedded in it.

Useful when jumping between blocks during rehearsal — adjust the threshold carefully so it does not trigger on short TC loops or brief rewinds.

When enabled, if timecode ran for less than the threshold (seconds) before stopping, the recording is automatically cancelled. If timecode ran for longer than the threshold, the recording is kept normally.

Useful for avoiding a build-up of unwanted recordings when someone plays just a few seconds of timecode to check the system — a brief test run never becomes a real recording entry.

When enabled, recordings that are cancelled are automatically removed from the database. This applies to recordings cancelled by the Cancel Short Recordings rule above, as well as recordings stopped manually within that same duration threshold. If “Permanently delete files when removing entries” is also on, the video file is deleted from disk as well.


How many seconds before a range’s start timecode a recording is considered to belong to that range. This affects the Review module’s range filter: if a recording started 3 seconds before a range began, a Pre-Roll of 5 seconds would still associate that recording with the range correctly.

Set this to a little more than your typical pre-roll buffer to ensure recordings are reliably captured under the correct range.


Makes OBS recordings stored on the server machine available over the local network to the Review module and the Notepad note detail view. Requires OBS to save files to a path the CueCollab server can read.

When enabled, users on other devices can stream and review OBS recordings directly in their browser without copying files manually.

Permanently Delete Files When Removing Entries

Section titled “Permanently Delete Files When Removing Entries”

When a recording entry is deleted from the database (manually or via Cleanup), the corresponding video file is also deleted from disk. This cannot be undone. Disable this if you want to keep video files even after removing them from CueCollab.


When enabled, recording filenames follow a configurable pattern instead of the device’s default naming. Available placeholders:

{year} {month} {day} {hour} {minute} {second} {rangeFilename} {rangeText} {rangeTimecode} {recorderLabel} {showName}

Example: {showName}_{rangeText}_{year}{month}{day}_{hour}{minute}{second} produces MyShow_Act1_20250115_142305.

Make sure your template always produces unique filenames — including a time component ({hour}{minute}{second}) is strongly recommended to prevent accidental overwrites when recording the same range multiple times.


The device list shows all configured recorders with their type, connection endpoint, and current live status. Each device can be individually enabled or disabled without removing it from the configuration.

Add Device opens a setup dialog. Two device types are supported:

Connects via the OBS WebSocket server (enable via Tools → WebSocket Server Settings in OBS). Enter the endpoint as ws://<IP>:<port> — the default OBS WebSocket port is 4455, so for a local instance: ws://localhost:4455. Set an optional password if OBS WebSocket authentication is enabled.

OBS devices connecting to localhost are automatically designated as “Local OBS” and can serve recordings for in-browser review.

Connects to a Blackmagic HyperDeck via its Ethernet control protocol on TCP port 9993. Enter the HyperDeck’s IP address on your local network.

If no local OBS device is configured, a step-by-step setup wizard appears. It guides you through: enabling the OBS WebSocket server, configuring OBS output format to Hybrid MP4 (required for reliable in-browser streaming), adding the Recording Overlay as a browser source in OBS, and confirming the connection before adding the device.