ZoneMinder Forums

In the usual place at http://www.dgmo.org/zoneminderpatches is patch #6. This implements decimation. The motion detection now runs using a 1/4 size image (1/2 the width, 1/2 the height). With this patch, zma is now using less CPU than zmc, and I'm processing 45 fps on a 1.6GHz CPU @ ~ 75% CPU. NOTE ...

PS: It would be helpful is people could mention what most of their false alarms come from? My top sources are cameras changing light levels, overcast changing to/from sunlight, and large moving shadows (in that order). My patch takes care of about 70% of the type events, but can't do 100% without ...

The big item on my list that looks like a fair amount of work, but a lot of value, is to just add training. So you can go over past events and say 'false alarm', and it learns which ones are false alarms. The key problem here is data reduction. It's impractical to try and train a bayesian network ...

Entertainingly, I went through exactly the same thought process when I was searching for the leak.

Next up is to run valgrind over it.

Just posted latest code at http://www.dgmo.org/zoneminderpatches Mostly minor changes to tweak the settings. I'm running all cameras at 10 fps, with transparency set to 10%, and it's performing pretty well. moOd: Which delta image is that? /tmp/blend*.jpeg or /tmp/sq*.jpeg? That looks fine for a ...

Updated patch at http://www.dgmo.org/zoneminder-1.23.3-motion-4.diff This has higher thresholds, and much, much lower CPU usage. (Less than half what was previously using). Just for future reference; calculations are free, accessing memory is expensive. time in ::Blend dropped by 30% switching from ...

Hm. I applied your latest patch and have been running it for about 30 mins now. It's still running in alarm state.. and doesn't seem to be calming down. I'm still running with my old settings from the previous patch that worked fine. Should I adjust any parameters with this new one? Yes, I need to ...

Hmm. I just found one of my zma processes chewing 1.8 gig of ram. So there's definately a memory leak somewhere, but I can't see what triggers it yet. I just re-read through my diffs and I don't _think_ I've added a memory leak but ....

There's an updated patch at http://www.dgmo.org/zoneminder-1.23.3-motion-3.diff The changes are: #1. Use a multiplicative light level model. This basically means that if the image average values change by 5%, then the reference image values are also scaled 5%. (Previously, it use to use an additive ...

I've also discovered that average pixel and blobs are ignored, even after applying the latest patch by mor released on this forum. My settings are working pretty well now. The only thing I'm getting false triggers from is all sudden changes my camera does to compensate lightning. Pretty annoying ...

Are you referring to 'Reference Image Blend %ge' in the monitor config (mine is currently 2), or a value in the source code? Where is 'minimum number of frames to alarm'? Are you referring to 'Alarm Frame Count' in the monitor config? Yes and yes. For 10fps, 2% may be on the low side. If I get time ...

Probably the first value to look at is to increase the Blend percentage. At 10fps you could try 3 or even 4%? Note that it doesn't log values under 2.5. I I also set the 'minimum number of frames to alarm' to 10 to avoid the intermittent spikes. Re locking up: That's a new one on me. My box has ...

Hi. This image was impressive! I presume, some more advanced functions like object removal and placement detections could be developed with this approach? Because you already have the ongoing "state" of the background, and can detect whether something was added or removed? Maybe. :) Not 100% sure ...

The short answer to that is 'no'. The longer answer is: It's not change that's important, so much as constant change. If an area is always different from the blended image, than that difference will be reduced in importance over time until it's ignored. For example, if a pixel is constantly changing ...

Ah-hah! Thanks for this. I'm ashamed to say I hacked around this in zmc by changing it simply to not exit if it got a correct image. I thought it was my cameras producing that junk :) I'll put this patch into my source tree. Ps: You may want to consider using 'diff -u' to generate patches. It makes ...