Reyalp : it's not really a sensivity problem and even less a reaction time, it's like it doesn't see my hand or a pen being shaked like 20cm away from the lens (and yesterday where I put the cam for the birds it was the same, I couldn't trigger with my hand where the birds where supposed to land, but closer it triggered it), the simple MD script triggers as anything enters the frame.It I had played with the settings I would understand the difference, but I'm really without ideas atm.

MD doesn't know about distance, but the size of the moving area could be relevant.

The "pixel step" parameter should control how close together pixels are checked. It's possible that bugs could result in less pixels being checked than intended, or some part of the image not being checked.

Hej,Okej thanks I'll try that tomorrow. But this would mean that something new in CHDK has broken the chroma detection on my A540 ?

Potentially, that's why I'm trying to narrow down the cause.

It would also help to know exactly what version of CHDK you were running previously when you say it worked.

Phil.

Hej,Well the simple test seems to show that the Y luminance setting works better than the U chroma with my hand.I really can't tell what version worked last because I hadn't try to detect birds for some time, last time I used MD was a storm last summer and the birds prolly 2013. If it's sunny I'll try my luck on the long-tailed with the Y setting anyway, can't be worse than the U setting atm. :þ

And reyalp, I have already tested the test mode and seems that the numbers show that it's detecting my hand (over 10 when my hand enters the frame). Lowering the pixel step to 3 doesn't trigger better with my hand saying hello to the cam like 20 cm away from the lens (about same distance as the test mode).

I'm new here (just joined today) but I've been using your updated script for a few days now, and it is great!

There is one thing that I've experienced with it that I'm wondering if you (or anyone else) could confirm.

I'm using the script on an A590 and an SX110 and both exhibit the same results.

Under the "Masking" heading, It appears that the "mask columns right" and "mask rows top" variables may be transposed. In order to mask columns right, I have to change the "mask rows top" value and vise versa.

I'm sure I could fix it myself, if I knew what I was doing (but I don't)

Under the "Masking" heading, It appears that the "mask columns right" and "mask rows top" variables may be transposed. In order to mask columns right, I have to change the "mask rows top" value and vise versa.

Good catch - I think you are the first person to report noticing this.

This script is a rewrite of the original MDFB script by Fudgey. While putting it all together and translating to Lua, I did not notice that he corrected for the transposition you noticed in the final call to md_detect_motion(). That works but it's not the best way to do things if you want a script to be maintainable long term.

In any case, I missed what he had done and the script is broken as you described. I'll fix it and post an update.

I have tried the MDFB2013 on my Canon PowerShot G9 and it work great. I tried it on a newly purchased Canon PowerShot SX 500IS camera and it behaves a bit differently. When taking photos, both original and in CHDK mode, the lcd screen get brighter in very short moment when trigger button is pushed down, this seems to affect the motion detection. E.g. at lower threshold the photos are taken repeatedly seemingly triggered by the camera it self. Is there some settings at the camera that could be adjusted?

UPDATE: I realize that the question is more about camera settings than the script. I'll re-post it in a proper place.

Under the "Masking" heading, It appears that the "mask columns right" and "mask rows top" variables may be transposed. In order to mask columns right, I have to change the "mask rows top" value and vise versa.

Good catch - I think you are the first person to report noticing this.

This script is a rewrite of the original MDFB script by Fudgey. While putting it all together and translating to Lua, I did not notice that he corrected for the transposition you noticed in the final call to md_detect_motion(). That works but it's not the best way to do things if you want a script to be maintainable long term.

In any case, I missed what he had done and the script is broken as you described. I'll fix it and post an update.