@TyzzyT commented on GitHub (Nov 27, 2023):
That makes a huge difference. CPU usage is down to 16.6% and ffmpeg is able to keep up with the stream. Thanks Nick!
@NickM-27 commented on GitHub (Nov 26, 2023):
also to note, you can always run detect on the main stream but use the detect -> width / height along with hwaccel to scale the stream down. For…
@monkeydust commented on GitHub (Nov 27, 2023):
You are connecting via rtmp so the rtmp input args need to be used, not rtsp
damn - yes my bad changed to "preset-rtmp-generic" and its…
@pstratem commented on GitHub (Nov 26, 2023):
I was thinking instead of decoding both streams in parallel, going back to decode the recorded stream when motion is detected.
But now that I…
@NickM-27 commented on GitHub (Nov 27, 2023):
I'd suggest using the recommended reolink config https://docs.frigate.video/configuration/camera_specific#reolink-cameras
@NickM-27 commented on GitHub (Nov 27, 2023):
You are connecting via rtmp so the rtmp input args need to be used, not rtsp
@NickM-27 commented on GitHub (Nov 26, 2023):
the stream has to be decoded to run object or motion detection, running detection separately will just lead to more resource usage because both the…
@NickM-27 commented on GitHub (Nov 27, 2023):
I would suggest trying the i965 driver instead of iHD
@Calimerorulez commented on GitHub (Dec 18, 2023):
My config:
@Calimerorulez commented on GitHub (Dec 18, 2023):
Ok, I took the plunge and migrated the Frigate container to another server, a Ryzen 5600G, using the AMD-vaapi driver, instead of the i965…
@NickM-27 commented on GitHub (Dec 18, 2023):
interesting, perhaps some issue with that particular driver / CPU then, https://github.com/blakeblackshear/frigate/pull/8604 seems like what changed
@github-actions[bot] commented on GitHub (Jan 18, 2024):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.…
@Calimerorulez commented on GitHub (Dec 18, 2023):
Just upgraded to beta 7, and there's the same behavior as in beta 6, reverting back to beta 5, because that runs fine.
I can't explain why,…
@NickM-27 commented on GitHub (Dec 18, 2023):
what is your current config and also what CPU is this again?