A720 IS and its overexposure-behaviour

Jucifer

251
[A710IS]

Re: A720 IS and its overexposure-behaviour

« Reply #40 on: 20 / July / 2008, 05:36:40 »

Advertisements

« Last Edit: 20 / July / 2008, 06:46:11 by Jucifer »

Logged

forum search // google // autobuilds

viewpix

23

Re: A720 IS and its overexposure-behaviour

« Reply #41 on: 20 / July / 2008, 05:48:07 »

Ah, cool!
May a hint for you: with custom curves - > syscurves.CVF my picture becomes blue-saturated. Bug or feature?

Logged

Jucifer

251
[A710IS]

Re: A720 IS and its overexposure-behaviour

« Reply #42 on: 20 / July / 2008, 07:17:06 »

syscurves.cvf is normally not used as other curves (but with/as EV correction), and has a dedicated function (in curves.c).
So I think it's a feature. :]

Logged

forum search // google // autobuilds

viewpix

23

Re: A720 IS and its overexposure-behaviour

« Reply #43 on: 20 / July / 2008, 07:53:44 »

Logged

Jucifer

251
[A710IS]

Re: A720 IS and its overexposure-behaviour

« Reply #44 on: 20 / July / 2008, 09:02:58 »

Quote from: toinech on 12 / July / 2008, 18:01:05

Just need to set the curve mode to "Auto DR" use the standard EV comp feature by looking at the Zebra. The system will apply the proper amplification to the shadow based on the EV comp.

If you set Auto DR but use no exposure compensation (or use EV+), the curve won't be applied.

Logged

forum search // google // autobuilds

LjL

266
A720IS

Re: A720 IS and its overexposure-behaviour

« Reply #45 on: 20 / July / 2008, 12:19:41 »

You want the highlights to tone down, and stop getting blown out, so you need a shorter exposure, so you need negative compensation.

Then you need to apply a curve in order to stop the shadows from flattening out (or reverse the over-aggressive curve the A720 applies, if that's the case), and that's what Auto DR does automatically, in my understanding.

As for noise - expect some.

Logged

viewpix

23

Re: A720 IS and its overexposure-behaviour

« Reply #46 on: 20 / July / 2008, 12:39:03 »

Logged

LjL

266
A720IS

Re: A720 IS and its overexposure-behaviour

« Reply #47 on: 20 / July / 2008, 16:27:19 »

Document a feature that was born weeks ago? Perhaps you're asking for a bit too much

Besides, I haven't used it, you have

The wiki is there for everyone to edit!

Logged

viewpix

23

Re: A720 IS and its overexposure-behaviour

« Reply #48 on: 21 / July / 2008, 05:44:59 »

Back again from testing. Got the feature working right now.

Conclusion: curve-feature helps a little bit (for me the "+2EV"-setting brought best results) but - of course - the pix becomes very noisy. So you have to decide wether living with overexposured or noisy pix.

Well, i think the day where i will buy a DSLR is coming closer and closer...;-)

« Last Edit: 21 / July / 2008, 05:51:08 by viewpix »

Logged

hiker_jon

284

Re: A720 IS and its overexposure-behaviour

« Reply #49 on: 22 / July / 2008, 00:54:04 »

Hi,
I've been away and so couldn't respond to your post right away.

RGB space is NOT linear. The sensor space is. "Linear" means that the response of the sensor is proportional to the intensity of the light that falls on it. A conversion is applied between the sensor data and RGB colorspace during development of the raw data. The conversion uses a gamma of about .45 which is close to a square root (.5). I.e. RGB = sensor ** gamma.

This conversion magnifies the noise in the dark areas. You can see this in many ways.

First calculus shows that
dy = dx * gamma * 1/(x**(gamma-1))
Since 1/(x**(gamma-1)) is a decreasing function of x the output noise will decrease as x increases.

Second my example shows that the first half of the sensor range is mapped into the RGB range of 0 to .707. So noise of a certain intensity gets magnified inside of that range compared with the same size noise in the second half, which gets mapped to .707 to 1.

Jon

Quote from: LjL on 03 / July / 2008, 09:29:40

Quote from: hiker_jon on 02 / July / 2008, 16:56:47
I'm not sure of this, but Canon may deliberately overexpose their images a little on P&S cameras.

That's quite possible.

There is one thing, though... viewpix is saying that if less exposure is forced, the result is underexposed.
So it seems he just can't attain correct exposure.

That might mean that the picture itself is taken at the correct exposure, but that the JPEG processing "fakes" overexposure by mapping bright tones to white -- or alternatively, that the picture is indeed overexposed, but then the dark tones are darkened even more during JPEG processing.

This is not dissimilar from what you say below.

Quote
Have you heard of "shooting right"? The camera sensors collect data in linear space then a non-linear mapping (like a square root) is applied to go to RGB space.

Just a little nitpick... I believe that an "RGB space" may very well be linear; it's just that the gamma function used is not.
And that would be because monitors and printed are generally non-linear (1.8 to 2.5 gamma in sRGB), and common (though debated) practice is doing the gamma adjustments in the picture itself rather than in the picture viewer or operating system.

Quote
Because of this non-linearity there is more information in the bright parts of the image than in the dark parts. So overexposing a little can help to reduce noise in dark areas.

You mean more information squashed in the bright parts, don't you? (See below...)

But there is more! A CCD sensor has a certain amount of noise (roughly the one captured by a dark frame) that doesn't depend on pixel brightness.
That means (or at least may mean, but I believe that to be the case) that the noise part, when considered as a percentage of the total pixel brightness, is higher in the darker pixels!

Why would we treat noise as a percentage of brightness? Well, because our eye sees it that way. Given a fixed absolute amount of noise, it'll be more noticeable on dark areas than bright ones.

From this follows that if you want some visible detail in the dark areas, you'll have to expose them longer than to obtain the same amount of visible detail in the bright areas, I think.

This might be what the Canon software is trying to achieve. Note that it's perhaps a mistake to think "the photo is overexposed and NOT underexposed" just because bright areas are totally white, while the dark areas are NOT totally black.
Even if they're not totally black, what you see may be 100% noise (or close enough to the noise threshold anyway), so, effectively, they'd be underexposed.
And that's a picture that, for practical purposes, is both over and underexposed.

Quote
To see this consider that the square root of .5 is .707. So half of the dynamic range of the sensor (0 to .5) is mapped to 0 to .707 and the other half goes from .707 to 1.

This would mean giving the dark areas more detail, right? (And this is indeed much like the typical gamma correction function, as far as I know).

So you end up with wasted bits (all noise) in the dark tones, and with possibly too few bits left to encode bright tones (although this might be good, since our eyes are more demanding with the dark tones).
That's why I said "squashing" information before.

So again if you want to actually fill up the dark bits with information, you expose for longer.

My conclusion would be that if you just want to have the full sensor information with no surprise, you need the full 10 or 16 bits contained in the RAW (and encoded linearily). Then apply (or don't) your own gamma correction as desired.

Otherwise, playing with the "Contrast" setting in "My colors" might (or might not) result in changing the JPEG curves to give you more bits for the bright tones (and then step exposure down as needed when shooting).

Or still, you could use the CHDK build (which I believe exists) that lets you apply custom curves during RAW to JPEG conversation, which should be equivalent to - but maybe speedier than - doing RAW post-processing on a computer.

Logged