10.42 appears on the livestream. Who typed it?

An athlete crosses in 10.42 seconds; moments later a clean lower-third graphic slides onto the livestream. Now the question nobody watching asks: who typed that? At many events, a broadcast operator, squinting at a results screen, retyping numbers by hand, live, under pressure. Occasionally 10.42 becomes 10.24 in front of every viewer and screenshot-taker on the internet — arguably the most public place a timing error can appear.

Let the data walk itself over

vMix can fill its graphics templates from a data source instead of a keyboard. Connect that source to the timing workflow and the chain becomes: Lion Timing records and approves the result → the plugin hands over race, name, place, and time as structured data → vMix drops each value into its labelled slot. The broadcast operator still decides when the graphic goes on air; what disappears is the retyping, and with it the retyping errors.

The two failure modes worth designing against

The wrong value in the right slot: automation is obedient, not intelligent — test with long names, ties, disqualifications, blank fields before the event. The right value at the wrong moment: feed it approved results only; a provisional first reading that auto-publishes is the approval-gate mistake at broadcast speed. And when the connection drops, graphics don’t go blank — they go stale, so the workflow should show the age of its data and offer a manual fallback.

Next in the Academy: The fastest typist on race day shouldn’t be a human →