NickM-27
commented
1 year ago I see a few things here that could be improved.
- You should be using ffmpeg presets, these are not the same as the args you are running and will reduce CPU usage
ffmpeg:
hwaccel_args: preset-vaapi
output_args:
record: preset-record-generic-audio-aac- your go2rtc config is not correct, you have
frontdoorbut no camera in the go2rtc config named frontdoor
it should be
go2rtc:
streams:
camera1:
- rtsp://xxx:xxx@192.168.222.333/live
- ffmpeg:camera1#audio=opus # <- needs to match the name of the camera for this config
webrtc:
candidates:
- 192.168.222.333:8555
- stun:8555For audio, I tried both "aac" and "opus", but I cannot get audio from mse, and I cannot get webrtc to work at all (spin wheel forever).
please provide an ffprobe (can be retrieved from system page) with your cameras settings.
Also, I do not quite follow how I can use my go2rtc setting to replace my current camera setting (as present in the attached config).
Just follow the docs https://deploy-preview-4055--frigate-docs.netlify.app/configuration/restream#reduce-connections-to-camera
Looks using go2rtc is to reduce connections to cameras. But it will likely increase CPU usage? How does it use hardware acceleration? If it simply copies the stream (which I guess is CPU's job), looks hardware acceleration is not that useful here?
go2rtc is used to provide the mse / webrtc live views, reduce connections to the camera, and can be utilized for many other things as well. I have not seen CPU usage that high, but hardware acceleration is only used if you are transocding your stream (like h.265 -> h.264).
I have Frigate integrated with Home Assistant (HA). If I understand correctly, it uses rtmp to send over the stream to HA. I get rtmp is deprecated. If go2rtc incurs heavily on CPU and bring down the host, does it mean that there is no way to integrate with HA?
There were some reports in the early betas of issues with go2rtc performance but at this point I have not heard of it. For now RTMP can be used but it is deprecated and will be removed in a future version, it also uses some CPU as well.
my-umd
Describe the problem you are having
I have read the document but still cannot fully get it to work. I trimmed down my config to include only one camera. Please check the attached config.yml file. For audio, I tried both "aac" and "opus", but I cannot get audio from mse, and I cannot get webrtc to work at all (spin wheel forever). Also, I do not quite follow how I can use my go2rtc setting to replace my current camera setting (as present in the attached config).
Looks using go2rtc is to reduce connections to cameras. But it will likely increase CPU usage? How does it use hardware acceleration? If it simply copies the stream (which I guess is CPU's job), looks hardware acceleration is not that useful here?
I have Frigate integrated with Home Assistant (HA). If I understand correctly, it uses rtmp to send over the stream to HA. I get rtmp is deprecated. If go2rtc incurs heavily on CPU and bring down the host, does it mean that there is no way to integrate with HA?
Thanks for your help.
Version
0.12.0-7D589BD
Frigate config file
Relevant log output
Frigate stats
Operating system
Other Linux
Install method
Docker CLI
Coral version
Other
Any other information that may be helpful
Wyze cam v2 with rtsp firmware.