How do you tell if the exif values are correct or not? I was just shooting straight down onto grass (the same area and conditions as yesterday) and it's a reasonably sunny day today. The overexposed images that were produced make me think that it did actually use a slower shutter speed, but I'm not much of an expert with chdk cameras.
These overexposed shots all have motion blur too, so I still think the shutter speed is low.
Quote from: Wreck on 07 / December / 2013, 20:25:12These overexposed shots all have motion blur too, so I still think the shutter speed is low.If that's true, then it would mean the CHDK port for the SD960 is seriously broken. Nothing much I can do about that with a script.
Bug reports are welcome (preferably with a description on how to reproduce).
I have applied the 'short shutter press' override fix in changesets 3264, 3265, but I'm not sure if that will have any influence on this script.
-- set up all exposure overrides set_tv96_direct(tv96setpoint) set_sv96(sv96setpoint) if( av96setpoint ~= nil) then set_av96_direct(av96setpoint) end nd_string="none" if(Av_mode > 1) then -- ND filter available ? if ( insert_ND_filter == true ) then set_nd_filter(1) -- activate the ND filter nd_string="NDin" else set_nd_filter(2) -- make sure the ND filter does not activate nd_string="NDout" end end -- and finally shoot the image press("shoot_full_only") sleep(100) release("shoot_full") repeat sleep(50) until get_shooting() == false
The script does not correctly handle the situation where the camera wants to insert the ND filter and reports using a smaller f-stop setting as a result. It assumes the reported Av value is the actual aperture f-stop setting and does its exposure calculations based on that. When the actual shot occurs, it ends up using calculations based on the ND filter being inserted even though it does not insert that filter.
The fix for cameras without an adjustable aperture is to use get_prop(props.MIN_AV) to determine the actual Av96 value of the aperture rather than the get_av96() function.
Reading your commit comments, it appear this only happens on the first shot?
The camera may engage the ND filter in bright light, but take the picture without it (not CHDK related).is about the issue here, that's a script logic problem and not related to the patch
Quote from: srsa_4c on 08 / December / 2013, 09:02:26I have applied the 'short shutter press' override fix in changesets 3264, 3265, but I'm not sure if that will have any influence on this script.Looking at the code in core/shooting.c, it does not look like the change to the aperture_sizes_table in this patch going to change the value returned by get_av96() if the ND filter is inserted ?
Started by Jim
Completed and Working Scripts
Started by nadavofi
« 1 2 »
Started by Benny_H88
« 1 2 3 »
Started by davefolts
Creative Uses of CHDK
Started by GlobalSurvey
General Help and Assistance on using CHDK stable releases