#Frigate Detect Stream Slow

1 messages · Page 1 of 1 (latest)

fringe radish
#

Hello, I'm having an issue with new cameras that wasn't present on my previous set of cams. The live view is working, however on the debug view, it tends to fluctuate from the set 5 fps, to around 1 fps, if it doesn't hang entirely for a few seconds. This is causing a lot of missed detections and no notifications. New cameras are Amcrest. three IP5M-T1277EW-AI and one IP8M-DLB2998EW-AI.

Logs:
https://pastecode.io/s/ptejqzrw

Conf:
https://pastecode.io/s/34u2qit5

The only settings I recall changing for the new cameras are the cam URIs, zones, and detect resolution. Any insight is appreciated. Thanks.

dusty kestrel
#

Hello @fringe radish,
Do the new Cameras have bigger resolution?
What are you using as a server? Storage?
Nor a Frigate user but I know it likes CPU, GPU and good networking / drive speed.

fringe radish
dusty kestrel
#

So what exactly changed?

#

Because if it's only the cameras, it's either the bigger data chunks or the new cameras aren't working with go2rtc or the faster transfer protocals.

fringe radish
#

Only the cameras changed on the hardware side. I agree that it's likely related to the new cameras, so I'm trying to get some config recommendations or camera settings to support the new cameras. I suppose I can try lowering the resolution of the camera on the camera itself for testing.

#

Reducing all four cameras down to 1080p did not appear to have an impact.