It *feels* as though CHDK is introducing a fixed random pattern of zeroed pixel values, regardless of camera A or camera B.
Only *one* of RGB channels gets zeroed. There appears to be some processing or interpolation going on because the visual result is what looks like 3x3 dot [Fig 2], with the dot color & morphology depending on the zeroed channel.
Thank you for taking the time and for your professional reply. This CHDK is the latest posting for the SX110 & uses DNG 1.3.
At first when I noticed this behavior with camera A, that was when I thought the same as you, something in the hardware I was not addressing by setting/using the appropriate bad pixel options in CHDK. I tried every reasonable combination and opticn CHDK offers in the RAW menu to no avail, really stuck.
CHDK in Camera A reports 6100 bad pixels and camera B has 13000
Enabling DNG 1.1 did create a visually-perfect white image, so does it does work OK. But I can't recall seeing the relevant explanation in the CHDK docs. If it is not there, perhaps a developer or site admin could write it in.
I did certainly had read about badpixel and its differences, thank you suggesting it anyway. That is a very good mechanism because I do long exposures ... I understand it operates on soft-defective pixels (hot/warm) as opposed to dead (black) pixels.
Q1. Does badpixel and badpixel.bin work together in DNG 1.1?
Q2. Is there a menu option that I have to set ?
Q3. What are the differences between 1.3 and 1.1? A link?
Q4. Is there a way I can read the DNG files directly from the SD card in the camera without having to remove it (and not use PTP, yet)?
However, there may be a caveat in CHDK itself that a developer might consider looking at: DNG file numbering, DNG file numbers don't get incremented on their own. I suspect that because the parallel JPG file gets automatically transferred to the computer after processing the shot leaving no trace of the IMG_* file in the folder. Hence, perhaps for that reason, CHDK does not increment the file number. In fact, if I don't delete the last shot (leave an empty folder), then more than one DNG file with the same number gets saved.
At present, even though CHDK is running and saving DNGs by computer control, I don't have access to CHDK camera features via RemoteCapture. For example, the shutter speed drop-down does not have the extended Tv values.
Q. In the context above, what would I need to obtain full seamless computer-controlled remote operation? I think there may be no way out but to change the device driver, at least, and then add extensions to CHDK, a kind of CHDK++, scripts, etc ?
You seem very knowledgeable ... I noticed a C code snippet in a reply ... are you one of the developers?
Started by ab
« 1 2 3 »
Started by bugsplatter
Started by turnstile
« 1 2 »
Started by waterwingz
Forum related topics (including issues)
Started by hari-bhari
« 1 2 3 »
RAW Shooting and Processing