[Support]: history view error after update to 16.0 #19574
Replies: 2 comments 6 replies
-
|
The "track count mismatch" error you're experiencing is a known issue in Frigate v0.16.0 that occurs when there's an inconsistency between audio and video tracks in recorded segments (1)(2). This error specifically indicates that one clip has 0 tracks while another has 1 track for the same media type, preventing proper playback in the history view (1)(2). This issue appears to be related to audio recording configuration. Based on similar cases, the error often occurs when there are inconsistencies in how audio tracks are handled across different recording segments (1)(2). To troubleshoot this issue:
The error is intermittent ("Sometimes - not all the time") which suggests it's related to specific recording conditions or camera stream variations rather than a consistent configuration issue. 📚 Sources:
Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
I commented out the ffmpeg audio pieces - snippet from configuration for one of the cameras. And here is the camera config for that same camera: That particular camera is a Backstreet Surveillance camera so I do not know what "brand" it is. The audio output from the camera is G.711U. The only other choice is G.711A. I have I do have two Dahua cameras that output AAC audio -- I am not 100% positive, but I do not believe they have this history view hangup. What I have noticed trying to troubleshoot:
Is the issue related to how frigate handles G.711 audio? Should I try G.711A instead of G.711U? |
Beta Was this translation helpful? Give feedback.
-
|
AAC audio is required for recordings playback. You can try transcoding with a single stream in go2rtc, eg: |
Beta Was this translation helpful? Give feedback.
-
Yea... but if the recording won't play the audio doesn't do any good. :). The issue seems so intermittent that it is difficult to figure out what "fixes" it vs a temporary working state. |
Beta Was this translation helpful? Give feedback.
-
|
Update: I did change the audio on two of the cameras to G.711A and it cleared the history review issue -- at least for the moment. |
Beta Was this translation helpful? Give feedback.
-
|
Clearing the errors and being able to view history seems to be always a short term fix. Any ideas on a solution or work around? Not being able to view history is kind of a deal breaker. |
Beta Was this translation helpful? Give feedback.
-
|
We have not been able to reproduce the issue. Even when a user shared their exact files and database the issue was not reproducible, so it's unclear what's going on |
Beta Was this translation helpful? Give feedback.
-
|
Anything I can do to assist troubleshooting? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
Sometimes - not all the time - I get this error when I try to view history.
[error] 236#236: *8685 filter_init_filtered_clips: track count mismatch, first clip had 0 current clip has 1 media type 1 while sending to client, client: 192.168.110.127, server: , request: "GET /vod/Garden/start/1755460800/end/1755464400/seg-1-v1-a1.ts HTTP/1.1"
Version
0.16.0-c2f8de9
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
How? Streaming works correctly.Frigate stats
No response
Install method
Docker Compose
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
Mixed
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions