. . . and any advice for someone wanting to start the trial and error process with an A570IS.

it is camera independent feature. once made it will work on all cameras.

you can use dirty workaround set triggerdelay, timeout, thresholdand check if t<1thats will be no motion during specified timeout

of course there will be dead time periods ( due to trigger delay ) ie if you chose timeout 2 seconds and 1 second trigger delay and something constantrly moves on the scene you will lost 50% of time on preparation

Nope. I could never get it to work and I got fed-up with asking the "developer" for any further information on the issue. Trying to get any clues at all is like pulling teeth. I don't bother to deal with people who think their arcane and obscure hints qualify as any form of "help". I have more important things to do than pumping-sunshine up their @ss just to get them to reveal how to use their routines.

If you want any assistance on any of the uBASIC commands from now on, I suggest you direct your questions directly to the developer who created them. I'm not going to be their translator anymore.

Hi,i installed ur motion detection script on my canon a540 and i must say that its working like a charm. u mentioned in ur post about a script thru which the camera would take a snap as soon as it detects ZERO ACTIVITY. this is a great idea when photographing a big crowd of 10-15 people. i just wanted to know if this script already exists or if u r working on it.if it doesn't then it would be nice if u could kindly come up with this innovative script.

you can use dirty workaround set triggerdelay, timeout, thresholdand check if t<1thats will be no motion during specified timeout

of course there will be dead time periods ( due to trigger delay ) ie if you chose timeout 2 seconds and 1 second trigger delay and something constantrly moves on the scene you will lost 50% of time on preparation

Yesterday I posted a script which does this... it's not the simplest thing to use and not tested well but I does work. Trigger delay isn't really a problem (a value of 0 works for me, I put 100 ms as a default to be safer) because the script doesn't shoot between MD restarts (and shooting is what starts most of those things that require waiting). I didn't include any of those get_prop loops, but if it turns out the script sometimes does go into a MD loop (ie it will never detect stillness) it'll have to be thought over more carefully.