supplierdeeply

Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!

  • 203 Replies
  • 40903 Views
Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #80 on: 26 / November / 2013, 16:15:17 »
Advertisements
It should be available in movie mode (mode dial explicitly set to movie mode), but they don't call this AE lock, see manual page 110.
Well what do you know - there it is!  My only excuse is that it's not actually "my" camera   :-[

And when locked that way,  the rest of the script performs just like my other cameras.     So I'm guessing the call to
Code: [Select]
call_event_proc("PT_DoAELock")needs something different for the SX50?

As a side note,  it appears that the SX50 port does not capture the rotary jog dial correctly.  Turning the dial in <ALT> or script modes still causes the Canon OSD exposure offset needle gage to move.  I'll take a look at that.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline srsa_4c

  • ******
  • 3601
Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #81 on: 26 / November / 2013, 16:51:53 »
So I'm guessing the call to
Code: [Select]
call_event_proc("PT_DoAELock")needs something different for the SX50?
Yes, several event procedures changed names in newer cameras, this cam has "SS.DoAELock".

Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #82 on: 26 / November / 2013, 17:02:57 »
So I'm guessing the call to
Code: [Select]
call_event_proc("PT_DoAELock")needs something different for the SX50?
Yes, several event procedures changed names in newer cameras, this cam has "SS.DoAELock".
"My" sx50 seems to have gone off on a "walk about".  When it returns,  I'll see of I can use return codes to figure out which event proc works for which camera.  Is there any other way to figure out which one to use?
Ported :   A1200    SD940   G10    Powershot N    G16

Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #83 on: 26 / November / 2013, 21:19:53 »
Yes, several event procedures changed names in newer cameras, this cam has "SS.DoAELock".
That works for the SX50.  Thanks.

A grep through the funcs_by_name.csv files show either DoAELock or PT_DoAELock.  I have the script trying both .. but issuing PT_DoAELock seems to hang the SX50 sometimes.  Would be nice to have a different way to pick which function to call.
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline philmoz

  • *****
  • 3066
    • Photos
Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #84 on: 26 / November / 2013, 21:35:28 »
Yes, several event procedures changed names in newer cameras, this cam has "SS.DoAELock".
That works for the SX50.  Thanks.

A grep through the funcs_by_name.csv files show either DoAELock or PT_DoAELock.  I have the script trying both .. but issuing PT_DoAELock seems to hang the SX50 sometimes.  Would be nice to have a different way to pick which function to call.

C stubs like DoAFLock and UnlockAF, with Lua / uBasic hooks?

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)

Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #85 on: 26 / November / 2013, 23:20:58 »
C stubs like DoAFLock and UnlockAF, with Lua / uBasic hooks?
Meaning adding a set_aelock() function that works like set_aflock() ?   I like that idea a lot!

Not sure why we have not hit that before? Probably because script writer just pound out the set_xv96() commands before every shot and don't need it ?  But for manual control of exposure in video, I guess we do need it now.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline philmoz

  • *****
  • 3066
    • Photos
Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #86 on: 27 / November / 2013, 04:01:00 »
C stubs like DoAFLock and UnlockAF, with Lua / uBasic hooks?
Meaning adding a set_aelock() function that works like set_aflock() ?   I like that idea a lot!

Not sure why we have not hit that before? Probably because script writer just pound out the set_xv96() commands before every shot and don't need it ?  But for manual control of exposure in video, I guess we do need it now.

Untested patch adds DoAELock & UnlockAE wrappers and set_aelock function for Lua & uBasic.

Note: I had to add NULL_SUB entries for DoAELock and UnlockAE for many older VxWorks cameras so it will not work on those.

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)

Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #87 on: 27 / November / 2013, 11:28:03 »
Untested patch adds DoAELock & UnlockAE wrappers and set_aelock function for Lua & uBasic.
Note: I had to add NULL_SUB entries for DoAELock and UnlockAE for many older VxWorks cameras so it will not work on those.
Wow - that was quick. Nice to be able to update the sigfinder rather than hand edit all those files!

Works well on my standard cameras - the sx50 is out "birding" again so I'll check it later.

Updated test script attached - I added set_aelock() and commented out the related event proc calls.  There's a user @param to let you selectively enable the function for testing purposes.  I'll remove that later when the script goes into general release.

Script still needs a little work - initial values for Tv, Sv, Av from get_xv96() are not the values the video mode uses so you have to adjust the controls to sync.  Maybe I'll just default the initial values via a manual overrided to  1/100, f2.8 and ISO100 so that everything starts sync'd.  Could make the values @params I guess.

Also need to add a @param value for Maximum ISO - let users with cams like the SX50 that crash at ISO3200 lock that out in their script.

Other than that,  I'm pretty happy with how the script works now.   Thanks for turning set_aelock() around so quickly!

Note: I had to add NULL_SUB entries for DoAELock and UnlockAE for many older VxWorks cameras so it will not work on those.
So set_aelock(),  like set_aflock(),  does not return status.  Is it worth adding something so that cameras that point to a NULLSUB return 0 and everything else returns 1 ?

Edit : attachment deleted - see follow post later in this thread for newer version of the script
« Last Edit: 29 / November / 2013, 09:45:12 by waterwingz »
Ported :   A1200    SD940   G10    Powershot N    G16


*

Offline srsa_4c

  • ******
  • 3601
Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #88 on: 27 / November / 2013, 14:24:35 »
add NULL_SUB entries for DoAELock and UnlockAE for many older VxWorks cameras
The attached patch for finsig_vxworks should make the above unnecessary.

*

Offline philmoz

  • *****
  • 3066
    • Photos
Re: Video Manual Control: ISO, APERTURE & SHUTTER SPEED CONTROL, PLEASE!!!!
« Reply #89 on: 27 / November / 2013, 16:35:05 »
add NULL_SUB entries for DoAELock and UnlockAE for many older VxWorks cameras
The attached patch for finsig_vxworks should make the above unnecessary.

Thanks, I'll merge that with my changes and add it to 1.3.
Should be added to 1.2 as well for compatibility, might wait a bit so it can be tested more.

Edit Added to 1.3 in revision 3250.

Phil.
« Last Edit: 28 / November / 2013, 03:33:15 by philmoz »
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)

 

Related Topics