Race Timing System: Analyze an RTSP stream

Analyze an RTSP stream

python3 camera_capture.py --source rtsp://CAMERA_ADDRESS/STREAM --live --camera finish-cam --checkpoint finish --roi 100,100,640,300 --send

You may set GA360_CAMERA_SOURCE in the environment instead of --source, particularly when a stream URL contains credentials. Only run captures you can access. The program runs in the foreground; Ctrl+C stops it. It does not install a service or run permanently. The maximum-frame bound still applies.

Live times are live arrival estimates, based on the timing computer's clock when frame metadata is processed. They are not the camera's hardware capture timestamps. Camera buffering, decoding, OCR backlogs and network latency can shift these values. --latency-ms subtracts a measured live latency estimate; it does not guarantee correction for variable delay. Synchronize clocks and validate the particular camera path before treating estimates as race crossing times.

--send prompts for the local receiver password (or uses ZEBRA_TIMING_PASSWORD) and sends observations to http://127.0.0.1:8765 by default. --receiver https://TIMING_COMPUTER:8765 supports a different, certificate-verified receiver. This is the local timing password, not the Hub API key. No credentials are stored in the detection log. The capture program blocks redirects and remote plain HTTP.