Fix frigate live view by capping detect FPS #204

Merged
eblume merged 1 commit from fix/frigate-detect-fps into main 2026-02-17 16:18:03 -08:00
2 changed files with 5 additions and 1 deletions
Showing only changes of commit 7d7762b5d5 - Show all commits

Fix frigate live view by capping detect FPS to 2

ONNX inference on ARM64 CPU takes ~750ms/frame, causing the detect
stream to fall behind at 5 FPS. This caps detection at 2 FPS to prevent
recording segment backlog and ffmpeg watchdog restarts. Also syncs
motion masks, zone coordinates, and alert labels from the live config.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Erich Blume 2026-02-17 16:11:45 -08:00

View file

@ -30,18 +30,21 @@ data:
roles: [detect]
detect:
enabled: true
fps: 2
stationary:
max_frames:
default: 1500
motion:
mask:
- 0.401,0.026,0.4,0.078,0.587,0.072,0.585,0.02
- 0.881,0.422,0.79,0.233,0.593,0.038,0.553,0,0.634,0,0.824,0.192,0.892,0.307
zones:
driveway_entrance:
coordinates: 0.85,0.366,0.689,0.347,0.661,0.175,0.795,0.255
coordinates: 0.85,0.366,0.781,0.35,0.734,0.222,0.795,0.255
objects: [car, dog, person]
review:
alerts:
labels: [person, car]
required_zones:
- driveway_entrance
objects:

View file

@ -0,0 +1 @@
Cap detect FPS to 2 and sync motion masks/zones from live config