Yes, that's the mode dial position. Remember to disable flash, though. I'd use P with auto ISO and custom white balance to better compare the shots (unless you are going to ditch the JPEGs and only use RAWs, in that case WB doesn't matter at all). Note that the script will not give you a constant sampling rate since it just sleeps a constant time after shooting, and the shooting takes a variable time. You'll have to either fix the script to use get_tick_count for the delay (like some "accurate" intervalometer scripts do) or dig the datestamps out of jpeg filenames or exif tags and plot xy.
So am I missing some overriding stuff here, or how is P/AUTO-mode compatible with my goal of shooting a constant-exposure-setting timelapse movie? Shouldn't I be using M?
Constant sampling rate isn't required, but if it's far from constant, it would be nice to have it timestamped in some way. Isn't it possible for example to print get_tick_count or get_day_seconds to the output file instead of the p index?I'm eager to get home from work and start testing all this stuff. Friday might be clouded out in Finland, but luckily intensity measurements can be done anyway.
Then you can set the manual exposure you wish using CHDK overrides. I'm not sure what happens when you use CHDK Tv+Av+Sv override AND CHDK continuous mode Tv bracketing override simultaneously. I hope it brackets from the override. If it doesn't, I'd report it as a bug.
if (p%60=0) then shoot
Vostok, sorry if I didn't reply before but I was out of country for a few days....I haven't read all the thread yet, but just to clarify what bv_log does:this script is meant to mainly to log data, and will only shoot a picture every 10 minutes or so
File names and labels only in finnish, sorry
Started by faulkner
Started by Sapog_topchet
Started by Microfunguy
Started by thedark_master
Started by Multiades