Improving CHDK ND filter support

  • 108 Replies
  • 32434 Views
Re: Improving CHDK ND filter support
« Reply #10 on: 01 / September / 2017, 09:22:06 »
Advertisements
Here's the test ND test script I wrote, along with some results.
Thanks…..
My results from ND test
S110 283-284 => propcase 287
G1x  276-277 => propcase 284
SX50 323-328
Sx230 330-342

I made dumps for SX50 and SX230 with your method:
SX230
Prop 18 could be filters state
Prop 103 could be filter value (325)
SX50
Prop 297 could be filters state
On both elph130 and d10, I noticed that the zoom level seems to change very slightly with/without ND.
Really the zoom? May be Canon made just a different crop to reduce vignettation in the corner with ND filter…


*

Offline reyalp

  • ******
  • 11583
Re: Improving CHDK ND filter support
« Reply #11 on: 01 / September / 2017, 12:59:09 »
I made dumps for SX50 and SX230 with your method:
SX230
Prop 18 could be filters state
Prop 103 could be filter value (325)
SX50
Prop 297 could be filters state
Thanks for testing. Unfortunately, these don't work.

Propset 4 and 5 appear to be identical through 357, if ND propcases were below that, they would likely be identical.

18 is "focus state" (whether AF succeeded), 103 is over exposure. 297 doesn't seem to be a known value.

It really looks like the ND information isn't in a propcase for these cameras :(
Quote
Really the zoom? May be Canon made just a different crop to reduce vignettation in the corner with ND filter…
I haven't looked at raws yet, but the is jpeg very slightly wider angle when the ND is in. This wouldn't be noticeable at all in normal shooting, but might be visible in a timelapse.

To be clear, I don't think Canon is intentionally changing the zoom position, I only meant the FOV of the image changes.
« Last Edit: 01 / September / 2017, 17:09:39 by reyalp »
Don't forget what the H stands for.

Re: Improving CHDK ND filter support
« Reply #12 on: 01 / September / 2017, 14:50:53 »
Another test with SX50. Dump until 1000. No differences over prop 273. Prop 297 didn’t change again. :(
Test was made in TV mode. I can really here the noise, when ND goes in and out…
It really looks like the ND information isn't in a propcase for these cameras :(
Yes… :(

*

Offline reyalp

  • ******
  • 11583
Re: Improving CHDK ND filter support
« Reply #13 on: 01 / September / 2017, 17:09:23 »
Another test with SX50. Dump until 1000. No differences over prop 273. Prop 297 didn’t change again. :(
Test was made in TV mode. I can really here the noise, when ND goes in and out…
There must be variables that reflect this state. If you can get a CameraLog (see http://chdk.wikia.com/wiki/Debugging#Logging_camera_console_output) from half presses when the ND is activated and not, that could provide some clues.

It's possible that finding ND related variables would help us come up with something that works across all the different permutations.

I can probably provide a script to do this later if it's not clear. You can also use the chdkptp devutil dlog* commands.
Don't forget what the H stands for.


Re: Improving CHDK ND filter support
« Reply #14 on: 01 / September / 2017, 18:00:00 »
I can probably provide a script to do this later if it's not clear.
May be that’s the easiest way…
You can also use the chdkptp devutil dlog* commands.
I have chdkptp installed and I can connect the SX50.
The only think what I made in chdkptp before was ‘shoot’ in ‘Live’ .
‘devutil dlog*’ didn’t say me anything…

*

Offline reyalp

  • ******
  • 11583
Re: Improving CHDK ND filter support
« Reply #15 on: 01 / September / 2017, 22:48:54 »
I have chdkptp installed and I can connect the SX50.
The only think what I made in chdkptp before was ‘shoot’ in ‘Live’ .
‘devutil dlog*’ didn’t say me anything…
Make sure "native function calls" are enabled in the misc menu on the camera

devutil is module with some extra development related commands you can use in chdkptp. You can load it with
Code: [Select]
!require'extras/devutil'.init_cli()
After that, help will show you the new commands.

To get camera log, try the following
Code: [Select]
rec
dlstart
... press shoot half in a scene that doesn't trigger the ND in canon firmware, release ...
dlgetcam no-nd.log
... press shoot half in a scene that does trigger the ND in canon firmware, release ...
dlgetcam nd.log

You can also use devutil to test propcases:
dpget gets the values props 0-1000
dpcmp gets the values again, and compares them with values that dpget got.
Don't forget what the H stands for.

Re: Improving CHDK ND filter support
« Reply #16 on: 02 / September / 2017, 01:30:02 »
To get camera log, try the following
Got the log files. Hope that helps. I triggered ND with a lamp. If there is no information in the log I can do it again when the sun comes out.
Result from console:
Code: [Select]
> rec
ERROR: already in rec
> dlstart
log started: A/dbg.log
> dlgetcam no-nd.log
A/dbg.log->no-nd.log
> dlgetcam nd.log
A/dbg.log->nd.log
To be sure, if the noise which I hear comes from ND, can I set the cam to MF?

*

Offline reyalp

  • ******
  • 11583
Re: Improving CHDK ND filter support
« Reply #17 on: 02 / September / 2017, 01:46:02 »
To be sure, if the noise which I hear comes from ND, can I set the cam to MF?
I don't think MF would cause a problem.

You might be able to tell from the shutter and aperture value shown on the camera too (the shutter speed gets longer after you hear the click, even though you are pointing at a brighter scene)

Looking at your logs, I don't see anything obvious. This doesn't mean the logs are bad, it's quite possible the Canon firmware doesn't output anything special for this case.
Don't forget what the H stands for.


Re: Improving CHDK ND filter support
« Reply #18 on: 02 / September / 2017, 02:35:29 »
Another try wit SX50
TV Mode. TV=1/15s. ISO100. MF
In the shadow => Aperture goes to f3.5 (red) the might be dark
In the sun => Aperture goes to f8.0 (red) overexposed and I heard switching of ND
I’m wondering why the size of no-nd2.log is less than half size of no-nd.log…


Update:
I deleted my previous post. Camera settings where the same as my first run expect MF.
« Last Edit: 02 / September / 2017, 04:44:29 by c_joerg »

*

Offline reyalp

  • ******
  • 11583
Re: Improving CHDK ND filter support
« Reply #19 on: 02 / September / 2017, 14:59:49 »
Another try wit SX50
TV Mode. TV=1/15s. ISO100. MF
In the shadow => Aperture goes to f3.5 (red) the might be dark
In the sun => Aperture goes to f8.0 (red) overexposed and I heard switching of ND
If it's using ND, it seems like there should be a light level (or Tv value) where the ND goes in and the Av drops below 8, like
Av = 8, no ND
move to 1 stop brighter light
Av = 4 (- 2 stops), ND in (+3-ish stops)

If it works this way, you should be able to find this point just by adjusting the Tv value, starting with one that gives you Av < 8.

This assumes the camera shows the actual Av of course.
Quote
I’m wondering why the size of no-nd2.log is less than half size of no-nd.log…
The camera puts stuff in the log pretty often so just differences in timing or how long you held half press could make a big difference.
Don't forget what the H stands for.

 

Related Topics