Improving CHDK ND filter support - page 20 - General Discussion and Assistance - CHDK Forum
« previous next »
Pages: 1 ... 15 16 17 18 19 [20] 21 22 23 24   Go Down

Improving CHDK ND filter support

  • 234 Replies
  • 107503 Views
*

Offline koshy

  • *****
  • 1096
Re: Improving CHDK ND filter support
« Reply #190 on: 19 / August / 2019, 06:09:58 »
Advertisements
Quote from: reyalp on 18 / August / 2019, 21:33:40
@koshy:
Can you try the attached build on G9?
Sure
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...)
*

Offline koshy

  • *****
  • 1096
Re: Improving CHDK ND filter support
« Reply #191 on: 19 / August / 2019, 06:58:49 »
Quote from: reyalp on 17 / August / 2019, 21:21:14
Quote from: koshy on 17 / August / 2019, 21:08:45
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.
Here we go on that one.
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...)
*

Offline Caefix

  • *****
  • 947
  • Sorry, busy deleting test shots...
Re: Improving CHDK ND filter support
« Reply #192 on: 20 / August / 2019, 12:07:29 »
{=) Found again & CHIMPed & tested ixus160

--[[
@title ND_test.Lua
@subtitle :...,....1....,....2....,....3....,....4....,....5
@param N ND AUS ein
@values N AUS ein
]]--

for i=1,9 do
    set_nd_filter(1+i%2)
    click("shoot_half")
    print (i,-get_av96(),-get_tv96())
wait_click(999)
sleep(999) end
set_nd_filter(2-(N or 2)%2)
sleep(999)

This miniscript returns !=0 only after a shot here.
There are 2 groups of cams...

PS: Have done a rerun with SX610 just for fun.
... same group.
« Last Edit: 20 / August / 2019, 14:12:04 by Caefix »
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 14117
Re: Improving CHDK ND filter support
« Reply #193 on: 20 / August / 2019, 23:11:02 »
@koshy I think I found my mistake in the last A530 build. Please try this one. Thanks
Logged
Don't forget what the H stands for.
*

Offline reyalp

  • ******
  • 14117
Re: Improving CHDK ND filter support
« Reply #194 on: 20 / August / 2019, 23:48:05 »
Quote from: Caefix on 20 / August / 2019, 12:07:29
{=) Found again & CHIMPed & tested ixus160
Thanks.

I'm not clear about the script. Does this show some problem?

Note in Lua, the code
Code: [Select]
set_nd_filter(2-(N or 2)%2)
probably doesn't do what you want. Only nil and false are false, so "N or 2" is always N (since N is a menu param in this script).
Logged
Don't forget what the H stands for.
*

Offline koshy

  • *****
  • 1096
Re: Improving CHDK ND filter support
« Reply #195 on: 21 / August / 2019, 05:35:51 »
Quote from: reyalp on 20 / August / 2019, 23:11:02
@koshy I think I found my mistake in the last A530 build. Please try this one. Thanks
Nice work, that gets it. USB remote now works as it should - with synch enabled. 5V on: half press, black screen for like 10 sec, 5V off during that period shoots. ND test attached.
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...)
*

Offline Caefix

  • *****
  • 947
  • Sorry, busy deleting test shots...
Re: Improving CHDK ND filter support
« Reply #196 on: 21 / August / 2019, 13:16:45 »
 :haha Ixus145...

Aye, a fast script once written for some trouble of the day, no literature.
Intention: Watching, feeling, hearing the cam & ND work.
I expected as a sideeffect updated values in print() after "click",
but I seem to get 0 or the values of the last shot.
Btw.: I feel a reaction at 'ND not enabled port' SX700e.
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 14117
Re: Improving CHDK ND filter support
« Reply #197 on: 21 / August / 2019, 14:10:47 »
Quote from: Caefix on 21 / August / 2019, 13:16:45
Ixus145...
Thanks again :)
Quote
Aye, a fast script once written for some trouble of the day, no literature.
Intention: Watching, feeling, hearing the cam & ND work.
I expected as a sideeffect updated values in print() after "click",
Normally, Canon firmware doesn't known about ND override, so get_tv96 shouldn't change (maybe a little if Canon auto-exposure comes out different, but not because of ND). get_av96 also usually won't change in current CHDK, except on ports like elph175_elph180 that set the prop. In the in the future, more ports will probably do this.

Quote
Btw.: I feel a reaction at 'ND not enabled port' SX700e.
Yes, this camera almost certainly does not have ND. SX710 100% for sure doesn't and appears to be the same optics.
Logged
Don't forget what the H stands for.
*

Offline Caefix

  • *****
  • 947
  • Sorry, busy deleting test shots...
Re: Improving CHDK ND filter support
« Reply #198 on: 21 / August / 2019, 14:33:32 »
...SX710.
Yes - no ND, I would "see" it, but set_nd is not ignored, there´s a vibration in the lens.
Maybe aperture reacts, shouldn´t that be another statement?
Logged
All lifetime is a loan from eternity.
*

Offline reyalp

  • ******
  • 14117
Re: Improving CHDK ND filter support
« Reply #199 on: 21 / August / 2019, 16:22:07 »
Quote from: Caefix on 21 / August / 2019, 14:33:32
Yes - no ND, I would "see" it, but set_nd is not ignored, there´s a vibration in the lens.
Maybe aperture reacts, shouldn´t that be another statement?
Yes, on most cameras without ND, the Canon "ND" functions still exist and aperture to minimum / maximum.  See https://chdk.setepontos.com/index.php?topic=13228.msg135727#msg135727

However, current SX700 builds should have the ND functions disabled since r4974. Maybe you're using an old build?
Logged
Don't forget what the H stands for.
Pages: 1 ... 15 16 17 18 19 [20] 21 22 23 24   Go Up
« previous next »
 

Related Topics
SimplePortal 2.3.6 © 2008-2014, SimplePortal