Why Is Frigate Recording Audio Out of Sync with Video?
- Input stream timestamp irregularity
- ffmpeg transcode buffer behavior
- camera stream profile mismatch
Problem Description
Frigate recordings play back with audio that gradually drifts out of sync with the video — audio leads or lags by several seconds in longer recordings. This is caused by mismatched audio/video clock sources, UDP packet loss dropping frames from one stream, incompatible audio codecs, or a camera firmware bug in the RTSP stream itself.
Why This Happens in Real Homes
Why this happens in real homes usually comes down to environment and timing, not instant hardware failure. Recorded clips play with noticeable audio-video timing mismatch. The pattern people actually report is Audio lags video, sync drift increases, and live view may look normal
The most common real-world triggers are Input stream timestamp irregularity, ffmpeg transcode buffer behavior, and camera stream profile mismatch. The fix is most reliable when the sequence is followed exactly: Check source stream timestamps, then Tune transcode settings, then Verify long-clip sync. After the repair, run multiple command and automation checks so the issue does not reappear later in the day.
Symptoms
- Audio lags video
- sync drift increases
- live view may look normal
Recognize these? Here's what usually causes it.
Common Causes
- Input stream timestamp irregularity
- ffmpeg transcode buffer behavior
- camera stream profile mismatch
Most fixes happen in the first 3 steps.
Do not tune only short clips when drift appears over time.
Tools & Requirements
Step-by-Step Solution
Check the camera audio codec and sample rate
Audio/video sync issues often start at the camera level. Log into your camera's web interface and check the audio settings. Set the audio codec to AAC (not G.711 or PCM) and the sample rate to match the video stream framerate timing. AAC at 16000 Hz is the most compatible option. G.711 can cause sync drift over long recordings because its fixed sample rate does not adapt to variable video frame timing. If the camera only supports G.711: Frigate can transcode to AAC, but this adds CPU load.
Use a consistent container timestamp for audio and video
Sync drift happens when audio and video streams use different clock sources. In FFmpeg (which Frigate uses internally): the -use_wallclock_as_timestamps 1 input flag forces both streams to use the same wall clock, preventing drift. However, this is an advanced setting. First try the simpler approach: in frigate.yml, use the preset-record-generic-audio-aac output args preset, which includes proper audio sync settings. If you have custom FFmpeg output args: make sure they include -async 1 for audio stream sync correction.
Verify the RTSP stream itself is in sync
Test the raw camera RTSP stream outside of Frigate to determine if the camera outputs sync or if Frigate introduces it. Play the stream directly: ffplay rtsp://user:pass@camera-ip/stream. Watch for 10+ minutes. If audio drifts in ffplay: the camera firmware has a sync bug — check for firmware updates. If ffplay stays in sync but Frigate recordings drift: the issue is in Frigate's recording pipeline. Report the specific camera model and firmware version to the Frigate GitHub issues if this is the case.
Use TCP transport instead of UDP for RTSP
UDP packet loss causes frames to be dropped from either the audio or video stream independently. When video drops a frame but audio does not (or vice versa): the streams gradually go out of sync. Switch to TCP transport: in frigate.yml FFmpeg input args, add -rtsp_transport tcp. This eliminates packet loss at the cost of slightly higher latency. For recording purposes (not live view): the latency tradeoff is irrelevant and TCP should always be used.
Re-mux recordings with FFmpeg to fix existing files
For recordings already saved with audio sync issues: you can fix them by re-muxing without re-encoding. Run: ffmpeg -i input.mp4 -c copy -af aresample=async=1 output.mp4. The aresample filter with async=1 stretches or compresses audio to match the video timeline. For batch fixing: script this across all recordings in a directory. This does not re-encode (fast, no quality loss) — it only adjusts the audio timing metadata in the MP4 container.
Quick Solutions
Still having issues? This is usually the deeper cause below.
If pairing fails after multiple attempts, the device may still be registered to a previous account — factory-reset it before trying to add it to a new one.
A/V sync should be validated under sustained recording conditions.
Pairing failures almost always come down to distance during the initial handshake — manufacturers seriously understate how close you actually need to be.
- Input stream timestamp irregularity
- ffmpeg transcode buffer behavior
- camera stream profile mismatch
Before you go — try one of these (they fix most cases).
Official Manufacturer Manual
Frigate provides official product documentation through their online manual rather than downloadable PDF. Access setup guides, troubleshooting steps, and product specifications for your Frigate Audio Sync Drift.
Source: docs.frigate.video
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.
Accessories owners commonly pair with Frigate Audio Sync Drift.
SANDISK 64GB Extreme microSDXC UHS-I Memory Card with Ada...
SANDISK 128GB Ultra microSDXC UHS-I Memory Card with Adap...
SANDISK 64GB Ultra microSDXC UHS-I Memory Card with Adapt...
As an Amazon Associate we earn from qualifying purchases.