Frigate NVR Updates: Detector Cleanup and Bounding Box Fix
Frigate merged a fix for a bounding box format bug affecting object detection post-processing, and opened a PR to remove the DeGirum detector, continuing a trend of consolidating and hardening the detector backend.
Duration: PT2M7S
Episode overview
This episode is a short developer briefing from Frigate NVR Updates.
It explains recent repository work in plain language.
- Show: Frigate NVR Updates
- Published: 2026-08-01T13:13:35Z
- Audio duration: PT2M7S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good morning. It's August 1st, 2026, and this is Frigate NVR Updates.
Today's activity centers on one theme: cleaning up and correcting the object detection pipeline, particularly the code that handles model output across multiple hardware backends.
The headline fix comes from PR 23876, merged by Josh Hawkins. It corrects the box format being passed into OpenCV's non-max suppression function, a bug tracked in issue 23875. This function is responsible for filtering overlapping detection boxes down to the most confident result. Getting the format wrong there can…
The second theme is active pruning of the detector list. PR 23882, opened right after the NMS fix, proposes removing the DeGirum detector entirely, along with its associated requirements and model wheels. Coming right on the heels of a bug fix in shared detector code, this reads as part of a broader effort to…
For developers running Frigate: if you use Edge TPU, TFLite, MemryX, or RockChip hardware, expect improved detection reliability from the merged fix. If you're running DeGirum, watch this PR closely since removal would mean planning a migration to another supported detector.
What's next: PR 23882 is still open, so the…