High FPS Sync - Flair May Read Every Other Pulse Above ~800 FPS¶

LIKELY SYNC BOTH

Summary¶

At very high camera frame rates, Flair may not detect every sync pulse. A community explanation states that beyond about 800 FPS, Flair may read one pulse every two frames. This can make the displayed detected frame appear to alternate between true frames and middle frames.

Symptoms¶

Flair appears to detect alternating real/middle frames
Behavior appears at very high FPS, above normal sync operating range
Operator expects every camera pulse to be detected but Flair reads a lower effective rate

Stable ID¶

ISSUE-SYNC-011

First Reported¶

2020-06-22 - Carlos asked why Flair sometimes detected real frames and sometimes the middle at high FPS.

Software Environment¶

Both. This is a timing/sync behavior rather than a UI-specific workflow.

Hardware¶

High-speed cameras
RT14 / sync input path
Camera sync generator / camera sync output depending on setup

Community Solution¶

[LIKELY] 2020-06-22 - User: Timothy Heys Cerchio¶

Beyond about 800 FPS, Flair cannot detect each and every pulse and may read one every two frames. A theoretical workaround is to scale the move to half the camera frame rate so the effective sync relationship remains usable.

confidence_score: 0.72

Media Text / Description¶

Media 1: 2020-06-22 20:37 - ~ Carlos

WhatsApp Excerpts¶

2020-06-22 20:37 - ~ Carlos: Hi masters!! I’m curious why the flair sometimes detect the real frames and sometimes it’s the middle. I’m know that over 400 FPS we haven’t sync but... it’s curious...¿?
2020-06-22 20:37 - ~ Carlos:
2020-06-22 20:45 - Timothy Heys Cerchio: Hi @~Carlos Not really 'scientific' (on my side) but basically beyond 800 FPS Flair cannot detect each and every pulse... So it reads one every 2 frames! 😉
2020-06-22 20:47 - Timothy Heys Cerchio: So, theoretically you could even Sync if you scale down your move to half the camera framerate 😁.