- Timestamp/PTS issues from the camera
- FFmpeg audio/video sync handling
- go2rtc restream timing
Problem Description
Frigate recordings play back with audio noticeably out of sync with the video — voices do not match lip movement, or sounds occur before or after the corresponding visual event. The audio-video drift usually starts at the camera level where the audio encoder clock runs at a slightly different rate than the video encoder, and accumulates over longer recordings.
Why This Happens in Real Homes
Frigate recording audio drifting out of sync is a timestamp (PTS) handling issue between the camera's stream and how FFmpeg muxes it — cameras sometimes send irregular or variable-frame-rate streams with imperfect timestamps, and small errors accumulate over a clip into a noticeable lip-sync drift. Audio transcoding can add to it.
The common fixes are on the FFmpeg/go2rtc side: adjust the record FFmpeg args to correct A/V sync, or route the stream through go2rtc to normalize the timing before Frigate records it. Prefer a constant-frame-rate stream from the camera where possible, and address any camera-side clock or keyframe irregularities. Testing the main stream versus the sub-stream can isolate which stream introduces the drift.
Symptoms
- Recording audio out of sync
- Lip-sync off in recordings
- Audio drifts in playback
- Sound ahead/behind video
- Sync worsens over the clip
- Audio desync on record
- Out-of-sync clips
- Timing off in recordings
Recognize these? Here's what usually causes it.
Common Causes
- Timestamp/PTS issues from the camera
- FFmpeg audio/video sync handling
- go2rtc restream timing
- Variable frame rate stream
- Camera clock/stream irregularities
- Audio codec/transcode timing
- Config args affecting sync
- Camera stream instability
Most fixes happen in the first 3 steps.
Do not change multiple stream parameters at once when tracking sync drift.
Tools & Requirements
Step-by-Step Solution
Check the camera audio and video stream settings
Audio sync issues usually start at the camera level. If the camera encodes audio (AAC or G.711) separately from video (H.264/H.265) with different clock sources: the streams drift apart over time. Log into your camera's web interface and check: audio codec (set to AAC for best compatibility), audio sample rate (set to 8000 or 16000 Hz), and video GOP (group of pictures) interval (set to 1-2 seconds). Long GOP intervals cause Frigate to start recording on a non-keyframe, which can create initial sync offset.
Match the record stream codec to FFmpeg expectations
Frigate records the raw stream from the camera — it does not re-encode. If the camera sends audio in G.711 (PCMU/PCMA) but the container format expects AAC: the muxing can cause sync drift. Set the camera audio codec to AAC and video to H.264 for the most compatible combination. In frigate.yml, you can add output args to remux correctly: ffmpeg: output_args: record: preset-record-generic-audio-aac (check Frigate docs for the exact preset name).
Reduce the recording segment length
Frigate records in segments (default 10 seconds). Audio drift accumulates over time — a 1ms drift per second becomes 600ms over 10 minutes. Shorter segments reset the sync point more frequently. Try: record: retain: mode: motion, segment_length: 5. Shorter segments create more files but each one starts with fresh audio-video synchronization. This is a workaround, not a fix — the root cause is usually the camera's audio clock.
Update camera firmware
Audio sync bugs are common in IP camera firmware. Manufacturers frequently release firmware updates that fix the audio encoder timing. Check your camera manufacturer's support page for firmware updates. After updating, test a 5-minute recording and check if audio stays in sync throughout. If audio sync improves but is not perfect: the camera's hardware clock may have limited accuracy — some cheaper cameras have noticeable audio drift that no firmware can fully fix.
Use a separate audio source if camera audio is unreliable
If the camera's built-in audio consistently drifts: consider using a separate audio source. Some Frigate setups use a dedicated microphone connected to the Frigate server and merge the audio in post. However, this is an advanced configuration. For most users: switching the camera audio to AAC and reducing segment length is sufficient to keep audio sync within an acceptable range (under 200ms drift per minute).
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 issues are easier to isolate with controlled test clips of fixed duration.
Pairing failures almost always come down to distance during the initial handshake — manufacturers seriously understate how close you actually need to be.
- Timestamp/PTS issues from the camera
- FFmpeg audio/video sync handling
- go2rtc restream timing
- Variable frame rate stream
- Camera clock/stream irregularities
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 AV Sync.
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 AV Sync.

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.

