I just loaded this script today and I too was able to get it working without modification to the script. I did however find that I couldn’t get shots any faster than about 1 every 3 seconds and I’m not sure why. The built in one (movie mode> timelapse) will take a shot every 1″ but you’re limited to 640×480. I think the camera’s burst mode is 1.3 FPS so theoretically it should be faster than what I’m able to get.

I used a guerilla pod to fix the camera to my rearview mirror and get some interesting time lapses while driving. I want to try this again but with longer shutter speeds so all of the car headlights are streaking. I’m really digging this little point and shoot, so much power packed into a little camera now that CHDK has come out.

It didn’t require any revisions. The weird thing, so far, is that for shooting daylight scenes it only works when in M(anual). For some reason when it’s in A(uto) it stops. Anybody have any idea about this?

Thanks,
John

Thanks for testing that out! I unfortunately don’t have many power tools to test this with except for a rechargeable power drill, but that probably wouldn’t be the most accurate test! Were you able to get the angle of motion blur on the spinning skilsaw?

The auditory trigger definitely sounds like an interesting script.

I’ll play around some more and see what I can figure out. It would be interesting if someone devised a script that fires the camera off of an auditory trigger via the microphone (ie a balloon popping). I’ve seen some trigger circuits that do this but they have to use a pitch black room and rely on the fast flash for the sharp exposure, if CHDK could do it via a script and have a flash synched 1/10000s exposure that could yield some very interesting shots.

I have noticed the same 1/1,500 shutter speed exif data you mentioned. I didn’t think about it much and just added it to my SD1000-CHDK quirkiness mental list. In the chdk wiki, it states the max shutter speed achievable is 1/10,000. I haven’t confirmed the highest achievable shutter speed, but I have confirmed that the shutter speeds do go higher than the stated 1/1500.

This was my quick test (I hope it isn’t too flawed!):
I set the ND filter to “Out” in CHDK. This is actually very important when using manual shutter speeds otherwise you’ll get very random results (4 stops of difference because the camera will drop in the ND filter at random times!) I set the shutter speed to 1/1250 and value factor to 1 in CHDK. Took a picture outside. Then switched it to 1/2500 and took another picture etc. etc. etc… When I compared the pictures, the images got progressively darker. I’m not sure what the highest achievable shutter is, but I think it is at least a little bit higher than 1/10,000. I’ve read in the wiki that physical aperture size affects the highest speeds. I can understand that on leaf type shutter, but I’m not really sure why it would affect a CCD type shutter. The CCD is just turning on and off.

Regarding the motion detection. Part of this is from memory because I tried two different scripts. The first is lightning script: http://chdk.setepontos.com/index.php/topic,459.0.html (looks like it is off the thread now). I think I set the trigger delay to 13 and didn’t get continuous shooting. Then I tried the more customizable one here: http://chdk.setepontos.com/index.php/topic,518.0.html (script is also missing it appears). The trigger delay that worked for me sort of was 40. I think it really depends on the lighting of what you’re shooting. I need to experiment more with this. I just wanted to try it to see if it would even work. I haven’t really used the script though for shooting anything worthwhile.

Here is the script I was using (that now I realize is way too short compared to others I’ve seen)

e=e*100
f=f*1000
while 1
press “shoot_half”
rem for get_prop use 205 for DigicII and 206 for DigicIII
do
get_prop 206 p
until p=1
md_detect_motion a, b, h, f, d, c, 1, t, 0, 1, 1, a, b, i, g, e
if i=0 then click “shoot_full”
rem the next loop is endless if AE lock is activated, use 205 for DigiII
do
get_prop 206 p
until p1
wend
end

As for the motion detection script, what variables did you change in order to get it to work? Once I start the script it just keeps shooting for ever. I noticed on the script’s wiki page it says that if AE lock is on it will get stuck in a loop but I don’t know how to disable AE lock.

Hopefully you can shed some light, I’d appreciate it. If I find anything out I’ll let you know as well.

Thanks,
James