[Support]: OpenCV exceptions, corrupt segments and watchdog errors caused by invalid ffmpeg audio preset #19732
Replies: 3 comments 1 reply
-
|
Your analysis is correct: using the wrong FFmpeg audio preset—such as To ensure reliable recording with audio, you should use the ffmpeg:
output_args:
record: preset-record-generic-audio-aacIf your camera source already outputs AAC and you want to avoid unnecessary transcoding, you can use The documentation highlights that using the correct preset is necessary for audio to work, and that using an unsupported preset for your camera's audio format will break recordings(1)(2). The user interface may not always detect this immediately, so it's important to check logs for errors after configuration changes. For more on FFmpeg presets and audio compatibility, see: 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
Not sure what you mean, mp4 doesn't support PCM audio. It is entirely related to audio.
There will be errors in the logs, currently the UI isn't aware of recording specific stream errors though this has already been improved for the next version |
Beta Was this translation helpful? Give feedback.
-
That's great ! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the info. It helped to me with some Tapo C200 which were working fine with version 0.15 and not with 0.16. Just change the ffmpeg output args from preset-record-generic-audio-copy to preset-record-generic-audio-aac following your recommendation and now it wortks fine. Same codec missing, pcm_alaw. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
I updated from Frigate 0.15 to 0.16 without changing my config file (wanting to let the "auto configuration update" do its work first).
After Frigate restarted, everything seemed fine in the UI, all cameras were apparearing, and Frigate's status was "System is healthy".
However, looking further, I had several new errors showing in the logs:
And indeed I was unable to replay recent recording from the 4 cameras identified in the logs, so they were not recorded !
I started by searching for the OpenCV exception on the web, but it gave nothing recent related to the new 0.16, and it was generally considered as something to ignore. However in my case, 4 recording streams were KO whereas they were OK just before updating to 0.16, so I couldn't ignore it.
I knew these cameras were outputting G711 instead of AAC, and having read the release notes about the breaking changes, especially those related to go2rtc audio, I knew I still had to modify the config file about the ffpmeg audio preset, and so I did. After using the "preset-record-generic-audio-aac" preset instead of "...-copy", everything went back to normal.
So, what I consider bugs is:
Steps to reproduce
My understanding of the problem is this:
Version
0.16.0-c2f8de9
In which browser(s) are you experiencing the issue with?
Firefox 142
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Sorry I don't have them, but I could see the relevant streams by clicking on them in the Go2RTC UIOperating system
Proxmox
Install method
Docker Compose
Network connection
Wired
Camera make and model
Cheap Ali Express: PG2185I (Panoeagle?) and USAFEQLO IF56N53
Screenshots of the Frigate UI's System metrics pages
Sorry I didn't take any screenshot of that
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions