[Support]: Chrome Version 146.0.7680.178 not displaying feeds #22776
Replies: 1 comment
-
|
The error Your go2rtc streams are configured to use H.264 video, which should be compatible with Chrome. However, the MSE player in Chrome can be sensitive to specific stream characteristics. (1) Here are some things to try: 1. Add opus audio transcoding for WebRTC fallback Your current config only adds AAC audio. Adding opus support allows Frigate to fall back to WebRTC if MSE fails: (1) go2rtc:
streams:
reolink_garage:
- rtsp://reolink:<password>@192.168.3.58:554/h264Preview_01_main
- "ffmpeg:reolink_garage#audio=opus"
reolink_driveway:
- rtsp://reolink:<password>@192.168.3.42:554/h264Preview_01_main
- "ffmpeg:reolink_driveway#audio=opus"2. Check camera I-frame interval settings Set your camera's I-frame interval (keyframe interval/GOP length) to match your camera's frame rate, or choose "1x" on Reolink cameras. Values higher than the frame rate can cause playback issues. (1) 3. Verify video codec in go2rtc web interface Access go2rtc's web interface at port 1984 and click "stream" for your camera to verify the stream is being received correctly and check the negotiated codecs. (2) 4. Try transcoding video to H.264 If the stream format is causing issues, you can re-encode the video: (2) go2rtc:
streams:
reolink_garage:
- rtsp://reolink:<password>@192.168.3.58:554/h264Preview_01_main
- "ffmpeg:reolink_garage#video=h264#hardware"Note that transcoding is resource intensive. (2) 5. Check browser console logs Open Chrome's Developer Tools (F12 > Console tab) while loading the Live view to see detailed error messages about codec negotiation or playback failures. (1) Since this appeared after a Chrome update, it may be a regression in Chrome's video decoder. You could also try rolling back Chrome or using a different Chromium-based browser to confirm. 📚 Sources: Have another question? Just tag @inkeep. |
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
When I updated to chrome version 146.0.7680.178 I lost the ability to view video feeds in my browser.
Live feed just sits there with a spinning circle. If I go to review video, I get an error: Failed to play recordings (error 4): PipelineStatus::DECODER_ERROR_NOT_SUPPORTED: video decoder initialization failed with DecoderStatus::Codes::kUnsupportedConfig
When I swap to Safari it works perfectly.
Steps to reproduce
...
Version
0.17.1-416a9b7
In which browser(s) are you experiencing the issue with?
Google Chrome 146.0.7680.178
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Debian
Install method
Docker Compose
Network connection
Wired
Camera make and model
Reolink
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions