How to Fix Frigate Recording Gaps During High Motion
- Storage write bottleneck
- Decoder saturation
- Over-aggressive stream settings
Problem Description
When your Frigate Frigate High-Motion Recording isn't working as expected, it usually traces back to one of a small number of causes — this guide covers them in order, starting with the most likely.
Symptoms
- Gaps during busy periods
- Dropped segments
- High CPU coincides with gaps
Recognize these? Here's what usually causes it.
Common Causes
- Storage write bottleneck
- Decoder saturation
- Over-aggressive stream settings
Most fixes happen in the first 3 steps.
Do not tune based on idle-time metrics only.
Tools & Requirements
Step-by-Step Solution
Check resource peaks
Correlate recording gaps with CPU, memory, and disk spikes.
Tune stream profiles
Reduce unnecessary frame/bitrate pressure for less critical feeds.
Retest under load
Generate controlled motion and verify timeline continuity.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If the sensor still misses events after repositioning, check whether a scheduled 'home' or 'away' mode is overriding the sensitivity setting silently.
Capacity planning should include high-motion worst-case windows.
This issue almost always looks more complex than it is — the majority of cases trace back to a single setting, a stale credential, or a default that shipped wrong.
- Storage write bottleneck
- Decoder saturation
- Over-aggressive stream settings
Before you go — try one of these (they fix most cases).
Need More Help? Frigate Support
Note: The contact information below connects you directly to Frigate's official customer support team, not Trunetto. They can help with warranty claims, device replacements, and advanced technical issues.