I would be surprised if there was that much variation in production of a given model, but who knows. Anyway,
1) There's no reliable way to determine the ND value on cameras with both an ND and iris
1) Create a script like isoinc.lua to test ND value1.1) determine if the "delta ND" propcases accurately reflects ND value.
On 83 of my first G1x I became always 0. On my second G1x I have a value like 65440. But I have different Firmware on my G1x.
I've heard of someone who has changed the lens unit a P&S. But that was not enough. The service had to carry out a calibration. Perhaps the ND filter will be calibrated at this time.May be there are some function of calibration in the firmware?
Quote from: reyalp on 29 / August / 2017, 16:54:071) There's no reliable way to determine the ND value on cameras with both an ND and irisBut when the propcases includes a calibrated ND value, why the script can’t use it?
I thought about it. My idea was:1) Make 10 shoots with ND Filter and 10 without ND Filter with isoinc under constant light condition.2) Calculate average meter values with and without ND Filter to see the differences
One thing we don't know is if this value is present in "hidden" ND cameras like SX260
1) switch ND off (set_nd_filter(1)), half press2) read all propset values, note all values with 03) switch ND on (set_nd_filter(2)), half press4) read all propset values, note all values which changes from 0 to something between 100 and 300.5) repeat step 4 to verify
What we know is that the prop value goes from 0 to something between 100 and 300.Is it helpful to make a script whichCode: [Select]1) switch ND off (set_nd_filter(1)), half press2) read all propset values, note all values with 03) switch ND on (set_nd_filter(2)), half press4) read all propset values, note all values which changes from 0 to something between 100 and 300.5) repeat step 4 to verify
Or just write every prop value in a file to search on a PC….
Just to understand a little bit more about the stuff. What is behind a prop value? Just a specific memory or a register?
You should also check PROPCASE_ND_FILTER_STATE (196 for both propset 4 and 5)
So first, you have to figure out what makes the canon firmware use it. I would guess the Canon firmware uses it in Tv or Av mode where the other limit is reached. So for example, if you set Tv = 1/15 in a with light so bright that even the highest aperture would be over-exposed, the canon firmware probably puts in the ND. Same if you set Av to the widest value with enough light to make the shutter go over the Canon max.
Quote from: reyalp on 31 / August / 2017, 03:04:08You should also check PROPCASE_ND_FILTER_STATE (196 for both propset 4 and 5) Checked on S110 ND off 196:0 ND on 196:1
Correct. Canon Firmware switches ND on and off but 80,87 and 88 always 0. So, no changes in prop values.
I went to the CHDK menu and made 3 dumps and 3 pictures (In M mode) with
You could check to see if there are propcases elsewhere using the prop compare feature or a script to dump the full range.
IIRC people did look when we first realized these "hidden" ND existed and didn't find anything.
How did you control the ND? Using CHDK overrides (from menu or script) would probably not affect propcases normally set by the canon firmware.
I would expect Canon firmware never uses the ND in M mode.
What is the full range? 400? I thought default of the script where full range…
Quote from: reyalp on 31 / August / 2017, 17:34:59I would expect Canon firmware never uses the ND in M mode.How do you explain the three different exposed pictures? I understand off and in but not 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 »
General Discussion and Assistance