Setting focus from scripts or menus - page 16 - General Discussion and Assistance - CHDK Forum

Setting focus from scripts or menus

  • 556 Replies
  • 133462 Views
Advertisements
I carefully installed the latest CHDK, but forgot to make STICK download 1.3 rather than 1.2.
Having a menu option or other GUI way to do that would be a nice addition to STICK  :xmas
Ported :   A1200    SD940   G10    Powershot N    G16

One of the main goals is to be able to manually focus from a script regardless of camera setup (MF or AFL).

In fact, the new SDM interface that I am working on uses just such a function.
For those cameras that require to be in manual-focus mode I am simply assuming that  my existing PressSw1AndMF code works for the vast majority of current SDM-supported cameras (the G15 and SX50hs are the most recent and presumably have problems, not tested yet).

I am also assuming the corresponding #defines in the single camera.h file are correct.
The strategy is to simply wait until a user complains.

That said, I will be sending-out builds for testing in about one week.
I will try to contact previous testers and regardless of whether they do my tests or not ask them to do the CHDK test.

I will start with the CHDK cameras still awaiting data at that time.

SDM testers are normally very unreliable.

In fact, the new SDM interface that I am working on uses just such a function.
We are still waiting on more information about what works with what prior to completing any changes to CHDK.

Quote
For those cameras that require to be in manual-focus mode I am simply assuming that  my existing PressSw1AndMF code works for the vast majority of current SDM-supported cameras (the G15 and SX50hs are the most recent and presumably have problems, not tested yet).
As we are learning,  this is not always the case.  Sometimes PressSw1AndMF actually crashes the camera - the G15 and SX50 being two such examples.

Quote
I am also assuming the corresponding #defines in the single camera.h file are correct.
I don't think that's necessarily a safe assumption - most ports have been done by people who are using CHDK for the first time.  Errors and partial testing are unfortunately not uncommon.  Rumour has it that one very senior CHDK developer's personal camera had the #defines configured in a manner that allowed the camera to crash. ;)

Quote
The strategy is to simply wait until a user complains.
My guess is that when we are done,  the few CHDK ports where we have no test data will simply have all MF capability disabled until we hear from an owner of that camera.

Quote
That said, I will be sending-out builds for testing in about one week. I will try to contact previous testers and regardless of whether they do my tests or not ask them to do the CHDK test. I will start with the CHDK cameras still awaiting data at that time.
Thank you.

Quote
SDM testers are normally very unreliable.
People have different priorities in life.  Let's be thankful for the few who actively contribute.
Ported :   A1200    SD940   G10    Powershot N    G16

Canon A630
set_focus_only test blanked screen and shut down camera
It looks like you also did not enable Lua Native Calls in the CHDK Miscellaneous menu?  Would you please do so and rerun the test (with the set_focus_only test disabled).
Ported :   A1200    SD940   G10    Powershot N    G16


There are some more recent test results in the German CHDK forum: http://forum.chdk-treff.de/viewtopic.php?p=28795#p28795 and the next posts
Some of these are good tests but others unfortunately have problems.  The testers seem confused about the need to enable Lua Native Calls and about the need to disable individual tests if they crash rather than disabling the interlock bypass mode.

gehtnix : ran old verion of script for ixus50 and did not have Lua native calls enabled for A610

Knarf :  ran old version of script

ferdy :  ran with Lua Native calls disabled and then disable the event proc test

Gernot : ran all his tests with Lua Native calls disabled

S5andi : disabled interlock bypass when set_focus_only crashed rather than just disabling that test.
Ported :   A1200    SD940   G10    Powershot N    G16

One of the main goals is to be able to manually focus from a script regardless of camera setup (MF or AFL).

In fact, the new SDM interface that I am working on uses just such a function.
For those cameras that require to be in manual-focus mode I am simply assuming that  my existing PressSw1AndMF code works for the vast majority of current SDM-supported cameras (the G15 and SX50hs are the most recent and presumably have problems, not tested yet).

I am also assuming the corresponding #defines in the single camera.h file are correct.
The strategy is to simply wait until a user complains.

That said, I will be sending-out builds for testing in about one week.
I will try to contact previous testers and regardless of whether they do my tests or not ask them to do the CHDK test.

I will start with the CHDK cameras still awaiting data at that time.

SDM testers are normally very unreliable.
I can test SX130 101c and 101f. Will get a third one so i will have a pair of the same FW for SDM next week.
A590 IS-1.01b(x5), SX130IS-101c(x3), 101f(x2)
3dstereo-aeropanorama-Jungfraujoch
http://www.stereopan.tk

I can test SX130 101c and 101f. Will get a third one so i will have a pair of the same FW for SDM next week.
Thank you.  We really only need test results from one camera - the firmware version does not matter.   However, please remember to enable Lua Native calls in the CHDK Miscellaneous menu - several recent testers have neglected to do that and we end up with a only a partial test result.
Ported :   A1200    SD940   G10    Powershot N    G16

*

Offline na560

  • *
  • 11
Canon A630 rerun with Lua native calls enabled.
Sorry about that.


*

Offline na560

  • *
  • 11
A610 and S90

*

Offline na560

  • *
  • 11
Results for A650 attached.

Just remembered that A610 crashed on set_focus only test.

 

Related Topics