MDFB2013 - updating the fastest CHDK motion detection script

philmoz

yvesson
I'm using the U (chroma), other settings I didn't change but threshold.

...

I might also add that the simple motion script (both bas and lua) triggers as well as before.

The simple MD scripts trigger on Y only. Try that and see if it makes any difference.

Phil.

yvesson

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 ?

philmoz

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

reyalp

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

The test mode may help figure out what's going on.

yvesson

philmoz

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

yvesson

Hej,
My cam is catching birds atm and it's actually working with the luminance setting, so I just declare the chroma setting useless. :Ã¾

Click!

Hey waterwingz,

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) 😐:

Thanks again for the great update to a fast script!

waterwingz

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

Kestrel1978

Hi,

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.

Regards,
Kes

Click!

waterwingz

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

Thanks very much waterwingz! 😀

waterwingz

Click!
Thanks very much waterwingz! 😀

Script updated - use the link from the first post in this thread.

Stormrunner25

I'm haveing the same issue as drillthrall did . what did you do turn that off?

waterwingz

Stormrunner25
I'm haveing the same issue as drillthrall did . what did you do turn that off?

I assume you mean this post : https://chdk.setepontos.com/d/10864/15 ?

If so, did you read the response to that post? The next post in the thread? I think you will find your answer there.

Hint : If you are going to make reference to another post, it's helpful if you "quote" that other post so that people who might be able to help know what you are referring to (and don't have to do looking for it).

Stormrunner25

waterwingz

n6mod
I tried the naive implementation, adding [tt]shoot()[/tt] to the inner until() loop in [tt]fast_md()[/tt]. This works, but the total cycle time of that shot is about 4s. If I'm aiming for a 15s timelapse, that means there's only about a 70% chance of catching a motion event. Is there a different strategy that will reduce the cycle time of the shot?

The problem you are having is related using the shoot() command, which causes the camera to focus and set exposure. However, in the inner loop that has already been done by the press("shoot_half") statement so there is no need to do it twice.

Try this :

[code]function fast_md()
splash("Fast Reaction Photo MD")
repeat
press("shoot_half")
repeat sleep(10) until (get_shooting()==true)
motion = detect_motion(e,f,1,9)
if ( motion == 0 ) then
click("shoot_full_only")
else
if (post_shot_delay> 0) then sleep(post_shot_delay) end
release("shoot_full")
end
release("shoot_half")
repeat sleep(10) until (get_shooting()==false)
wait_click(50)
until not( is_key("no_key"))
end
[/code]
Sorry - have not had time to test this myself. If it doesn't work, I'll take a look later this week when I have my development machine and cameras back.

Note : there was also a one second delay related to the need to turn the backlight off after every shot. If we use the new set_lcd_display() command that is no longer needed. We can look at that after we get the loop time down.

How would we go about saving that in file form? Thanks

waterwingz

Stormrunner25
How would we go about saving that in file form? Thanks

Where it says Code : [Select] , just left click on the word Select. Then cut the selected area (using a mouse right click). Open the MDFB2013.lua script, find the fast_md( ) function and pasting the stuff you just copied over it.

On the assumption you are going to struggle a bit with the instructions I just posted, I have attached a copy of the script modified as per my earlier post. I even tested it this time and found that it was not turning off the display, so I fixed that.

Note that you need to set Reaction Mode [ Fast ] and if you want the display to stay off completely, select Display Power Saving [ LCD ] ( and be sure the Canon shot review mode is set to OFF ).

MDItervl.lua

9.84KB

Stormrunner25

waterwingz

Where it says Code : [Select] , just left click on the word Select. Then cut the selected area (using a mouse right click). Open the MDFB2013.lua script, find the fast_md( ) function and pasting the stuff you just copied over it.

On the assumption you are going to struggle a bit with the instructions I just posted, I have attached a copy of the script modified as per my earlier post. I even tested it this time and found that it was not turning off the display, so I fixed that.

Note that you need to set Reaction Mode [ Fast ] and if you want the display to stay off completely, select Display Power Saving [ LCD ] ( and be sure the Canon shot review mode is set to OFF ).

Thanks.

Stormrunner25

Stormrunner25

waterwingz

Where it says Code : [Select] , just left click on the word Select. Then cut the selected area (using a mouse right click). Open the MDFB2013.lua script, find the fast_md( ) function and pasting the stuff you just copied over it.

On the assumption you are going to struggle a bit with the instructions I just posted, I have attached a copy of the script modified as per my earlier post. I even tested it this time and found that it was not turning off the display, so I fixed that.

Note that you need to set Reaction Mode [ Fast ] and if you want the display to stay off completely, select Display Power Saving [ LCD ] ( and be sure the Canon shot review mode is set to OFF ).

Thanks.

Guess I'm just stupied but no matter what I do I can't get it to work. I've even tried flashing a flashlight in front of it and nothing is working

Stormrunner25

Stormrunner25

Stormrunner25

waterwingz

Where it says Code : [Select] , just left click on the word Select. Then cut the selected area (using a mouse right click). Open the MDFB2013.lua script, find the fast_md( ) function and pasting the stuff you just copied over it.

On the assumption you are going to struggle a bit with the instructions I just posted, I have attached a copy of the script modified as per my earlier post. I even tested it this time and found that it was not turning off the display, so I fixed that.

Note that you need to set Reaction Mode [ Fast ] and if you want the display to stay off completely, select Display Power Saving [ LCD ] ( and be sure the Canon shot review mode is set to OFF ).

Thanks.

Guess I'm just stupied but no matter what I do I can't get it to work. I've even tried flashing a flashlight in front of it and nothing is working

Ok this is what I keep getting when I try and use that script.

e preload drawings oono file A\CHDK\SCRIPTS\dra wing.lua'oono file A\CH\DK\LUALIB/ drawings.luna'
**Terminated**

Stormrunner25

ok so I got it to work now so no worries.

waterwingz

[unknown]
I know this this issue is kinda old but I had the same transpose issue with my A590. At first I thought I forgot how to use the mask function even though I have been using it for five or more years. Then I edited the script and fixed it. I never tried to advise Walter because I was afraid I was doing something wrong. I need a dose of self-confidence or something.

I thought I fixed this 8 months ago. When you run the script, if you have the fixed version, the script title will say "v1.1a" rather than "v1.1"

« Previous Page Next Page »