Talk:CHDK/uBASIC/Scripts: OMNI Intervalometer

My experience with the cycle times using this script (OMNI Intervalometer) on a Canon S3:

Note: I got similar results using full 6M resolution and using the 640x480 image resolution. All my results were obtained in P mode, writing onto a 2Gb high speed card. (Indoors; at night; with no flash; aimed at my computer monitor.)

If I used a 0.5 interval time, I got about a bit less than a 2 sec cycle time. Presumably that reflects about 1.4 secs of processing time added to the specified delay of 0.5 sec. HOWEVER, this is with the image "review" time OFF (you find this on the first main menu when in shoot mode; this setting determines how long the shot you just took is displayed on the LCD or viewfinder before back to active shoot mode). If your image review time is not OFF, then that time is also added to cycle time.

Additionally, the very first parameter you enter "Script shoot Delay" (in 0.1 sec) also is added to the cycle time. (I'm not sure what this is for). It works fine at 0, and I don't see any reason to not leave it there (and, frankly, I don't know what prompted me to change it enough for me to see that it had an effect).

So, the approximate cycle time of the OMNI Intervalometer will be the sum of the following:

- 1.4 seconds (approx) of processing time for the image, plus

- the duration of the camera's image review time, plus

- the duration of the "Script shoot Delay" variable, plus

- the duration of the 3 interval variables (min, sec, 0.1 sec)

So about the fastest I could get it to go is ~1.9 sec when specifying a 0.5 sec interval.

BTW, I found a free quick-n-dirty program to assemble a sequence of images into a AVI. It's called JPGVideo (google it).

YMMV. Cheers, Divalent.