Academy · Reliability

The finish that almost wasn’t recorded.

Why professional timing doesn’t depend on one person pressing one button at exactly the right moment.

The most dangerous moment on a race day isn’t a close finish. It’s a button that didn’t get pressed. The operator looks up from judging the last race — and the winner has already crossed. The camera was perfectly aligned; the image would have been superb. None of that helps if the crossing wasn’t recorded. So a serious system isn’t designed around the hope that nobody blinks. It’s designed in layers.

Layer 2: Motion detection — an extra pair of eyes

Like a motion-activated porch light: the system watches a chosen zone of its own finish-line view, and when real movement enters, it starts recording. The lone breakaway who arrives forty seconds early gets caught. And like the porch light, it can be fooled — an official crossing, a flag, a bold pigeon — which is why you set the zone and sensitivity for the real venue. It supports the operator; it doesn’t replace judgment.

Layer 3: Pre-roll — the moments from before the trigger

Any trigger reacts when the movement arrived — the front wheel may already be through. The fix: the camera never stops watching. It holds the most recent moments in a short rolling memory, and when a trigger fires it keeps the buffered moments from just before it. So the saved image can begin before its own trigger.

Layer 4: Continuous recording — the long notebook

Pre-roll protects seconds; continuous recording protects the day. Think of a notebook where every finish-line moment is written down and the important races are marked. But recording everything is not the same as finding anything — a raw day of footage is a haystack. This is where motion detection earns its second job: it organizes the record around real movement, so the backup is a tidy row of events, not hours to scrub. A backup you can’t search in thirty seconds is only technically a backup.

Layer 5: Independence — don’t put both copies in one bag

Two copies on the same computer are lost with the computer. Independence has a wonderfully practical test: unplug the cable. A backup on the operator’s laptop stops the instant the link, the laptop, or its power fails — precisely the moments a backup exists for. A camera that records on-board keeps writing evidence with the cable hanging loose. The question for any backup, ours included: what single failure would destroy both recordings?

How Lion Timing approaches this

Direct manual control, motion-assisted recording with visible status, pre-roll ahead of both manual and automatic triggers, and continuous recording that writes evidence to storage as it arrives — so Stop seals the recording rather than creating it. The backup records in the camera itself, independently of the operator’s computer, with motion detection keeping it organized. One unexpected moment should never erase a finish.

1. Motion detection triggered slightly after the wheel entered the line. Why is the wheel still in the image?

Pre-roll. The camera continuously buffers the latest moments and keeps the ones from just before the trigger — so a recording can begin before its own trigger.

2. Two recordings saved to the same computer — how safe is that backup?

Only partially — both share the computer’s power, disk, and crashes as single points of failure. A real backup avoids sharing failure points.

3. Someone trips over the camera–laptop cable seconds before the finish. What does a camera-side backup do?

The camera keeps recording on-board; the finish is retrieved once the connection returns. The recording never needed the laptop.

The explanation worth remembering

A professional system assumes the button will one day be pressed too late — and builds layers so it doesn’t matter: motion detection to notice, pre-roll to reach back before the trigger, continuous recording to keep the whole day, and an independent copy in case the first one dies.

Next in the Academy: A recorded finish is not yet a result →