[Support]: Frigate 0.14 live UI question #13521
Unanswered
gelato
asked this question in
General Support
Replies: 2 comments 21 replies
-
the only reason the live view would switch to jsmpeg is because there was some error in the MSE or WebRTC stream, either a decoding error or too many buffering errors |
Beta Was this translation helpful? Give feedback.
0 replies
-
I suspect that buffering errors might be the cause (i don't see any other errors in the log), can you tell me where in the browser to look for them? Also, is there no way to completely disable fallback to jsmpeg? It's working flawlessly until it switches to jsmpeg... |
Beta Was this translation helpful? Give feedback.
21 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem you are having
Live UI always works using jsmpeg format until i refresh the page, then it works using full-fps format for some time, like 20 minutes or so (idk which it is - mse or webrtc, i have configured both), then it switches back to jsmpeg and stays like that no matter what happens until i refresh the page again. Tried Edge and Firefox, PWA mode and simple web page - behaviour is always the same.
I know that cameras in new UI should switch to full stream when they detect an activity, but can you please elaborate on what is an "activity" in Frigate world?
Also, maybe there is a way to just disable the whole bandwidth-saving functionality and just use full MSE/WEBRTC stream for cameras? Why are we even bothered with bandwidth saving in current network environments, where i can stream 120FPS/sec 8k videos to VR headset?
Currently i'm running Frigate in Kubernetes with host network mode enabled (that doesn't matter in my case anyway, tried everything already). Hardware: x86 Intel N95 Chipset (Ninkear box), connected via wifi (3 unifi ap6 near it, rssi -60), Coral TPU connected to Frigate instance, transcoding to h264/aac with nvidia gpu, tp-link vigi cameras.
Side note: i really like new UI, it's far better than everything what Home Assistant has to offer right now, but those laggy 10fps/sec on cameras are frustrating...
Version
0.14.1-f4f3cfa
What browser(s) are you using?
Edge/Firefox latest stable
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
2024-09-03 14:22:15.530749506 [INFO] Preparing new go2rtc config... 2024-09-03 14:22:15.884380763 [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually 2024-09-03 14:22:15.935475832 [INFO] Starting go2rtc... 2024-09-03 14:22:16.134481490 17:22:16.134 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2 2024-09-03 14:22:16.134484974 17:22:16.134 INF config path=/dev/shm/go2rtc.yaml 2024-09-03 14:22:16.134548003 17:22:16.134 INF [api] listen addr=:1984 2024-09-03 14:22:16.135016990 17:22:16.134 INF [rtsp] listen addr=:8554 2024-09-03 14:22:16.139256708 17:22:16.139 INF [webrtc] listen addr=:8555 2024-09-03 14:22:25.538531083 [INFO] Starting go2rtc healthcheck service...
FFprobe output from your camera
Frigate stats
Operating system
Debian
Install method
Docker Compose
Object Detector
Coral
Network connection
Wired
Camera make and model
TP-Link VIGI C330/C230
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