No problem. Here's a test build with zoom delay 300
I have been torturing my poor ixus with various scripts some hours now, zooming and focusing back and forth, taking pictures in between, etc. Not a single crash!
(excluding crash from "set_prop(221,1)", Differing from comment at PROPSET6.LUA, in ixus160 M1 pic size value seems to be 2, leaving 1 being something undefined...)
Aflock behaviour seems to be a bit mystery in ixus160. It looks like aflock is not needed to achieve manual focus. However, with aflock focus behaves differently than without it. (With aflock there seems to be some kind of ceiling, focus does not change anymore after certain value)
FWIW, CHDK behavior with AF is slightly different from aflock and MF. In AF, calling set_focus just stores a value, which is applied during shooting after the cameras normal AF process has finished. If aflock or MF is enabled, calling set_focus immediately sets the focus.
When you say "ceiling" you mean you can't set_focus beyond a certain distance unless you use aflock?
Can you check what the value is for each resolution? In chdkptp, you can just use =get_prop(221) after highlighting the resolution in the func menu.
$ diff PROPDUMP.LOG_L PROPDUMP.LOG_W67c67< [65]= 0,---> [65]= 3100,94c94< [92]= 0,---> [92]= 5152,106c106< [104]= 0,---> [104]= 5152,117c117< [115]= 0,---> [115]= 1,250c250< [248]= 0,---> [248]= 3100,274c274< [272]= 1040,---> [272]= 897,
luar set_prop(143,2)luar set_zoom()luar set_aflock(1)luar set_focus(1014)
Now that zoom is working perfectly, I ran into focusing problems. Example: Without chdk, I zoomed in to somewhere middle and took a photo of the camera box with autofocus. Crop of that picture attached. Next, I booted into chdk and figured out the zoom used in previous step. Then took pictures with all possible focus settings. Crop of the best picture attached.
Any idea?
Does it happen if you just have chdk running, and do everything else the same as the no CHDK case? E.g. zoom manually and use auto focus? Or does it only happen when you use set_focus and/or set_zoom?
You can try using set_mf() instead of set_aflock()
With no zoom or with very little zoom (under 10) it is possible to reach correct focus with set_focus(). There is even some room, you do not have to set focus value as low as you could.It looks like with higher zoom values the minimum focus value is too high. Thus set_focus() is not able to go as low as autofocus is. For example, with full zoom (100) lowest possible focus value is 1300, which is still blur, and setting higher value only makes it worse. So the correct value is probably somewhere under 1300
It looks like with higher zoom values the minimum focus value is too high. Thus set_focus() is not able to go as low as autofocus is. For example, with full zoom (100) lowest possible focus value is 1300, which is still blur, and setting higher value only makes it worse. So the correct value is probably somewhere under 1300Are these minimum values defined somewhere in CHDK?
That's not to say the IXUS160 does not have it's own MF problems. But it's far from perfect on most other Powershots.
I think what gaphill described is something quite different: The focus distance *range* accessible to set_focus is different from what the canon AF can do.
When you tried zooming to 100, have you tried doing this manually with the camera buttons vs using set_zoom?If you focus with AF at a distance you can focus with set_focus, what does get_focus return?
___> cconnected: Canon IXUS 160, max packet size 512con> rec # After this driving to max zoom manuallycon 1> rs # Result: sharp imagecon 4> luar return get_focus()5:return:1300con 5> luar set_focus(1300)con 6> rs # Result: blur imagecon 9> luar return get_focus()10:return:1300
Started by amavroidis « 1 2 ... 5 6 » General Discussion and Assistance
Started by STEREO_A Creative Uses of CHDK
Started by reyalp DryOS Development
Started by reyalp General Discussion and Assistance
