Are the timestamp digits really recognized as motion?

zappen · Post by **zappen** » Wed Jun 24, 2009 6:41 pm

i was looking at the analysis images to finetune motion detection, and noticed that the digits of the timestamp are being recognized as movements

here is a screenshot:

In the last image i see the previous digits overlayed with the new ones, as when showing a motion
Is this normal? because i think it's triggering the alarms, expecially when both the last 2 digits or more changed. i tried to disable the option TIMESTAMP_ON_CAPTURE but it seems worst, all the timestamp background is recognized as a movement in the analysis images.
Should i put a inactive zone on the timestamp or disable totally timestamping to prevent this? or is a bug?

mitch · Post by **mitch** » Wed Jun 24, 2009 7:18 pm

Technically the best thing to do would be to limit your active zone to exactly what you care about monitoring rather than the entire window. It will nicely have the side effect of reducing the load on ZM too.

Normando · Post by **Normando** » Thu Jun 25, 2009 5:34 am

You are right zappen, this is a bug, also for 1.23.3

A question: How you get the live debug images?

zappen · Post by **zappen** » Thu Jun 25, 2009 3:38 pm

in options/debug , there is ZM_RECORD_DIAG_IMAGES, also ZM_RECORD_EVENT STATS is usefull