Sync / Phase Lock Lost At End Of Run¶
Summary¶
An image-defined message at the end of a run was interpreted as lost sync / lost phase lock. This can happen if the sync pulse timing or frequency varies too much, stops, or is intermittently disconnected inside the sync path.
Symptoms¶
- Message appears at or near end of run.
- Sync was expected to be locked.
- Camera/sync source may be unstable or briefly disconnecting.
- Can be caused by sync-box internal false contact.
Evidence¶
Related Media¶
Media Text / Description¶
- Media 1: 2026-05-07 23:44 - Markus: Image description: end-of-run sync warning / error prompt. Chat question: "What's this, in the end of run?" Breakdown: lost sync / phase lock caused by unstable or interrupted sync pulse.
WhatsApp Excerpts¶
Media Text / Description¶
phase lock lostlost sync end of runsync pulse stoppedsync box false contactFlair phase lost- Image description: end-of-run sync warning screenshot interpreted as lost sync / lost phase lock, likely caused by unstable or interrupted frame-sync pulse.
[7/5/2026, 11:44:08 pm] ~ Markus: What’s this, in the end of run?
[7/5/2026, 11:45:01 pm] ~ Steve_Schweiger: Arri?
[7/5/2026, 11:46:09 pm] ~ Michael deAnthony: hi guys, i would like to ask, has anybody ever rigged a Sony Venice 2 Rialto on the Bolt Classic on track? Im wondering on how to manage the cable along the arm, or is it preferable to just stick with the body
[7/5/2026, 11:46:10 pm] ~ Michael deAnthony: thankss
[7/5/2026, 11:46:22 pm] ~ Łukasz Trojan: You've lost sync
[7/5/2026, 11:46:30 pm] ~ Ante: As per manual - If the timings between the system and the incoming pulse vary by too much, an error will be reported. There are two possible errors: either the frequency of the incoming pulse has varied too much in which case the system will report that synchronisation has been lost, or if the phase relationship between the system and the incoming pulse varies by more than 1/4 frame, then the system will state that Phase Lock has been lost. If this happens, then it is likely that the frequency of the sync pulse is not stable, and the computer is having trouble locking in to it. It is also possible for the sync pulse to stop completely, in this case, the computer will wait a reasonable time for it, and then will post an applicable message.
[7/5/2026, 11:50:46 pm] ~ Niko: For Sony Venice 2 Rialto you can connect up to 12 m without repeater So you can tie the cable to the arm and tie the recording unit somewhere to the base of the robot
Community Solutions¶
[LIKELY] Check Sync Source Stability¶
Confirm the camera/sync generator is outputting the correct stable frame rate and that Flair is configured for the same rate.
Confidence: 0.8
[LIKELY] Inspect Sync Box And Cables¶
Check BNCs, sync box connectors, and internal cable/false-contact possibilities if sync appears to work then drops intermittently.
Confidence: 0.76
[CONFIRMED] Treat As Different From LTC Timecode¶
This is about frame sync / phase lock, not music LTC trigger timing. Diagnose the sync pulse path first.
Confidence: 0.84
Related Issues¶
- See also: Sync Generator Stability - AJA Gen10, Blackmagic, Evertz
- See also: High FPS Sync - Flair May Read Every Other Pulse Above ~800 FPS
- See also: RED V-Raptor / Milo - Universal Sync Box Failure and Misconnection Risk
- See also: LTC Timecode Erratic / Jumping — Noise from Shared Power Supply
