Closed erkexzcx closed 1 year ago
This seems like an issue with the software h264 encoder being too slow. You could check the go2rtc config file in the go2rtc dashboard and adjust the parameters to see if it gets better.
Perhaps we should put a note in the docs that birdseye restream is only recommended when using hwaccel
This seems like an issue with the software h264 encoder being too slow.
Thank you for your reply. If this were true, then all streams should be like this. jsmpeg
however, works completelly fine.
To me, it sounds like an issue is somewhere else... 🤔
This seems like an issue with the software h264 encoder being too slow.
Thank you for your reply. If this were true, then all streams should be like this.
jsmpeg
however, works completelly fine.To me, it sounds like an issue is somewhere else... 🤔
No, that is incorrect. Jsmpeg is not encoded to h264 as it is just raw frames being sent via websocket
Is there another device you can use to view the streams? Need to test if this is a device webbrowser problem or a frigate installation compatibility problem.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the problem you are having
Here is the thing with Birdseye camera:
Here is my relevant config:
I don't have any GPU, so there is no hardware acceleration.
Here is what I mean "glitchy":
[Click me]
Red/yellowish artifacts, videos overlapping. This is visible on MSE and RTSP streams. Tried different browser and different RTSP viewers on Android - always the same glitchy view. However, it looks totally fine on jsmpeg view. :shrug: ![image](https://github.com/blakeblackshear/frigate/assets/5955795/6d9ca842-e0f1-4627-8238-e9cbcec3a375) ![image](https://github.com/blakeblackshear/frigate/assets/5955795/9143b54c-1956-4397-81e7-fcde7a1f36b2) ![image](https://github.com/blakeblackshear/frigate/assets/5955795/fbdea94c-276b-4a25-b617-955a1a104b01) Here is jsmpeg view - always work without issues: ![image](https://github.com/blakeblackshear/frigate/assets/5955795/a515d094-2177-47c6-b8b6-df6564c4bb23)Resources is not a problem:
[Click me]
![image](https://github.com/blakeblackshear/frigate/assets/5955795/45dc1b6a-5a34-4221-919b-727a78e4d502) ![image](https://github.com/blakeblackshear/frigate/assets/5955795/045eca4e-b6a4-47ad-987e-3d899c21e885) ![image](https://github.com/blakeblackshear/frigate/assets/5955795/06bd83f9-fc38-4a6c-a0a4-55d26586766c)Why would it happen? Any ideas?
Version
0.12.1-367d724
Frigate config file
Relevant log output
FFprobe output from your camera
Frigate stats
Operating system
Debian
Install method
Docker Compose
Coral version
USB
Network connection
Wired
Camera make and model
Most of them old Hikvision cameras, at least one newer Hikvision, ~5 new Dahua cameras.
Any other information that may be helpful
Bare metal server without GPU. Coral TPU accelerator works fine, max CPU usage I've seen is up to 50%. Resources usage of the host is acceptable, nothing is maxed out.