ZoneMinder Forums

I've now tried the latest patch this evening but are getting some strange results when looking at the delta image. The images looks like this: http://i288.photobucket.com/albums/ll176/ubermood/Delta3.jpg It seems that the resolution is wrong, or something? :roll: I will try some more testing later ...

Maybe a dumb question, but i am a bit of a n00b, but how can i apply this patch againt which file?

You apply the patch by simply running "patch -p1 < PATCHFILE.diff" in the same directory you've got your sourcecode for ZoneMinder v1.23.3.

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. May 26 13:13:13 yin zma_m1[12663]: INF [Average 27.930651, pixels 614 (1.013229, 1.010361, 1.016342)] May 26 13:13:13 yin zma_m1[12663]: INF ...

The light changed should be compensated. Could you post some of the log lines around when the lighting changes? (You should see "(-8, -8, -8)" or similar values gradually decaying to zero. This is essentially the offset in the lighting values. Yes, I can see those values directly after a lightning ...

Ah, thanks! That's true.. I will try setting an upper limit.

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 ...

As I understand it, it learns to ignore areas that are constantly appearing in the image and filter out that "noise". What happens if I temporarily put a chair or any other object in front of the camera, for say.. 5 minutes and then remove it. Will that area still be ignored until I restart ZM, or ...

I've been testing various settings of image blend now. My monitor is currently updating around 1.5-2fps. 1% was way too slow in compensating lightning changes. 10% was pretty OK, but I was still receiving a bunch of false alerts when my cameras built-in light compensator was working. Now I't running ...

Now it seems to work correctly! I took a look at zm_image.cpp and found this: if ( config.fast_image_blends ) . . } else { . . ..and realized that "ZM_FAST_IMAGE_BLENDS" needs to be turned off. I turned it off and the Average counter started ticking down and an image was also created in /tmp. It's ...

Thanks for your kind help with this.. I left it on over the night and it's still recording (~8hrs later). :lol: The numbers does not seem to trend down, as they look like this now: May 16 06:42:20 yin zma_m1[16079]: INF [Average 220.483776, pixels 125961 (10, 10, 10)] May 16 06:42:20 yin zma_m1 ...

In zm_zone.cpp, line 201, there's a line that reads if (pixel_avg > 2.50 && 0) { It should read if (pixel_avg > 2.50) { I'm sorry.. but, I think this correction was already implemented in your previous patch, that I was testing out. I doublechecked and there was no "&& 0". :roll: This is what's ...

I patched ZM 1.23.3 with "zoneminder-1.23.2-local.patch" and also applied the "crash-fix.diff" patch from your homepage. Now everything is succesfully up and running without any crashes. However.. my problem now is that it alarms as soon as I start it up. No matter what settings I apply in the ...

It's actually a patch versus 1.23.3. All the patches are versus 1.23.3 Thanks! :) Now the patching went through without errors. I will try some more when I get home. Need to update the database and all that stuff before reporting.. (quick test showed in the log that ZMA was till crashing ...

ZM worked fine with no errors before patching. I changed all "/* double pts = */" entries in your diff to "double pts =" instead, then I also removed "static struct timezone..." from zm_monitor.h and leaved the "extern struct timezone" line there instead. Did I something wrong? All the "/* double ...

Hi there! This is really interesting stuff! I tried your patch on version 1.23.2, with some slight modifications on your diff-file (some entries seemed to be incorrect).. but I am expericing problems with the "zma". Here is what my /var/log/messages says: May 13 23:48:43 yin zma_m1[7058]: ERR [Got ...