Race Timing System: Timing and detection

Timing and detection

Use Detection and timing settings for the bib/crossing ROI, sampling FPS, minimum OCR confidence and calibrated arrival-time offset. SRT's transport receive buffer is separate from the calibrated timing offset. Network feeds use live_arrival_estimate, including NDI; this does not claim device exposure-time accuracy. ROI evidence must remain under the existing 256 KB limit; select a small readable bib region rather than a full high-resolution image. Camera-only timing still requires enrolled bibs and explicit review.

Existing command-line capture also accepts these inputs:

python3 camera_capture.py --input-type srt --source 'srt://0.0.0.0:9000?mode=listener&latency=200000' --live --camera finish-srt --checkpoint finish --send
python3 camera_capture.py --list-ndi-sources
python3 camera_capture.py --input-type ndi --source 'CAMERA-HOST (Finish Camera)' --live --camera finish-ndi --checkpoint finish --send

Use GA360_CAMERA_SOURCE for connection values containing credentials; they are not printed by the capture program. File/recording and RTSP capture remain supported. CLI NDI/SRT inputs require --live; a recording-start timestamp cannot be applied to a live network feed.

Protocol/reference documentation: https://ffmpeg.org/ffmpeg-protocols.html .

Verification: 42 Python tests passed, including network-input validation, SRT option encoding, NDI copy-before-free/cleanup/discovery, managed session status/secret handling, auth/CSRF and existing timing regressions. A real local FFmpeg SRT caller/listener test decoded three evidence frames. An authenticated HTTP integration test connected a supervised SRT session, received a valid PNG preview and disconnected. All 13 embedded JavaScript blocks parsed, and simulated GUI checks exercised protocol switching and connection fields. NDI hardware/runtime reception and rendered browser layout were not available for verification.