Move Finishes But Flair Stays in Post-Roll for Many Seconds¶
Summary¶
After a move completes, Flair appears stuck in post-roll — the system does not return to Ready state for an unexpectedly long time (sometimes 10–30+ seconds). The cause is a trigger event (camera record stop, bloop, or other output) that has been programmed at a frame number beyond the last waypoint of the move. Flair waits to reach that trigger frame before exiting post-roll, even though the motion has already finished.
Symptoms¶
- Move finishes (robot stops at end position) but Flair stays in post-roll / not-ready state
- Delay is consistent and repeatable — same long pause every run
- Delay is proportional to how far past the end of the move the rogue trigger was placed
- System does eventually recover, but takes far longer than expected
Cause¶
A trigger event is programmed at a frame value that is beyond the last waypoint of the move.
Examples: - Camera record stop set at frame 1500 but move ends at frame 1000 - Bloop light trigger at frame 200 post-roll when move ends at frame 100 - End trigger inherited from a previous project and not cleaned up after editing
Flair calculates post-roll based on the last trigger event, not the last waypoint. If a trigger is set 500 frames past the end of motion, Flair runs out those 500 frames before declaring the run complete.
Fix¶
- Open Setups -> Trigger Setup or Setups -> External Camera Setup / Camera Record, depending on whether the event is a normal output trigger or camera record trigger.
- Review all programmed trigger events
- Identify any trigger whose frame value exceeds the last waypoint frame of the move
- Delete or reposition those triggers to within the move duration
- Re-run to confirm normal post-roll behaviour
Check camera record stop trigger
The most common offender is the camera record stop trigger. If auto-stop was set up and the frame value was not updated after the move was shortened, the stop trigger will still be at the old (longer) frame value.
Verification¶
After fixing: - Post-roll should complete within 1–3 seconds of the robot stopping - Run time should match the expected duration of the move plus normal post-roll margin
References¶
- Flair Operator Manual — Triggers / Camera Record Setup (Flair Classic — Ch.19 Inputs, Outputs & DMX: Triggers On/Off — p.286 · Flair 7 — Ch.16 Inputs, Outputs and DMX: Triggers On/Off — p.236)
Official Documentation¶
WhatsApp Excerpts¶
- 2021-06-01 02:25 - ~ Oscar Molano: Is there any downside on using just the bloop when doing multiple passes?
- 2021-06-01 02:26 - ~ Simon Wakley: Sync should always be used when there’s any doubt but many shots don’t really need it
- 2021-06-01 02:44 - ~ Peter Constan-Tatos: Best way is to open up the sync window and make it small so you only see the sync pulse readout. That way it’s a reminder and also you know you’re getting sync through.
- 2021-06-01 12:50 - ~ Dan Gottesman: i’ve had it working in 6.43; I’d imagine be e it’s been in there for a while. you can check quickly by right-clicking in one of the empty areas (in between buttons), and you should be able to pull up a window that’ll let you customize the layout. it’s a list of functions with checkboxes next to them.