See attached pictures, most spots are there on both shots (F8, full zoom, focus on infinite, "ND" in & out).
Yeah, the fact the spots get sharper with "ND" in makes it pretty clear the aperture is changing.I think it's safe to conclude the "hidden" ND is actually just a funny way to control the aperture, and these cameras do not actually have a ND filter.My feeling is we should undefine CAM_HAS_ND_FILTER on these cams, but I'm willing to hear arguments against.
Yeah, the fact the spots get sharper with "ND" in makes it pretty clear the aperture is changing.
I've noticed a slight magnification change, and slight blurring, in my time lapses before and after an ND filter switch.
As I mentioned in this topic, filters change the focal length, so changes in focus with and without a filter doesn't necessarily mean the aperture changed.
So maybe "aperture" is just a funny way to report the exposure change from a hidden ND filter.
In any event, I hope you don't undefine CAM_HAS_ND_FILTER. In my scripts, I have ND filter switch working on the SX260, D20, SX50, and G1X.
Without ND filter switching, I would would have to figure out all the aperture equivalents, which would be complicated and camera specific. I see no reason to disable a feature that's working.
On the cameras with real ND we notice Quote from: lapser on 16 / September / 2017, 14:06:13 I've noticed a slight magnification change, and slight blurring, in my time lapses before and after an ND filter switch. So, this should happen on cams with hidden ND’s as well when the have a real ND.
If I do a ‘set_nd_filter(x)’ in CHDKPTP on my S110 this has no effect until I do a half press. Is this the way how the ND changes?
on 2> =return call_event_proc('FA.Create')3:return:0con 3> =return call_event_proc('InitializeAdjustmentFunction')4:return:0con 4> =return call_event_proc('PutInNdFilter')5:return:0
3) With the current setup, a script cannot reliably control both aperture and ND, because in some some cameras they interact in an unspecified way, but script has no way to distinguish them from cameras that truly have both.For #3, I suppose we could add a way to identify "cam responds to set_nd_filter by changing the aperture" but this strikes me as a bad way to deal with the fact these cameras were only defined as having an ND due to misunderstanding.
The function works in my scripts regardless of how it creates the exposure change. It's a very useful function to me.
But my Canon D20 still gives a round Sun with the ND Filter IN. I think it has a plate with a round hole that flips in front of the lens to change aperture, but it could have an actual ND filter. Can you try your SX710 depth of field test with your D10?
* Naming: Having "min" mean the opposite of the propcase name is sub-optimal. I suggest we expose them as get_min_av96 and get_max_av96, meaning the minimum and maximum av96 value. This matches the propcase and should be relatively unambiguous.
* What to do on cameras that don't have the eventproc
* What to do on cameras that don't have an iris. I don't have any cameras that are ND only and have the eventproc, so I don't know what the underlying behavior is.
* What to do in playback mode.
local set_nd_filter_orig=set_nd_filterfunction set_nd_filter(state) if get_nd_present() == 0 then if not get_mode() then return end if state == 1 then set_av96_direct(get_max_av96()) elseif state == 2 then set_av96_direct(get_min_av96()) end else set_nd_filter_orig(state) endend
I'm on board with this change now. On the G1X, I should be able to control the aperture AND the ND filter from a script, i.e. for forcing long exposures of waterfalls during the daytime. I'll experiment with aperture control when I get back to scripting. Thanks for figuring this out.
Started by reyalp
Started by fudgey
Started by chocochan
« 1 2 »
Started by Mattttteo
General Help and Assistance on using CHDK stable releases
Started by reyalp
« 1 2 3 »
General Discussion and Assistance