Improving CHDK ND filter support

srsa_4c

4451

Re: Improving CHDK ND filter support

« Reply #120 on: 05 / February / 2019, 13:54:18 »

Advertisements

I have done the test with almost all my working ND-only cams:
a410, a490, a3200, a3400, ixus65, ixus870, ixus110, ixus115, ixus150
It turned out that the a490 has a circular aperture instead of an ND filter (similar to a410, 420, 430). At wide angle, I get F3.0 on screen with "ND" out and F4.5 with "ND" in.

ndtests.zip (14.16 kB - downloaded 9 times.)

Logged

reyalp

14111

Re: Improving CHDK ND filter support

« Reply #121 on: 05 / February / 2019, 17:04:03 »

Quote from: srsa_4c on 05 / February / 2019, 13:54:18

I have done the test with almost all my working ND-only cams:
a410, a490, a3200, a3400, ixus65, ixus870, ixus110, ixus115, ixus150
It turned out that the a490 has a circular aperture instead of an ND filter (similar to a410, 420, 430). At wide angle, I get F3.0 on screen with "ND" out and F4.5 with "ND" in.

Thanks. That's a big help.

I noticed a number of them have a big variation in the first shot, like waterwingz saw s100. I'm guessing this is a problem with the script or a quirk of CHDK overrides.

Also interesting that the "ND" values can be quite low. I set an arbitrary limit to warn if the ND was less than 2 stops because the ones I knew of were ~3, but the circular aperture cams are ~1.5, and ixus60 and ixus870 are under 2.

for ixus115, the it looks like the ND didn't get put in for "quick", but for some reason the script didn't retry.

Logged

Don't forget what the H stands for.

srsa_4c

4451

Re: Improving CHDK ND filter support

« Reply #122 on: 06 / February / 2019, 13:02:41 »

Quote from: reyalp on 05 / February / 2019, 17:04:03

for ixus115, the it looks like the ND didn't get put in for "quick", but for some reason the script didn't retry.

I can't tell why, but this is happening consistently.

Logged

reyalp

14111

Re: Improving CHDK ND filter support

« Reply #123 on: 10 / February / 2019, 02:03:50 »

Quote from: srsa_4c on 06 / February / 2019, 13:02:41

Quote from: reyalp on 05 / February / 2019, 17:04:03
for ixus115, the it looks like the ND didn't get put in for "quick", but for some reason the script didn't retry.
I can't tell why, but this is happening consistently.

Spent some more time on this. What I think is happening is the ND is being reset after the shoot / remote hook, so the check that would trigger the retry passes, but the ND isn't in for the actual shot.

I think the hook placement on the ixus115 port is suspect, wait_until_remote_button_is_released is right in the main capt_seq function

The version of ndtest in r5159 will also trigger the retry from the raw hook.

The A490 results are also weird in a couple ways:
* The recorded shutter speed for the first shot in quick is different from the set shutter speed, as if the initial override didn't work.

* It retries in quick mode, but setting the AV prop does not appear to put the ND in. It falls back to putting in the ND in the shoot hook (as ND+iris cams seem to need) which appears to work, but...

* The shutter override to compensate for ND appears to fail, both by the logged propcases and meter value.

I added an adjustable delay between get_shooting() going true and the shot starting, "Delay after get_shooting" on the theory this might affect the initial shots being off.

Logged

Don't forget what the H stands for.

srsa_4c

4451

Re: Improving CHDK ND filter support

« Reply #124 on: 10 / February / 2019, 12:21:17 »

I made a new test run with the newest script on the two mentioned cameras (with default params).
About hook placement: as I can imagine, many ports can have various problems and most of those won't be fixed. I did not touch the ones that I have, yet.

ndtest_ixus115.csv (5.03 kB - downloaded 7 times.)

ndtest_a490.csv (4.93 kB - downloaded 10 times.)

Logged

reyalp

14111

Re: Improving CHDK ND filter support

« Reply #125 on: 10 / February / 2019, 15:22:02 »

