I'm concerned that adding a second half shoot will almost certainly slow things down beyond 1 second.
Do you recall whether it's possible to skip the second half shoot and just do half shoot > set_* > release > shoot/full shoot ?
If not, I will look into doing this using prop cases, but I think this might reduce the number of camera models the script will work with.
Note that currently, only propset4 has TV2, so that would be an additional special case if you want to use it.
Thanks for that info. I added tests for nil values. Do all cameras have a TV value at least?
Quote from: lapser on 29 / August / 2012, 20:45:31Thanks for that info. I added tests for nil values. Do all cameras have a TV value at least?Yes, TV is required for CHDK to work at all. TV2 is an extra.
For cameras that don't have TV2, is it possible to update the EXIF data to display the correct value?Certain timelapse software relies on the EXIF data being correct to calculate smoothing between frames etc.
For cameras that don't have TV2, is it possible to update the EXIF data to display the correct value?
The EXIF data isn't exact enough to use, since it's truncated to the nearest 1/3 ev by the camera. The camera only can change exposure by 1/3 ev, which is visible in a time lapse.
I've modified my own copy of the script to use set_prop 69 T rather than set_tv96_direct T. This works for my camera, but I'll work on implementing this in a model-independent way when I get back.The rally starts tomorrow!
@param p = Log File Name@default p 0p=p+1 -- trying to write a new log file every time the script is runprint_screen(p)print(os.date())
I have another question for the gurus. If you modify a @param in a script, is there a way to make sure the new value is saved?
Started by clevermonkey General Help and Assistance on using CHDK stable releases
Started by DanDMan Script Writing
Started by tileboy1 General Help and Assistance on using CHDK stable releases
Started by Alarik General Discussion and Assistance
Started by apctjb « 1 2 3 » Script Writing