How it works
From a camera on the track to a film on the phone
Five steps that run on their own. No extra staff, and nothing changes about how you run the track.
Everything on this page comes off cameras working at the track. No animations, no stock footage. What gets passed round has to be the real thing, or it isn’t worth passing round.
- 01
The cameras never stop
Seven cameras hang over the Sopot track. That’s what this track needs. Nobody switches them on before a session and nobody watches them during one. The feed runs continuously, and the system knows when a run starts and when it ends.
How many cameras you run is your call. The system sets no limit, and we work the number out on the site visit. Cameras are inexpensive to replace, and one going down doesn’t stop the rest.
- 02
Everything stays on site
The feed lands on a computer at your track and is stored in short, one-minute segments. That’s what lets us pull any moment out later without scrubbing through hours of footage.
In Sopot footage sits for 30 days, then the oldest is overwritten. How many days your track keeps is down to its disks, not to a limit in the system. Nothing leaves the track until somebody orders it.
- 03
The system finds the moments
Nobody reviews the whole day. The system watches movement in the frame and cuts a clip whenever something happens: an overtake, a near miss, an incident.
The clip lands seconds after the event, and it starts before the event, so the run-up is never chopped off.
- 04
The picture hits the screens
The same footage feeds the reception wall, the operator’s mosaic and the live results. People waiting watch the track, not a screensaver.
Preview latency is under a second, so it genuinely reads as live.
- 05
The driver picks up their film
Once they’re off track, the driver scans a code, finds their shots and orders the edit. Landscape to watch, vertical for the phone.
The edit cuts several cameras together, so it comes out looking like broadcast coverage, not CCTV.
0.175
So a session leaves more than a memory.
Like the 0.175 s that came off on the last lap.
And the footage that proves where they stand.
On your side
What we need at the track
A short list. Hardware, installation, setup and upkeep are on us.
Internet at the venue
An ordinary connection is enough. Footage is stored locally, not in the cloud.
Room for the hardware
The computer and the disk take a shelf in the office. No server room.
Power near the cameras
We mount the cameras on what’s already there. Nothing gets rebuilt.
Someone to talk to
A person who knows the track and can tell us where the action actually happens.
Rather see it than read about it?
We’ll show you the system running a real session.