Quote from: srsa_4c on 10 / February / 2019, 12:21:17

I made a new test run with the newest script on the two mentioned cameras (with default params).

Thanks.

Quote

About hook placement: as I can imagine, many ports can have various problems and most of those won't be fixed. I did not touch the ones that I have, yet.

Yes, understood. Detailed tests like this always pick up issues...

On the results:
ixus115 correctly retries now, and behaves like a normal ND only cam that needs the prop set in quick.

A490
It looks like tv override doesn't work in quick, and even doesn't update the propcase. The av propcase in the log is also not overridden. This is quite strange. One explanation could be if get_shooting doesn't behave as expected, so the overrides don't get SET_NOW. I've updated the script to check for this in r5160

A490 is propset 3, dryos 43. It would be interesting to know if other similar cameras have this problem.

The new A490 log doesn't have the first shot overexposed glitch. It would be nice to know if this was due to script changes or test conditions. Can you try running with the "Delay after get_shooting" set to 50?

Logged

Don't forget what the H stands for.

srsa_4c

4451

Re: Improving CHDK ND filter support

« Reply #126 on: 10 / February / 2019, 18:26:53 »

Quote from: reyalp on 10 / February / 2019, 15:22:02

Quote
About hook placement: as I can imagine, many ports can have various problems and most of those won't be fixed. I did not touch the ones that I have, yet.
Yes, understood. Detailed tests like this always pick up issues...

I meant this like: we may need to work around bugs (if possible) if we can't fix the ports.

Quote

The new A490 log doesn't have the first shot overexposed glitch. It would be nice to know if this was due to script changes or test conditions. Can you try running with the "Delay after get_shooting" set to 50?

Two test runs, one with 100, other with 50ms delay. Artificial lighting this time.
The a490 is my only camera between dryos r31 and r47.

ndtest_a490_5160.csv (9.2 kB - downloaded 7 times.)

Logged

reyalp

14111

Re: Improving CHDK ND filter support

« Reply #127 on: 03 / March / 2019, 22:05:27 »

Quote from: srsa_4c on 10 / February / 2019, 18:26:53

I meant this like: we may need to work around bugs (if possible) if we can't fix the ports.

Of course. For now I'm happy if we can identify which are port bugs and which are differences in the underlying firmware.

In the ixus115 case, the workaround is setting the Av prop (CAM_ND_SET_AV_VALUE) which I think we will probably want to set by default for ND-only cams anyway (though now I'm wondering if we want an option to disable it from script to exercise ports

). Fixing the hook location would probably be good for other reasons (remote hook in the top level of capt_seq has caused other problems like https://chdk.setepontos.com/index.php?topic=7934.msg132496#msg132496 / commit 4799) but isn't urgent.

a490 seems like a Canon firmware difference. The script retry putting in the ND in the remote hook actually seems to work, but shutter override appears to fail in quick mode. The "ND" value and state functions clearly work based on the single and cont results, so I'm fine just noting that as a port quirk too.

I would be interested to know if the first shot glitch still shows up with the current script on A410, IXUS65 and IXUS870.

Logged

Don't forget what the H stands for.

koshy

1096

Re: Improving CHDK ND filter support

« Reply #128 on: 04 / March / 2019, 11:53:28 »

Quote from: reyalp on 04 / February / 2019, 02:08:25

I'd appreciate test results from any cameras with an ND filter that aren't listed as tested below.

It's still either these or more: https://chdk.setepontos.com/index.php?topic=13445.0
I can't promise when but I'll test all I have that are still missing.

Logged

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...)

koshy

1096

Re: Improving CHDK ND filter support

« Reply #129 on: 04 / March / 2019, 12:00:54 »

Since I'll I get 'em all out and updated to the latest build is there anything else you'd like to happen once each is active?
I'll use but a handful of fast SD cards. Once I'm done with one it goes back to hibernation for the time being. So, that would be best to know first I guess...

Logged

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...)