ZoneMinder Forums

zma_m3[15417]: WAR [Max blob count reached. Unable to allocate new blob so extending last one.]

i'm not sure what to do about it... but this warning is filling my log file quite fast. 4 gb in a few days.

the monitor giving the error has a resolution of 640x480 and there is only the standard zone. except i changed the the area and filter sizes from 3 to 1.
the camera shows a large area, so 3 wouldn't get all motion within the picture (yes, i'm using modect).

btw it's zm 1.21.4

-acrid

What are your zone settings for your camera ID 3?

Regards,
Corey

• min_x=0
  min_y=0
  max_x=100
  max_y=100
  check_method=blobs
  min_pixel_threshold=25
  max_pixel_threshold=0
  min_alarmed_area=1
  max_alarmed_area=75
  filter_width=1
  filter_height=1
  min_filtered_area=1
  max_filtered_area=75
  min_blob_area=1
  max_blob_area=0
  min_blobs=1
  max_blobs=0

it's a 640x480 monitor. if i change the bold values back to 3 (or 2) i don't catch every person...
maybe i should change the max_blobs to 75 or something?


merry christmas!

-acrid

you are using % settings and as such can set to the lowest setting of 1% image size which would appear isnt sensitive enough for yor need. If you change to pixels you can drop right down to say 100 pixels. You need to leave the filter at 3 not 1 as the blob detection will doing tonnes of work. Anyhow id chenge back to 3 on your filtered width and height, change to pixels and drop min to say 200 to start with. Dont go too low or it will constantly be in alarm.

Btw has anyone ever tried less than 1 in the percent settings ie 0.1 etc

This error occurs when you have setting set to a value so sensitive that too many individual areas of motion are picked up. You could try changing your filter are to 3x3 at least.

In 1.22.0 this area has been completely reworked so this issue will go away.

Phil

hmm,

i have the same problem using 1.21.4 i use default settings...

640*480 @ 5 fps
ip cam axis 206w

Just checked and I'm getting this error also, I have just the default zones on.

mycal

When I decreased the resolution to 320x240 this error went away. (on a system using 3 ports of a 4 port board)

I tried to allocate more shared memory and up back to 640x480 but I still could not avoid this messages.

this is on 1.21.4

mycal

You could try increasing the zone filter size slightly which should reduce the amount of separate patches of changed pixels. Essentially it appears you are getting a large area of speckled motion that doesn't form one contiguous block. Anything you can do to either reduce it, or make it more conjoined should help with this issue.

Versions 1.22.x have changed in this area so this problem should never occur in more recent systems.