The behaviour you are seeing is correct - a CHDK ISO value of 200 will come out on the camera as roughly ISO 320.This is because CHDK uses 'real' ISO values and the camera displays 'market' ISO values (I don't know the history behind this, it's just the way it is).When you set an ISO override in CHDK you are asking for a 'real' ISO value. CHDK calculates the equivalent 'market' ISO value and tells the camera to use that value using _SetPropertyCase(PROPCASE_SV_MARKET...All existing CHDK ports work this way - changing CHDK to use 'market' values for the IXUS 1000 would make this camera non-standard (from a CHDK perspective).Phil.
If I understand correctly you are saying that when you set an ISO override your images can come out underexposed - if so this is the same as on my cameras.On all three versions I've done (G12, SX30 and IXUS310) the overrides are applied after the camera calculates the exposure.
Now I can't say for sure that this is the 'correct' behaviour - you might think that being able to set an override and have the camera correctly calculate exposure would be more useful. Of course it could also be argued that not having the camera change exposure is better as it allows you to use the override to correct cases where the camera gets the exposure wrong.
It would be interesting to see how other cameras behave.
My camera have only 1 long time exposure mode, i can select time from 1 sec to 15 secMaybe it is possible to detect in chdk the program mode, or if chdk use time overwrite or aperture overwrite and do in automatic modes the code i use for ixus 1000 if it can work on other camera too.this programs on my camera do time aperture, automatic depend on ISO. { MODE_AUTO, 32768 }, { MODE_P, 32772 }, { MODE_EASY, 33314 }, // Changed in SX210 { MODE_PORTRAIT, 32783 }, // Changed in SX210 { MODE_NIGHT_SNAPSHOT, 32781 }, // Changed in SX210 { MODE_LANDSCAPE, 32782 }, // Changed in SX210 { MODE_VIDEO_COLOR_ACCENT, 2610 }, //?? { MODE_VIDEO_COLOR_SWAP, 2611 }, //?? { MODE_VIDEO_STD, 2612 },// Changed in SX210 { MODE_KIDS_PETS, 32786 },// Changed in SX210 { MODE_INDOOR, 32787 },// Changed in SX210
Quote from: Bernd R on 19 / October / 2011, 13:08:08My camera have only 1 long time exposure mode, i can select time from 1 sec to 15 secMaybe it is possible to detect in chdk the program mode, or if chdk use time overwrite or aperture overwrite and do in automatic modes the code i use for ixus 1000 if it can work on other camera too.this programs on my camera do time aperture, automatic depend on ISO. { MODE_AUTO, 32768 }, { MODE_P, 32772 }, { MODE_EASY, 33314 }, // Changed in SX210 { MODE_PORTRAIT, 32783 }, // Changed in SX210 { MODE_NIGHT_SNAPSHOT, 32781 }, // Changed in SX210 { MODE_LANDSCAPE, 32782 }, // Changed in SX210 { MODE_VIDEO_COLOR_ACCENT, 2610 }, //?? { MODE_VIDEO_COLOR_SWAP, 2611 }, //?? { MODE_VIDEO_STD, 2612 },// Changed in SX210 { MODE_KIDS_PETS, 32786 },// Changed in SX210 { MODE_INDOOR, 32787 },// Changed in SX210 Is this suggestion somehow related to your original post about CHDK ISO vs market ISO values and how CHDK sets ISO override after the camera has determine shutter speed and aperture settings ? Or is it something new ?
I understand this problem not really. For more than 75 cameras the ISO override function works fine, and for the Ixus1000 not?The CHDK overrides are functions without manual recalculation like in a manual mode. You can make a calculation in a script. There is a simple formula: Tv + Av = Bv + Sv. The APEX96 system is a good helper.msl
Started by Bernd R General Discussion and Assistance
Started by philmoz « 1 2 ... 7 8 » DryOS Development
Started by dougo3 General Discussion and Assistance
Started by rgleichman General Help and Assistance on using CHDK stable releases
Started by Caribou007 General Discussion and Assistance