Sync
The Sync & Timing card chooses how RigFX clocks its pipeline, where its timecode comes from, and when each frame is computed and sent.
The top of the card shows the timecode, the measured frame rate and the lock state. The REF and TC lights on the right show which signals the sync hardware receives.
Timecode source
| Source | Description |
|---|---|
| Hardware | The timecode of the sync hardware (the default). |
| OpenTrackIO | The timecode carried by the incoming OpenTrackIO stream, for example the camera's own clock. |
A short status beside the selector says what is in use. When OpenTrackIO11 is chosen but its stream is absent, carries no timecode or runs at a different frame rate, RigFX uses the hardware timecode and the status gives the reason.
Sync mode
| Mode | Description |
|---|---|
| Freerun | RigFX runs on its internal clock at the Target framerate. |
| External | RigFX locks every frame to the external Ref (Genlock7) signal, or to the timecode signal. |
The signals, the frame rates each one supports and the cabling are on Hardware → Genlock / Sync. If you plug both Ref and Timecode, they must come from the same sync generator: two sources drift apart over time.
The Ref lock also shows on the Ref LED, and the timecode on the Timecode LED (LED indicators).
Double-rate frame rates
50, 59.94 and 60 fps lock to a 25, 29.97 or 30 fps timecode. With a 25 fps timecode you can set the Target framerate to 50: the unit runs at twice the timecode rate, and numbers the frames of each timecode second from 0 to 49.
Target framerate
The expected frame rate of the Genlock7 signal (or, in Freerun mode, the rate RigFX runs at). The status line just below confirms the observed FPS — these two should match. If they don't, your reference signal is at a different rate.
In External mode, choosing the right Target framerate helps the signal lock to the right frequency quickly.
Lock status
When sync is locked, the status under the timecode shows Locked with the actual measured framerate. If the sync hardware is missing, stops answering or receives no reference, the card says so and what to check.
Drop-frame
Sets drop-frame timecode, for the 29.97 and 59.94 fps rates only (the switch is greyed out at other rates).
Jam-sync
Without a timecode on its input, the unit counts its own timecode. To set it to the studio's time, plug the studio timecode in for about 10 seconds, then unplug it: see Hardware → Genlock / Sync → Timecode.
Phase offset
Set the Phase offset12 in ms, with the slider or the number box. It defines how long the device waits after receiving the external genlock pulse before triggering its own internal Genlock7: data that arrives before that moment is used for the frame, data that arrives after it waits for the next one.
The phase offset goes from 0 ms to 90 % of a frame period at the current frame rate (36 ms at 25 fps, 18 ms at 50 fps). When the frame rate goes up, a larger offset is brought back to the new limit. The easiest way to set it is in the Phase View.
When no sync pulse arrives and the unit runs on its own clock, the phase offset is not applied: the PHASE marker is greyed out.
Output at Pulse
| Setting | Description |
|---|---|
| Off | Tracking packets are sent as soon as the frame is computed, just after the Phase offset12. |
| On | Tracking packets are held and sent on the next sync pulse, so they leave at the same moment of every frame. |
Phase View
The Phase View shows one frame, from one sync pulse (TICK) to the next, with a lane per source. Each dot is a packet, placed where it arrives in the frame:
- the PHASE marker is the Phase offset12: packets left of it are used for this frame, packets right of it (drawn orange) are used one frame later;
- the blue mark shows when the output leaves.
On the right of each lane: the packet rate, the median arrival time and the jitter. Drag the PHASE marker to set the offset, or double-click it to type a value. Place it after the packets of the sources you use, with some margin for their jitter.
^ and the Phase View](../../assets/screenshots/settings_sync.webp)