-
-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go2rtc is laggy/slow 2.0 #1698
Comments
I am guessing the WebRTC stream just isn't loading at all (for whatever reason), instead the card is trying to show you something and it's just showing you a HomeAssistant snapshot every second. You could verify this with:
... and the Frigate card will make no attempt to "cover up" if the stream doesn't load. You'd just get empty video players. Then you need to figure out why that's not loading. I'd start here and make sure you have followed all of these steps. Your Javascript console (F12 in your browser) may also show something useful. Good luck. |
show image: false helped. Doing this I realized my h264 streams were working, but my h265 streams were not. I did have the stun stuff set up, but what I discovered was it is a codec issue. webrtc needs h264 streams. Some of my 4k cams were h265, and I had my hikvision as h265. I almost had it licked, but then something happened and I can't figure that out now, lol. But one issue with h264/webrtc was with my hikvision ultra wide cams. I tried setting them to h264 native and webwtc wouldn't work. So I tried h265 and transcoded to h264, but ffmpeg said it couldn't do wider then 4096px. I tried updating gpu drivers now the whole thing is shot and I can't get it working again. Some other issue I guess. Details thanks though, your guidance did help. |
Checklist:
done and done
[REQUIRED] Card diagnostic information:
[REQUIRED] Description of problem:
webrtc doesn't work well. I have no way to test webrtc in frigate ui I don't think.
I am using opnsense as my firewall. Hass-os for home assistant, frigate integration, frigate-card. Frigate is installed in a docker container on a different machine, using frigate 0.15.0 beta 2 now.
frigate config contains
locally, and through cloudflare tunnel, the behavior is the same. if I leave the go2rtc mode as "- mse" the frame rate is full frames. But if I only use "- webrtc" I only get about 1fps.
streaming through nabu casa is very limited using mse, but won't play at all using webrtc
similar to this #1671
I tried looking for help in https://www.reddit.com/r/frigate_nvr/comments/1gwqoob/nabu_casa_and_frigate_in_a_docker_container_laggy/ too.
[OPTIONAL] Last working release (if known):
[OPTIONAL] Javascript errors shown in the web inspector:
[OPTIONAL] Additional information:
The text was updated successfully, but these errors were encountered: