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

Improving CHDK ND filter support

  • 230 Replies
  • 56100 Views
*

Offline reyalp

  • ******
  • 12731
Re: Improving CHDK ND filter support
« Reply #220 on: 26 / July / 2020, 22:03:27 »
Advertisements
Trying to stop procrastinating and finish this  :-[

Essentially all cameras with an ND have been tested. The remaining things I wanted to address are below. Any feedback is welcome.

Should ND-only cameras have CAM_ND_SET_AV_VALUE by default:
This define sets the AV propcases when ND overrides are used, to match the values the Canon firmware would use for the ND state.
It's required on some newer cameras (like elph180, elph185, sx620) for ND overrides to work at all. On older cameras, it's usually required when shooting using the "quick" (hold half shoot, click full) method. Some also require it in cont mode.

I'm inclined to set it by default, because it generally makes the override more predictable quick and cont, and makes the exif more consistent with the Canon firmware.

However, it has only been tested in the cases that appear to need it: That is, if ND override failed in quick, the script re-does the quick test with the equivalent of CAM_ND_SET_AV_VALUE, but not the single and cont tests.


Cameras that need ND state set in the remote hook:
Most iris + ND cameras need the ND state set in the remote hook in quick mode. This is also true on a few ND only cams. Some of both types also need it in cont.

Since we can now get the current actual ND state, we could have logic like
if nd_state != requested_nd_state
 set_nd_filter(nd_state)

This could either be done with defines on the cameras identified in testing, or just done all the time since it shouldn't affect cameras that don't need it.

One complication with this is that the "put_off" values are cleared when an override is applied, so we don't currently know the requested state by the time it gets to the remote hook.

I'm a bit more hesitant to add this.  In all the the cameras tested, setting the ND from the remote hook seems to work fine, but it's a low level thing that varies between ports. Additionally, the remote hook is not hit in some cases: Some ports don't have it, others probably miss it in some shooting modes.


Restoring ND prop on ND+iris cameras:
In the existing code, ND + iris cams mostly set the ND propcase to match the override. However, they don't restore it after the shot completes or if set_nd_filter(0) is used. As far as I can tell, this only exif makernote for ND, so it's probably not a big deal.

I worried that CAM_ND_SET_AV_VALUE might have a similar issue, but the camera updates the AV props on the next halfpress so it generally shouldn't. There might be exceptions on the few cameras that are ND-only but allow it to be set manually.
Don't forget what the H stands for.

*

Offline koshy

  • *****
  • 1051
Re: Improving CHDK ND filter support
« Reply #221 on: 22 / August / 2020, 15:20:58 »
However, it has only been tested in the cases that appear to need it: That is, if ND override failed in quick, the script re-does the quick test with the equivalent of CAM_ND_SET_AV_VALUE, but not the single and cont tests.
Maybe go by age, DryOS version or whatever to define a list of examplary cams to test an we could do that.
Koshy had a little ELPH which wasn't white as snow but everywhere that Koshy went the ELPH was sure to go. (actually an SD, but that detail ruins the rhyme...)

*

Offline reyalp

  • ******
  • 12731
Re: Improving CHDK ND filter support
« Reply #222 on: 29 / August / 2020, 21:27:57 »
I made CAM_ND_SET_AV_VALUE default to on in r5559, and updated the test script to record if it appears to be in use.

Maybe go by age, DryOS version or whatever to define a list of examplary cams to test an we could do that.
@koshy
Thanks. That's a good idea. List below is most of the unique OS versions, except for a couple with known, unrelated problems and ones I already have. Test procedure is as before, using r5559 or later:

* Aim the camera at a stable, low contrast scene, like a blank wall
* In Canon settings, shooting mode should be P, continuous mode should be enabled, flash and review should be off
* Run the CHDK/SCRIPTS/TEST/NDTEST.LUA script with default settings
* Post the log here.

a430 (early vx)
ixus960_sd950 (dry 23)
ixus85_sd770 (dry 23, different behavior)
ixus980_sd990 (dry 31)
ixus120_sd940 (dry 39)
(dry 43, 45 skipped because because they have other unresolved problems)
a3300 (dry 47)
ixus230_elph310hs (dry 49)
a1300 (dry 50)
ixus150_elph140 (dry 54p3)
ixus170_elph170 (dry 55p6)
ixus185_elph185 (dry 59p3)
« Last Edit: 20 / September / 2020, 23:12:20 by reyalp »
Don't forget what the H stands for.

*

Offline whim

  • ******
  • 2024
  • A495/590/620/630 ixus70/115/220/230/300/870 S95
Re: Improving CHDK ND filter support
« Reply #223 on: 30 / August / 2020, 04:45:34 »
@reyalp
@koshy

Thanks to reyalp's clear instructions I was able to contribute results for ixus230_elph310 (100b)
Hope it's useful,
whim



*

Offline reyalp

  • ******
  • 12731
Re: Improving CHDK ND filter support
« Reply #224 on: 30 / August / 2020, 15:15:13 »
Thanks to reyalp's clear instructions I was able to contribute results for ixus230_elph310 (100b)
Hope it's useful,
Thanks. Looks fine, one less for koshy to test :)
Don't forget what the H stands for.

*

Offline srsa_4c

  • ******
  • 4285
Re: Improving CHDK ND filter support
« Reply #225 on: 30 / August / 2020, 18:20:21 »
* Run the CHDK/SCRIPTS/TEST/NDTEST.LUA script with default settings
* Post the log here.
Results from ixus150 and a410 (in case it's of any use) attached. I used a410, because that one still has working "ND" and shutter, unlike my a430.

*

Offline Caefix

  • ****
  • 280
  • Sorry, busy deleting test shots...
Re: Improving CHDK ND filter support
« Reply #226 on: 31 / August / 2020, 10:59:12 »
Ix170: "ALL PASSED."   :)  ...
« Last Edit: 01 / September / 2020, 12:33:47 by Caefix »
All lifetime is a loan from eternity.

*

Offline reyalp

  • ******
  • 12731
Re: Improving CHDK ND filter support
« Reply #227 on: 31 / August / 2020, 21:17:11 »
Thanks for the test results, all look fine.

Don't forget what the H stands for.


*

Offline Caefix

  • ****
  • 280
  • Sorry, busy deleting test shots...
Re: Improving CHDK ND filter support
« Reply #228 on: 01 / September / 2020, 12:32:05 »
 :D A3300, Ix185 & 980 all passed.
All lifetime is a loan from eternity.

*

Offline Caefix

  • ****
  • 280
  • Sorry, busy deleting test shots...
Re: Improving CHDK ND filter support
« Reply #229 on: 08 / September / 2020, 13:33:33 »
IX960_SD950 ndtest: all passed, //  :-X but mftest...
« Last Edit: 08 / September / 2020, 13:40:22 by Caefix »
All lifetime is a loan from eternity.

 

Related Topics