[Support]: Frigate cannot get streams for two cameras after upgrading to 0.16.x #20451
Replies: 2 comments 22 replies
-
|
Based on the error logs, the issue is related to audio codec compatibility. The logs show FFmpeg errors indicating that The key error messages are:
This suggests your cameras are sending PCM A-law audio, which is incompatible with the recording format. To resolve this, you need to configure audio transcoding in your go2rtc streams(2). For your affected cameras (backyard and driveway), modify your go2rtc configuration to transcode the audio: go2rtc:
streams:
backyard:
- rtsp://admin:<password>@192.168.0.51:554/live/ch1
- "ffmpeg:backyard#audio=aac" # Transcode audio to AAC instead of opus
driveway:
- rtsp://admin:<password>@192.168.0.58:554/live/ch1
- "ffmpeg:driveway#audio=aac" # Transcode audio to AAC instead of opusThe documentation recommends using AAC audio codec for the most compatible audio codec with all Live view technologies and browsers that support audio(3). Alternatively, you could disable audio for these cameras by removing the audio transcoding line entirely, or use the The reason this worked before 0.16.x is likely due to changes in how Frigate handles audio streams in the newer version. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
The AI's response is correct. This is not a Frigate bug and was a breaking change listed in the 0.16 release notes. Just transcode your audio via one of the methods suggested and you should be back up and running. |
Beta Was this translation helpful? Give feedback.
-
|
I changed to acc, still cannot get two cameras back to work |
Beta Was this translation helpful? Give feedback.
-
|
Are you saying that OpenVino on CPU is lost in 0.16, but it will return in 0.17? |
Beta Was this translation helpful? Give feedback.
-
|
Running OpenVINO on J-series GPUs is not supported in 0.16 (or officially supported by Intel in general) But with the package updates in 0.17 users have reported that it works |
Beta Was this translation helpful? Give feedback.
-
|
That is good news, but my config may not benefit from it as I am using VM on QNAP NAS. VM may not be able to access GPU hardware. |
Beta Was this translation helpful? Give feedback.
-
|
I'm not aware of any other reason CPU usage would have increased due to the update. |
Beta Was this translation helpful? Give feedback.
-
|
CPU usage went down to ~60% after a full reboot. Still high but better than 90%+ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
After upgrading to 0.16.x, two cameras became unavailable (and all associated sensors) in Home Assistant.
Steps to reproduce
...
Version
0.16.1-e664cb2
In which browser(s) are you experiencing the issue with?
No response
Frigate config file
docker-compose file or Docker CLI command
Not available. Using Frigate add-on in Home AssistantRelevant Frigate log output
Relevant go2rtc log output
Operating system
Home Assistant OS
Install method
Home Assistant Add-on
Network connection
Wireless
Camera make and model
Two generic cameras with onvif support
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Two cameras don't work, but if I click on any one of them, Home Assistant can get live streams
Two other cameras work fine, including a Reolink camera doorbell.
Before I upgraded to 0.16x, all 4 cameras worked without any issues
Beta Was this translation helpful? Give feedback.
All reactions