Quote from: Michel2e on 28 / November / 2015, 06:06:23if of interest here are typical resultshere are 2 pics from this testing session. JPG direct from camera.Looking at the embedded "CanonSi Makernote" information in the image shows the AF image with a subject distance of 100. Same result as srsa_4c! The MF image shows it's subject distance as 6553. Exactly what CHDK tries to set it to
if of interest here are typical resultshere are 2 pics from this testing session. JPG direct from camera.
Quote from: Michel2e on 17 / November / 2014, 03:53:49Unfortunately, I cannnot run the MF mecha test3 script. I get a message:60 attempt to index global 'capmode" (nihil value).The chdk installation is not completed. You need the file CHDK/LUALIB/capmode.lua. Download the complete CHDK package for your camera and copy all files from the zip file to the sd card.msl
Unfortunately, I cannnot run the MF mecha test3 script. I get a message:60 attempt to index global 'capmode" (nihil value).
Thought I'd try this out on my A4000, but I'm getting the same error, and the capmode.lua file is definitely on my SD card.CHDK 1.5.0.
It appears there is a bug in the script. It does not load the capmode module. If the file were missing, it would give a different error. You could add capmode=require'capmode' at the top, but considering it can't run as written, it may not be the script waterwingz intended to post.
On the broader topic of the thread:It occurred to me that you could use raw op to detect contrast and generate a camera specific calibration. The user would need aim the camera at an appropriate stable, distant target.
Neat idea. But I think that's basically what the "half press" focus ( and set_aflock(1) ) commands already do?
If it works that would certainly be simpler and faster. I had the (possibly mistaken) impression from earlier discussion that reading back the SD from Canon AF didn't give usable values. Maybe that was due to confusion about the different CHDK and propcase values.
Quote from: reyalp on 15 / December / 2015, 20:48:05If it works that would certainly be simpler and faster. I had the (possibly mistaken) impression from earlier discussion that reading back the SD from Canon AF didn't give usable values. Maybe that was due to confusion about the different CHDK and propcase values.I'm still working on proving this - will likely take me a couple of weeks to find time to finish my testing. It would help if I owned one of the really bad cameras but I'll depend on some of the forum regulars for that.
My current assumption is that if you let the camera focus at a distant object, you can get a valid SD and/or mecha position that will work for each zoom step. The exact value may vary from shot to shot as the lens mechanism is not very precise and acceptable focus at infinity can occur over a range of settings - especially at maximum wide angle. But there should be a set of values that will work for any particular camera at any zoom step setting and focus at infinity.I'm still working on proving this - will likely take me a couple of weeks to find time to finish my testing. It would help if I owned one of the really bad cameras but I'll depend on some of the forum regulars for that.
Started by radioman193 « 1 2 ... 8 9 » General Help and Assistance on using CHDK stable releases
Started by sarkar General Help and Assistance on using CHDK stable releases
Started by Geezer « 1 2 3 » General Help and Assistance on using CHDK stable releases
Started by LeTomas DryOS Development
Started by LeTomas « 1 2 » General Discussion and Assistance