set_aelock() - for video modes only ? - page 3 - General Discussion and Assistance - CHDK Forum
supplierdeeply
« previous next »
Pages: 1 2 [3]   Go Down

set_aelock() - for video modes only ?

  • 26 Replies
  • 10795 Views
*

Online philmoz

  • *****
  • 3426
    • Photos
Re: set_aelock() - for video modes only ?
« Reply #20 on: 20 / June / 2014, 21:40:37 »
Advertisements
Quote from: waterwingz on 20 / June / 2014, 20:53:59
Okay - propcase scan script built and tested.  Runs kind of slow and it's not elegant but it works on all my cameras.

I think we now have valid alternative values for propset2 to propset6.

Propset Current New
1??
2206297
3208301
4210303
5210303
6209302

If someone with a propset 1 camera can try the script and report,  we might be done here?

(and this post marks the debut of CHDK running on my Powershot N)

If I can coax a few minutes charge into the old batteries I'll check the IXUS700 - if the pattern holds it should be 296.

Phil.

Edit: The IXUS700 does not seem to have an equivalent alternative value. Property 7 does get set to 1 when shooting; but it is set immediately, it does not wait until focussing and exposure are finished. Changing this one could affect other scripts that use get_shooting. The others should be ok to commit to SVN.

« Last Edit: 20 / June / 2014, 23:24:33 by philmoz »
Logged
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)
  g7x2 (1.01a, 1.01b, 1.10b)
*

Offline waterwingz

  • ******
  • 12125
    • Waterwingz
Re: set_aelock() - for video modes only ?
« Reply #21 on: 20 / June / 2014, 21:51:42 »
Quote from: philmoz on 20 / June / 2014, 21:40:37
If I can coax a few minutes charge into the old batteries I'll check the IXUS700 - if the pattern holds it should be 296.
If battery life is an issue, delete the 1) regular shoot test part of the script - you really only need the 2) aelock shoot test part
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline blackhole

  • *****
  • 867
  • A590IS 101b
    • Planetary astrophotography
Re: set_aelock() - for video modes only ?
« Reply #22 on: 21 / June / 2014, 03:41:00 »
Quote
The IXUS700 does not seem to have an equivalent alternative value.
The same situation is with the a530.
Logged
*

Offline waterwingz

  • ******
  • 12125
    • Waterwingz
Re: set_aelock() - for video modes only ?
« Reply #23 on: 21 / June / 2014, 08:21:44 »
Quote from: philmoz on 20 / June / 2014, 21:40:37
Edit: The IXUS700 does not seem to have an equivalent alternative value. Property 7 does get set to 1 when shooting; but it is set immediately, it does not wait until focussing and exposure are finished. Changing this one could affect other scripts that use get_shooting. The others should be ok to commit to SVN.
Good  catch - the script does not really check for that.  I guess I should recheck the other propsets - athough the "pattern" of old vs new value to use is the same for all of them.

Quote from: blackhole on 21 / June / 2014, 03:41:00
The same situation is with the a530.
Both propset 1 - as are about 20% of the cameras ported to CHDK.

I'll update the note in the wiki scripting function for set_aelock() to indicate the issue with propset 1 cameras.
« Last Edit: 21 / June / 2014, 08:30:53 by waterwingz »
Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline srsa_4c

  • ******
  • 4450
Re: set_aelock() - for video modes only ?
« Reply #24 on: 01 / July / 2014, 11:40:12 »
Quote from: waterwingz on 20 / June / 2014, 20:53:59
Okay - propcase scan script built and tested.  Runs kind of slow and it's not elegant but it works on all my cameras.
Thanks for the script.

As it turns out, not all cameras we call "propset 2" work the same.
This is the result of proptest.lua on my propset 2 cameras:
                        1st pass     2nd pass
a460   (DIGIC II) vx         206            -
a470  (DIGIC III) dry    115,206          115
sx100 (DIGIC III) dry    115,206          115
g10     (DIGIC 4) dry    297,206          297

That means we should probably bring back 206 as PROPCASE_SHOOTING for propset 2, unless someone has a better idea (like splitting propset 2 into two or more propsets?).
See this bug report.
Logged
*

Offline waterwingz

  • ******
  • 12125
    • Waterwingz
Re: set_aelock() - for video modes only ?
« Reply #25 on: 01 / July / 2014, 13:08:14 »


Quote from: srsa_4c on 01 / July / 2014, 11:40:12
That means we should probably bring back 206 as PROPCASE_SHOOTING for propset 2,

That would mean a lot of cameras cannot use set_aelock but it's probably the easiest solution and can be implemented right away.

Logged
Ported :   A1200    SD940   G10    Powershot N    G16
*

Offline oid_maps

  • *
  • 16
A570 and A720 Re: set_aelock() - for video modes only ?
« Reply #26 on: 02 / July / 2014, 07:11:43 »
On CHDK_DE 1.3, rev. 3492:

A570 IS (Firmware 1.00E):
Code: [Select]
Started
1) regular shoot test
 matches :  115 206
2) aelock shoot test
 matches :  115
Done

A720 IS (Firmware 1.00C):
Code: [Select]
Started
1) regular shoot test
 matches :  115 206
2) aelock shoot test
 matches :   
Done
Logged
My cameras:
* Canon PowerShot:
  - A570 IS (Firmware 1.00E)
  - A2000 IS (Firmware 1.00C)
* Other manufacturers:
  - Pentax K10D (Firmware 1.31)
Pages: 1 2 [3]   Go Up
« previous next »
 

Related Topics