Hello folks! Long time ZM user hoping for some help.
I recently upgraded my server so my Zoneminder VM now has enough muscle to handle 30FPS from the cameras. When I switched the cameras from 15 to 30 FPS, I started getting this error occasionally in the log:
"Max blob count reached. Unable to allocate new blobs so terminating. Zone settings may be too sensitive."
The error doesn't seem to affect capturing events; the events that cause the error are still fully saved. But I'm wondering what could be causing this problem as I've not changed any of the settings for the zone (see attached screenshot.)
How can I get rid of this error? Is it a big deal if I just ignore it? It happens once or twice a day, usually when there's a lot of motion in the frame. Event detection is working exactly as I want it, the error is literally the only problem here.
Thanks for any insight!
"Max blob count reached" errors showing up in the log after increasing framerates
Re: "Max blob count reached" errors showing up in the log after increasing framerates
Not sure why an fps bump would make a difference, perhaps due to blending, etc.
At the end of the day it means that it found too many blobs. The video is too noisy. Increase your min blob size etc and make it less sensitive.
Nothing bad will come from it other than that you may be recording when there is no motion just due to noise between subsequent frames.
At the end of the day it means that it found too many blobs. The video is too noisy. Increase your min blob size etc and make it less sensitive.
Nothing bad will come from it other than that you may be recording when there is no motion just due to noise between subsequent frames.
Re: "Max blob count reached" errors showing up in the log after increasing framerates
Thanks for the reply! I doubled the min blob area. Let's see if that stops the error without affecting sensitivity too much.