Skip to content

Bloop Light Programmed But Not Firing

CONFIRMED RESOLVED ALL RIGS / TRIGGER BOX BOTH

Summary

A bloop light (in-frame flash light used to mark the first frame of a move) is programmed in Flair but does not fire. There are three distinct causes, each with its own fix.

Symptoms

  • The bloop light is programmed in Flair but does not flash when the move runs.
  • Flair shows the bloop trigger as active in the setup but Output 1 of the Trigger Box produces no pulse.
  • The bloop fires correctly on a manual test but does not fire during the automated run.
  • All trigger outputs are suppressed — not just the bloop — and the robot may be in Slow mode.

Background

The bloop light is a bright flash of light placed in-camera-frame, triggered by Flair at a precise frame to mark the start of a move. It is used in multi-pass compositing workflows where precise sync is not available — the bloop frame is used to align passes in post.

The bloop is typically connected to Output 1 of the MRMC Trigger Box (DB37 ribbon cable device, 12V relay outputs).

Cause 1 — Robot Not in Fast Mode

Trigger Box outputs only fire when the robot is running in Fast mode. If the robot is running in Slow mode, triggers (including the bloop) are suppressed.

Fix: Set the robot to Fast mode before running the move.

Triggers require Fast mode

This applies to ALL Trigger Box outputs, not just the bloop. If you are using any trigger output (camera record start/stop, bloop, relay) and the robot is in Slow mode, none of them will fire.

Cause 2 — Triggers Switch Not Active

The Triggers enable switch (in the main Flair window or toolbar) must be active (enabled) for any trigger to fire.

Fix: Check that the Triggers switch is on before running the move.

Cause 3 — Ultibox-Routed Bloop Needs Manual Pre-Test

When the bloop is routed through an Ultibox (rather than direct from the RT14 trigger output), there is a known timing issue where the bloop does not fire on the first run unless it has been manually tested immediately before entering Ready to Shoot.

Fix: 1. Open the Trigger Test window in Flair 2. Click Test (fires the bloop manually) to wake up the Ultibox relay 3. Immediately proceed to Ready to Shoot and run the move

Ultibox bloop quirk

This is a known Flair / Ultibox behaviour. The manual test pulse appears to prime the relay for reliable firing on the subsequent automated run. This step is only needed for Ultibox-routed outputs, not direct RT14 trigger outputs.

Checklist

Before assuming the bloop hardware is faulty, verify all three causes:

  • [ ] Robot is in Fast mode
  • [ ] Triggers switch is enabled in Flair
  • [ ] If Ultibox-routed: clicked Test immediately before Ready to Shoot

Media Text / Description

  • Media 1: 2021-08-13 07:53 - Oscar Molano asked why a programmed bloop light tested OK and was active in settings, but did not light during the move. He attached .

WhatsApp Excerpts

  • 2021-08-13 07:53 - Oscar Molano asked why a programmed bloop light tested OK and was active in settings, but did not light during the move. He attached 00005387-PHOTO-2021-08-13-07-53-30.jpg.
  • 2021-08-13 07:58 - Simon Wakley replied that triggers only fire when the robot is running in Fast mode.
  • 2021-08-13 08:01 - Oscar said it still was not turning on in Fast mode.
  • 2021-08-13 08:08 - Peter Constan-Tatos described a similar issue when bloop was routed from the UltiBox camera accessories output: opening the test window and clicking Test immediately before Ready to Shoot made the bloop work when shooting.
  • 2021-08-13 08:15 - Simon Wakley asked for software version and whether rebooting had been tried; Oscar later reported Flair 7.1.0 and said he would try rebooting.

References

Official Documentation