If you override the aperture then the same aperture is used for both shots (assuming the override is within the aperture range for the zoom level).
Quote from: philmoz on 31 / May / 2018, 21:31:44If you override the aperture then the same aperture is used for both shots (assuming the override is within the aperture range for the zoom level).In a camera without an iris?! ... and in areas of the sensor that are shielded from any light that comes through the lens.
Camera without iris was what I was missing - but to be fair you did not mention this in the post I quoted and you claimed to be overriding the aperture.
For the bug it seems relevant how long shutter half-press is used. Long => overrides really make it. Shorter => overrides fail but still get written to meta data.
PS: What happened to the forum it eats my white space upon "preview" and when I try editing my old posts with lots of color formats those explode, too.
FWIW, you can turn the WYSIWYG editor turned off in your profile under look and layout.
Overrides not being applied on quick press (shooting without waiting for the camera to be ready) is a pretty common bug. ixus950_sd850 does not appear to have the usual workaround for this. Test build attached.
Note I initially thought you were talking about ixus850_sd800, which *also* appears to not have the workaround. If you have that one, it might be worth testing too.
I checked and I think I still have all Powershot SD cameras supported by CHDK. I can test with any eventually.
ixus950_sd850 does not appear to have the usual workaround for this. Test build attached.
Very good, that worked in fixing it. SD850 can be checked in.
What would be the easiest way to see what other cameras are affected? Testing the behaviour or looking at the code? Care to extend the fix to others? Seems worthwhile...
// this code added to avoid some incorrect behavior if overrides are used. // but it can cause some unexpected side effects. In this case, remove this code! "MOV R0, #0\n" "STR R0, [R4,#0x24]\n" // fixes overrides behavior at short shutter press // end of my code
"LDR R0, [R4,#0x24]\n" "CMP R0, #0\n" "BEQ loc_FF86CEF4\n"
So if you wanted to go through your cameras and check, I'd suggest looking at capt_seq.c, and testing if there is no comment or workaround.
capt_seq.c - auto-generated by CHDK code_gen.
Started by m2tk
Started by Kenith Olson
RAW Shooting and Processing
Started by trialex
Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by Wishmaster
Started by 74prof
General Help and Assistance on using CHDK stable releases