What is Timing Lock?

Timing Lock ensures that TAKE, CUE, and TAKE OFF commands execute at precisely the same time on all overlay outputs, regardless of network latency or jitter. This is critical for automation workflows where timing must be repeatable.

How does it work?

The server and each overlay client continuously synchronize their clocks using heartbeat messages. When a command is sent, it includes a scheduled execution time. The overlay waits until that exact moment to execute, compensating for variable network delivery times.

Frame buffer explained

The timing buffer (in frames at 59.94fps) determines how far ahead the server schedules commands. A larger buffer tolerates more network jitter but adds latency between pressing TAKE and seeing the result. 10 frames (~167ms) is a good default for internet connections.

Per-output overrides

Click the "Frames" value for any output in the table to set a custom buffer for that output. This is useful when outputs have different network conditions. Click "Global" to clear the override and use the default.

Status indicators

Good = calibrated, jitter under 1 frame (16.7ms). Warn = jitter 1-2 frames. Bad = jitter over 2 frames or not calibrated. Syncing = collecting initial measurements.