Improving CHDK ND filter support - page 18 - General Discussion and Assistance - CHDK Forum supplierdeeply

Improving CHDK ND filter support

  • 216 Replies
  • 42154 Views
*

Offline reyalp

  • ******
  • 12106
Re: Improving CHDK ND filter support
« Reply #170 on: 17 / August / 2019, 21:06:00 »
Advertisements
I can run the test on my G10, G16, and SD4000.    Once I figure out what to do - should I be using a recent unstable build?
Yes, use current trunk, script is CHDK/SCRIPTS/TEST/ndtest.lua

Test procedure is
Set camera to P mode, flash off, manual ISO, continuous shooting on
For cams with ND control in canon firmware, set ND off in canon UI
Aim camera at a low contrast, unchanging scene such as a blank wall.
run and upload the resulting ndtest.csv

SD4000 is already covered, no need to re-run that one.
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 912
Re: Improving CHDK ND filter support
« Reply #171 on: 17 / August / 2019, 21:08:45 »
a2200
a2300
a2600
a3100 - Dry r43 TV and AV prop overrides in quick appear to fail, ND control seems to work
First three I'll test sometime next week.
a3000 is missing here, also Dry r43 but we didn't test it yet.

*

Offline reyalp

  • ******
  • 12106
Re: Improving CHDK ND filter support
« Reply #172 on: 17 / August / 2019, 21:21:14 »
This script gave this result on G7, is it what you wanted?
I want to know which propcase changes when ND is changed in the Canon UI.

So, you could do two propdumps, one with it in and one with it out. The less other stuff that changes in between will make it easier to find, so you just do one dump, change the setting, do the next. You should not half shoot in between, since that will update a bunch of other props.

a2200
a2300
a2600
a3100 - Dry r43 TV and AV prop overrides in quick appear to fail, ND control seems to work
First three I'll test sometime next week.
a3000 is missing here, also Dry r43 but we didn't test it yet.
Hmm, I have a3000 recorded as tested, but perhaps it was a mistake.

Results for the others are good if you can test them, but definitely not urgent. We have really good coverage by normal CHDK standards :)
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 912
Re: Improving CHDK ND filter support
« Reply #173 on: 17 / August / 2019, 21:24:17 »
@koshy: A530 failed because the usb remote hook wasn't enabled. This isn't one of the super old cameras that doesn't support, the code looks just like A540, so I posted a test build in https://chdk.setepontos.com/index.php?topic=5305.msg141080#msg141080

If you can check the remote functionality as well as re-running the ndtest script, that would be helpful.
If I recall this right, CHDK Settings menu, Enable Remote, OnePush, Quick should shoot if plugging in a USB cable and pulling it out. Nothing happens though when I do that.

Edit: Do bet on stupidity...
To simulate USB trigger, it is possible to use a USB cable connected to the PC.
Put camera in REC Mode, and exit CHDK ALT mode. Plug USB cable in camera port (camera goes to half press mode), unplug USB (camera goes to full press mode, and takes a photograph).
That makes sense... Using a USB cable hooked to nothing is, well, cute.
« Last Edit: 17 / August / 2019, 21:38:06 by koshy »


*

Offline philmoz

  • *****
  • 3123
    • Photos
Re: Improving CHDK ND filter support
« Reply #174 on: 17 / August / 2019, 21:27:56 »
G12, G1X and G5X results attached.


All three give me a 'port needs ND in shoot hook for quick' warning.


Any tips on what needs to be implemented to fix this?


Phil.

CHDK ports:
  sx30is (1.00c, 1.00h, 1.00l, 1.00n & 1.00p)
  g12 (1.00c, 1.00e, 1.00f & 1.00g)
  sx130is (1.01d & 1.01f)
  ixus310hs (1.00a & 1.01a)
  sx40hs (1.00d, 1.00g & 1.00i)
  g1x (1.00e, 1.00f & 1.00g)
  g5x (1.00c, 1.01a, 1.01b)

*

Offline koshy

  • *****
  • 912
Re: Improving CHDK ND filter support
« Reply #175 on: 17 / August / 2019, 21:32:02 »
I want to know which propcase changes when ND is changed in the Canon UI.
Thanks for the clarification, script is quite neat so here we go:
diffs_were="[100] 03E4 -> 03EA"

*

Offline reyalp

  • ******
  • 12106
Re: Improving CHDK ND filter support
« Reply #176 on: 17 / August / 2019, 21:41:08 »
All three give me a 'port needs ND in shoot hook for quick' warning.

Any tips on what needs to be implemented to fix this?
This seems to be normal for ND+iris. There isn't currently a fix. There are also some ND only cameras that need it.

I haven't decided how to deal with it, we could either leave it up to scripts, or try to do it automatically in the remote hook, or I guess do more reverse engineering.

From the tests so far, manipulating the ND in the remote hook seems to work fine, but  maybe a bit sketchy.

I'm also still thinking about how to deal with the ND-only cameras that need the aperture propcase set. My inclination is to set CAM_ND_SET_AV_VALUE by default (allowing ports to undef if needed), but I'm not sure if there should be a way to override it at runtime.
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 912
Re: Improving CHDK ND filter support
« Reply #177 on: 17 / August / 2019, 21:43:10 »
A530: If you can check the remote functionality as well as re-running the ndtest script, that would be helpful.
So, that works. Some voltage on the cable does wonders  ;)
The ND test fails as posted.
« Last Edit: 17 / August / 2019, 21:47:36 by koshy »


Re: Improving CHDK ND filter support
« Reply #178 on: 17 / August / 2019, 21:46:17 »
G16 1.01c
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline reyalp

  • ******
  • 12106
Re: Improving CHDK ND filter support
« Reply #179 on: 17 / August / 2019, 21:46:23 »
Thanks for the clarification, script is quite neat so here we go:
diffs_were="[100] 03E4 -> 03EA"
Hmm, I would have expected it to be a 0 = ND out, 1 = ND in. Perhaps propset one doesn't have a prop for ND. https://chdk.fandom.com/wiki/PropertyCase lists 100 as custom WB.

Don't forget what the H stands for.

 

Related Topics