abritton2002 51dd062407 fix: VideoInfo.fps returns float instead of truncated int (#2210) ... * VideoInfo.fps returns float instead of int Truncating the raw CAP_PROP_FPS value with int() causes timing drift for non-integer frame rates (23.976, 29.97, 59.94). Over a long video this accumulates into noticeable sync errors — e.g. 23 vs 23.976 drifts ~1s per minute of footage. Changes: - VideoInfo.fps type annotation: int -> float - from_video_path: int(video.get(CAP_PROP_FPS)) -> float(...) - ByteTrack.frame_rate type annotation: int -> float (already converts to int internally via max_time_lost = int(frame_rate / 30.0 * buffer)) - Tests: assert fps is float, add float_fps_video_path fixture at 23.976 * fix: update examples to cast float fps to int where required * fix: wrap long docstring line in FPSBasedTimer (ruff E501) * test: remove unused float_fps_video_path fixture --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Jirka Borovec <6035284+Borda@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>		2026-04-13 20:05:19 +02:00
..
__init__.py	time in zone / dwell time demo (#1026)	2024-03-27 00:12:12 +01:00
general.py	feat: 🚀 dropping python 3.8 support and upgrade all codes to python3.9 syntax style as min	2025-07-14 20:12:11 +03:00
timers.py	fix: VideoInfo.fps returns float instead of truncated int (#2210)	2026-04-13 20:05:19 +02:00