I'm having trouble with this script. I don't seem to understand it at all. I have the reaction mode set to fast, I've tried threshold from 10-100 and it still doesnt pick up the lightning in an evening light. When I wave my hand in front of the camera then it goes off.

What camera?

Quote

Also, I don't get how the picture comparing thingy works.

Not clear what you are referring to.

Quote

The display goes black randomly I think, not after 7ms like I have set it.

If you are using one of the power saving modes, you should probably try to get it working first without.

I'm having trouble with this script. I don't seem to understand it at all. I have the reaction mode set to fast, I've tried threshold from 10-100 and it still doesnt pick up the lightning in an evening light. When I wave my hand in front of the camera then it goes off.

What camera?

Quote

Also, I don't get how the picture comparing thingy works.

Not clear what you are referring to.

Quote

The display goes black randomly I think, not after 7ms like I have set it.

If you are using one of the power saving modes, you should probably try to get it working first without.

Camera is SX150IS. This is what I mean by the pic compare: "Motion detect takes one sample from the display, then waits a time specifiedby the "compare interval" parameter before taking another sample and thencompares these two." Got this from the read me file of the script.Yeah, I was using power saving mode, should turn that off and try again, although it never takes a picture when theres actual lightning, only takes a pic when I wipe my hand in front of the lens.

However, for this to work, we need to know which set_led value turns on the AF LED. I've guessed that it's 0, but that might be wrong. If MD_tune does not turn on the AF LED, try calling set_led with 1 and 2 and let us know which one turns on the AF.

Hej,I'm sorry to say this but : this script doesn't work as well as the old one for me, and I don't know why.I'm using the same settings as my old birds pics and it doesn't catch any bird. Even with my hand it works if I'm 10cm from the lens but further away I can shake it in front of the cam and it won't shoot. Lowering the threshold didn't help until entering a loop. I'm using the U (chroma), other settings I didn't change but threshold.

Anyone helps me test anything, I have missed the long-tailed tits

It's with my good old A540 btw, I fear the new stuff isn't good for my old cam.

And btw the old fudgey basic script does the same thing. Anything has changed in CHDK relative to MD ?

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

I'm sorry to say this but : this script doesn't work as well as the old one for me, and I don't know why....And btw the old fudgey basic script does the same thing. Anything has changed in CHDK relative to MD ?

So are you saying that neither the old script or the new script work today? But the old script worked for you in the past ? If so, that suggests it's something with your camera or CHDK itself that has changed.

Quote

Even with my hand it works if I'm 10cm from the lens but further away I can shake it in front of the cam and it won't shoot.

Hej,Of course the old script worked in the past and obviously something has changed in CHDK. Reyalp where are you ? :pAlso of course I'm in macro mode, but it used to shoot blurry cars or birds meters away in the past, too.

Of course the old script worked in the past and obviously something has changed in CHDK. Reyalp where are you ? :pAlso of course I'm in macro mode, but it used to shoot blurry cars or birds meters away in the past, too.

Sorry if you find this process of questions & answers annoying. Over the last few years, I've learned that you have to establish a baseline condition to work from when helping people with problems. And I think I've helped at least a couple of people. But as you don't seem to appreciate my help, I'll withdraw from this conversation.

Hej,Of course the old script worked in the past and obviously something has changed in CHDK. Reyalp where are you ? :pAlso of course I'm in macro mode, but it used to shoot blurry cars or birds meters away in the past, too.

I'm not aware of anything that would significantly affect the reaction time or sensitivity of MD. Using MDTune, a540 reaction time seems to be very good.

Of course the old script worked in the past and obviously something has changed in CHDK. Reyalp where are you ? :pAlso of course I'm in macro mode, but it used to shoot blurry cars or birds meters away in the past, too.

Sorry if you find this process of questions & answers annoying. Over the last few years, I've learned that you have to establish a baseline condition to work from when helping people with problems. And I think I've helped at least a couple of people. But as you don't seem to appreciate my help, I'll withdraw from this conversation.

Hej,Nah it doesn't annoy me, just I named reyalp because I know he owned a A540 and he prolly tracked any change better than anyone. Don't feel bad about it. And you didn't know my old pictures because the scripts used to work very well and I'm so sad I missed the long-tailed tits yesterday. :/And I'm sure the macro mode isn't an issue because I think it can focus even at 50cm (and btw without the macro mode the behaviour is identical).

But since the simple motion detect scripts seem to trigger from a distance and both fudgey and this updated sript can't, there must be something to find, and of course you can help me.

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.