 |
|
 |
|
Next: priority aperture & speed
|
| Author |
Message |
External

Since: Oct 04, 2005 Posts: 833
|
(Msg. 241) Posted: Tue Mar 20, 2007 10:08 pm
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: rec>photo>digital, others (more info?)
|
|
|
John Sheehy wrote:
> "Roger N. Clark (change username to rnclark)" <username RemoveThis @qwest.net> wrote
> in news:45FF8497.8020101@qwest.net:
>
>> John Sheehy wrote:
>>
>>> Quantization is just the act of converting analog data to digitized
>>> integers. If there is no added noise in the process, then any analog
>>> range of values equivalent to one ADU will wind up with that single
>>> ADU value. For systems where absolute values matter, this means
>>> errors over any one ADU range, like -0.999 to 0, or -0.5 to +0.499,
>>> or 0 to +0.999; never +/- 1 as Roger suggests in other posts.
>> Gee, some simple research would prove you are wrong.
>
> Gee, maybe you should read what I actually write.
Yeah, some the other way. I always discussed quantization
in terms of the ADC. ADCs are not perfect.
Fine, now I hope we are on the same page.
> If you google my posts in other forums, you will see that I have
> concluded that the flat rate of read noise at all Canon DSLR ISOs
> probably has something to do with the last stages, including the ADC.
Great, we agree, sort of! From the data I see, I conclude
most of the noise at the low ISOs is due to the ADC.
> I
> have not concluded, in along time, however, that it is because of the
> bit depth of the capture.
A better ADC will improve the noise at low ISO. That comes with
more bits (higher bit converters).
> It is easy to quantize data further, and see
> at what point on the quantization curve you are. The fact is, you have
> to quantize ISO 100 by about two bits, and ISO 1600 by about 3 bits,
> before you see more noise, due to the quantization.
This does not make sense.
>
>> Try reading http://en.wikipedia.org/wiki/Analog-to-digital_converter
>> which is a pretty good writ-up.
>> For example, note the statement:
>> "Commercial converters usually have ±0.5 to ±1.5 LSB error in their
>> output." (section on commercial analog-to-digital converters.
>
> If you had paid any attention to what I wrote, you would have seen that I
> wrote "If there is no added noise ...". IOW, I was clearly and
> deliberately taking the mathematical aspect of quantization into
> isolation. I mentioned also in some other spot that it was not 100%
> clear if you were talking about the mathematical act of quantization, or
> the total effect of the ADC, incuding the noise it introduces.
I was only talking about the ADC. That is all that matters in the
quantization step. IT IS ALL ABOUT ADC PERFORMANCE.
12-bit ADCs do not give perfect 12 bits quantization.
> In the past 24 hours, I have had three people on DPReview quote your work
> to me, to prove that the 14 bits in the mkIII will automatically increase
> DR by 2 stops, because current cameras are limited by 12-bit capture.
> had you made it clear that it isn't the bit-depth itself, but the noise
> inherent in real-world ADCs, people might be drawing more accurate
> conclusions.
That is your jump to conclusions. If you read what I actually wrote...
e.g. see the caption to Figure 4 at:
http://www.clarkvision.com/imagedetail/digital.sensor.performance.summary
which I wrote before the 1D mark II was announced:
Figure 4. Dynamic range of sensors. Many sensors are limited to
just under 12 photographic stops by the camera's 12-bit analog-to-digital
(A/D) converter. Look for future DSLRs to use 14 or 16 bit A/Ds.
> There is only going to be 2 more stops of DR if the
> blackframe noise drops to 1.3 14-bit ADUs (0.325 12-bit ADUs). The
> Imaging Resource mkIII had ISO read noises of 4.88 14-bit ADUs and
> greater (I get 7.91 in one file; this may have some kind of electrical
> interference; I have to look closer for patterns).
There won't be 2 stops of improvement with 14-bit ADC if the
Analog Devices ADCs are indicative of the ADC used by Canon.
Canon claims 1 stop of shadow improvement.
>> Let's look at some noise in ADUs from a wide range cameras:
>>
>> Camera Read Noise in ADU (or DN, or LSBs)
>> ISO: 50 100 200 400 800 1600
>> Canon 1DMII 1.2 1.3 1.4 1.7 2.5 4.8
>> Canon 5D 1.8 1.8 1.9 2.1 2.6 7.4
>> Canon 10D 1.4 2.0 3.9 6.4 13.
>
> Those 10D figures are way off. They are 1.9, 2.8, 4.9, 9.0, and 18.0.
> Perhaps your figures were taken from a blackpointed RAW blackframe.
Oh, so you've tested my canon 10D? I didn't see you in my house.
My numbers are correct for my camera.
> The 5D figure is very high for ISO 1600, also. The 5D ISO 1600
> blackframes I have here are all 4.6.
Perhaps there is some variation in cameras, or you are testing
at different temperatures. See reference 13 on my
digital.sensor.performance.summary web page for the 5D data.
>
>> Nikon D50 1.8 4.0
>> Nikon D200 1.3 2.0 3.8 7.4 15.
>
> I don't recall seeing values this low at the low ISOs in the Nikon RAW
> files I had. These are probably taken literally from the RAW blackframe,
> so they are automatically reduced to about 60% of what they'd be if they
> weren't black-clipped, like the Canons.
Well, perhaps you could examine the real data, e.g.:
http://www.clarkvision.com/imagedetail/evaluation-nikon-d200
I don't just do a dark frame measurement; I analyze the
noise and response over the entire range of the sensor and model
the results. See Figure 1 on the above web page. You'll see the
largest deviation from the model is less than 10%, and I have
light levels down to DN 16 (out of 4095). Where is your data
that proves this is wrong?
> You should pay more attention. I never said no noise came from the ADC
> stage or unit; I said the *bit depth* was not the problem.
You've been arguing that a 14-bit ADC would not help the low
ISO performance. Canon and I claim otherwise. Canon has stated
improved shadow noise with their 14-bit converter in the 1DIII.
Current data indicate low ISO cameras (Nikon and Canon) are limited by
12-bit ADCs.
> Let me state my viewpoint with a very clear example; if you quantize a
> 12-bit Canon DSLR ISO 100 to 11 bits, it will lose little DR, much closer
> to 0 stops than 1 stop.
>
> If the 1DmkIII actually had noise of 1.3 14-bit ADUs, and you quantized
> that RAW data to 11 bits, it would still have more DR at the pixel level
> than a 12-bit RAW from existing 12-bit Canons.
This does not make sense.
I think this thread has gone on long enough. Let's simply wait
a few months until 1DIIIs are in the hands of competent testers
and publish real evaluations of read noise and full well
capacities. I predict the read noise in the 1DIII at low iso
will improve by about a factor of 2 over the 1DII simply from
typical ADC specifications.
Oh, and one other prediction: we'll see more images being limited
by photoshop's 15-bit math.
Roger >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Mar 23, 2006 Posts: 300
|
(Msg. 242) Posted: Wed Mar 21, 2007 8:37 am
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Mar 21, 5:27 am, "Roger N. Clark (change username to rnclark)"
<usern....TakeThisOut@qwest.net> wrote:
> Paul Furman wrote:
> > Roger N. Clark (change username to rnclark) wrote:
> >> Let's look at some noise in ADUs from a wide range cameras:
>
> >> Camera Read Noise in ADU (or DN, or LSBs)
> >> ISO: 50 100 200 400 800 1600
> >> Canon 1DMII 1.2 1.3 1.4 1.7 2.5 4.8
> >> Canon 5D 1.8 1.8 1.9 2.1 2.6 7.4
> >> Canon 10D 1.4 2.0 3.9 6.4 13.
> >> Nikon D50 1.8 4.0
> >> Nikon D200 1.3 2.0 3.8 7.4 15.
> >> Canon 20D 2.0 2.2 2.4 3.2 4.5
> >> Canon S60 2.5
> >> Canon S70 2.0 3.4 6.3 17.
>
> > Is there a way to show the 'main' sensor noise in the same units
> > compared to this read noise?
>
> Yes, the ISO 1600 values are pretty close to the true read noise
> of the sensor. So for read noise in ADUs at ISO 100 divide the
> ISO 1600 values by 16. For example, the 1DMII with 4.8 ADUs at
> ISO 1600 should be about 4.8/16 = 0.3 ADU at ISO 100. That is why
> a converter with more bits should improve the low ISO shadow detail.
>
> > I think I understand that an AUD is the
>
> > smallest unit of info that can be read, right?
>
> Yes, ADU. I don't know where this ADU term came from. In the
> terrestrial and planetary sciences, we use DNs, and so do the
> engineers I've worked with on spacecraft sensors.
> DN = data number.
>
> > And these AUDs are
> > essentially rounding errors, not random noise? If so I would expect them
> > to follow a more consistent increas like:
>
> > 1.2 2.4 4.8 9.6 19.2 38.4
>
> The ADUs (DNs) are errors introduced by 1) sensor noise + 2) analog
> gain amplifier noise + 3) A/D converter noise and converter errors.
> It's not a straight line increase because one of those three dominates at
> one end and another dominates at the other end of the ISO.
> #1 and 2 are strongly coupled. 1+2 dominates at the high ISO,
> #3 dominates at the low ISO in the above sensors. We are all
If that's the case, wouldn't on chip binning improve this problem (ie
number 3) at low ISOs? on-chip I mean by reading off 4 (say) pixels at
a time. I know that in CCDs this is not so hard to do for 4 pixels in
a line, but I have no idea if it's equally easy for eg a 2x2 block; I
also don't know if this kind of binning them together introduces other
sources of noise (in which case on-chip binning wouldn't help beyond a
point), or how it works for a CMOS sensor. Do you have any pointers to
more information? >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Mar 23, 2006 Posts: 300
|
(Msg. 243) Posted: Wed Mar 21, 2007 3:19 pm
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Mar 22, 12:00 am, John Sheehy <J....TakeThisOut@no.komm> wrote:
> Dalsa claims to be doing this with a 28MP CCD; they actually read a 2x2
> block of pixels with the same CFA filter color, if I remember their
> whitepaper correctly. They claim the same read noise four the 4 binned
> pixels, in electrons, as a single pixel, giving a gain of a stop over 2x2
> binning in software or firmware.
Great thanks, I'll look for info on their website. >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Mar 23, 2006 Posts: 300
|
(Msg. 244) Posted: Wed Mar 21, 2007 5:52 pm
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Mar 21, 7:15 am, "Roger N. Clark (change username to rnclark)"
<usern....RemoveThis@qwest.net> wrote:
> John Sheehy wrote:
>
> >> Nikon D50 1.8 4.0
> >> Nikon D200 1.3 2.0 3.8 7.4 15.
>
> > I don't recall seeing values this low at the low ISOs in the Nikon RAW
> > files I had. These are probably taken literally from the RAW blackframe,
> > so they are automatically reduced to about 60% of what they'd be if they
> > weren't black-clipped, like the Canons.
>
> Well, perhaps you could examine the real data, e.g.:http://www.clarkvision.com/imagedetail/evaluation-nikon-d200
>
> I don't just do a dark frame measurement; I analyze the
> noise and response over the entire range of the sensor and model
> the results. See Figure 1 on the above web page. You'll see the
> largest deviation from the model is less than 10%, and I have
> light levels down to DN 16 (out of 4095). Where is your data
> that proves this is wrong?
But if indeed the signal is clipped to what would have been zero had
there been no noise, then this would start to be visible only when the
signal and the standard deviation are roughly equal (since if the
signal is higher, the noise doesn't reach zero so doesn't get
clipped).
This would be invisible on the scale of figure 1. But if I understand
correctly, you obtained the values for the read noise by measuring the
output s and the noise n and fitting the noise curve to
n(s)=sqrt(f^2+m) where m is the number of electrons and f the fixed
noise? [that is, you determine f from this]? In that case indeed your
value for f would be the true read noise, because the deviation from
the model caused by this clipping would be over a tiny range of values
to the extreme left of your plot and wouldn't affect the fitting
appreciably.
Anyway, my D200 does clip the noise at zero (ie the stdev is
abnormally low for very low signals). Not that this contradicts your
results or has any practical significance (that I can tell). >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Mar 07, 2007 Posts: 193
|
(Msg. 245) Posted: Wed Mar 21, 2007 5:56 pm
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"acl" <achilleaslazarides.TakeThisOut@yahoo.co.uk> wrote in
news:1174491465.985153.29720@l75g2000hse.googlegroups.com:
> If that's the case, wouldn't on chip binning improve this problem (ie
> number 3) at low ISOs? on-chip I mean by reading off 4 (say) pixels at
> a time. I know that in CCDs this is not so hard to do for 4 pixels in
> a line, but I have no idea if it's equally easy for eg a 2x2 block; I
> also don't know if this kind of binning them together introduces other
> sources of noise (in which case on-chip binning wouldn't help beyond a
> point), or how it works for a CMOS sensor. Do you have any pointers to
> more information?
Dalsa claims to be doing this with a 28MP CCD; they actually read a 2x2
block of pixels with the same CFA filter color, if I remember their
whitepaper correctly. They claim the same read noise four the 4 binned
pixels, in electrons, as a single pixel, giving a gain of a stop over 2x2
binning in software or firmware.
--
<>>< ><<> ><<> <>>< ><<> <>>< <>>< ><<>
John P Sheehy <JPS.TakeThisOut@no.komm>
><<> <>>< <>>< ><<> <>>< ><<> ><<> <>>< >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Mar 23, 2006 Posts: 300
|
(Msg. 246) Posted: Wed Mar 21, 2007 7:58 pm
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Mar 22, 6:39 am, "Roger N. Clark (change username to rnclark)"
<usern....TakeThisOut@qwest.net> wrote:
> acl wrote:
> > On Mar 21, 7:15 am, "Roger N. Clark (change username to rnclark)"
> > <usern....TakeThisOut@qwest.net> wrote:
> >> John Sheehy wrote:
>
> >>>> Nikon D50 1.8 4.0
> >>>> Nikon D200 1.3 2.0 3.8 7.4 15.
> >>> I don't recall seeing values this low at the low ISOs in the Nikon RAW
> >>> files I had. These are probably taken literally from the RAW blackframe,
> >>> so they are automatically reduced to about 60% of what they'd be if they
> >>> weren't black-clipped, like the Canons.
> >> Well, perhaps you could examine the real data, e.g.:http://www.clarkvision.com/imagedetail/evaluation-nikon-d200
>
> >> I don't just do a dark frame measurement; I analyze the
> >> noise and response over the entire range of the sensor and model
> >> the results. See Figure 1 on the above web page. You'll see the
> >> largest deviation from the model is less than 10%, and I have
> >> light levels down to DN 16 (out of 4095). Where is your data
> >> that proves this is wrong?
>
> > But if indeed the signal is clipped to what would have been zero had
> > there been no noise, then this would start to be visible only when the
> > signal and the standard deviation are roughly equal (since if the
> > signal is higher, the noise doesn't reach zero so doesn't get
> > clipped).
>
> > This would be invisible on the scale of figure 1. But if I understand
> > correctly, you obtained the values for the read noise by measuring the
> > output s and the noise n and fitting the noise curve to
> > n(s)=sqrt(f^2+m) where m is the number of electrons and f the fixed
> > noise? [that is, you determine f from this]? In that case indeed your
> > value for f would be the true read noise, because the deviation from
> > the model caused by this clipping would be over a tiny range of values
> > to the extreme left of your plot and wouldn't affect the fitting
> > appreciably.
>
> > Anyway, my D200 does clip the noise at zero (ie the stdev is
> > abnormally low for very low signals). Not that this contradicts your
> > results or has any practical significance (that I can tell).
>
> I use the following noise model:
>
> N = (P + r^2 + t^2)^(0.5),
>
> Where N = total noise in electrons, P = number of photons,
> r = read noise in electrons, and
> t = thermal noise in electrons (effectively zero for short exposures).
> Noise from a stream of photons, the light we all see and image
> with our cameras, is the square root of the number of photons,
> so that is why the P in equation 2 is not squared (sqrt(P)2 = P).
>
> I track the signal and noise as a function of intensity, and watch for
> deviations from the model. Deviations indicate other noise sources
> are present, or other issues in the testing, or the camera and its
> processing. At low signals, if the read noise was clipped significantly,
> it would become obvious in the data as it would not fit well, showing
> a change in read noise as a function of intensity.
>
What I mean is this. As you say in your webpage
http://www.clarkvision.com/imagedetail/evaluation-nikon-d200/
the read noise at ISO 100 corresponds to about 1 DN; 10 electrons. So
unless the signal itself is of the order of 10 electrons, almost no
clipping will occur. In other words, we're talking about a deviation
from the noise model you have when you are at 1 DN or thereabouts,
which basically means no deviation. This would be completely invisible
on the graph and missed by any fitting procedure I know of (and
rightly so).
Another way to put it: this thing would occur when s\approx n, with s
the number of electrons and n the "noise electrons". This could not
possibly affect the fitting unless you only include a very small range
of data, nor would it be visible unless you specifically looked for it
(or noticed it by chance).
Now it may be that what I saw in my blackframes is because of the way
dcraw outputs "raw" data; maybe it subtracts an offset. I don't know,
and this effect, whatever is causing it, is so inconsequential that I
did not try to find out.
But all this has made me doubt myself, so I'll take some blackframes
and check again. I'll try to find and use a program not based on dcraw
to read the raw files (if such a thing exists). >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Oct 04, 2005 Posts: 833
|
(Msg. 247) Posted: Wed Mar 21, 2007 8:39 pm
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
acl wrote:
> On Mar 21, 7:15 am, "Roger N. Clark (change username to rnclark)"
> <usern....RemoveThis@qwest.net> wrote:
>> John Sheehy wrote:
>>
>>>> Nikon D50 1.8 4.0
>>>> Nikon D200 1.3 2.0 3.8 7.4 15.
>>> I don't recall seeing values this low at the low ISOs in the Nikon RAW
>>> files I had. These are probably taken literally from the RAW blackframe,
>>> so they are automatically reduced to about 60% of what they'd be if they
>>> weren't black-clipped, like the Canons.
>> Well, perhaps you could examine the real data, e.g.:http://www.clarkvision.com/imagedetail/evaluation-nikon-d200
>>
>> I don't just do a dark frame measurement; I analyze the
>> noise and response over the entire range of the sensor and model
>> the results. See Figure 1 on the above web page. You'll see the
>> largest deviation from the model is less than 10%, and I have
>> light levels down to DN 16 (out of 4095). Where is your data
>> that proves this is wrong?
>
> But if indeed the signal is clipped to what would have been zero had
> there been no noise, then this would start to be visible only when the
> signal and the standard deviation are roughly equal (since if the
> signal is higher, the noise doesn't reach zero so doesn't get
> clipped).
>
> This would be invisible on the scale of figure 1. But if I understand
> correctly, you obtained the values for the read noise by measuring the
> output s and the noise n and fitting the noise curve to
> n(s)=sqrt(f^2+m) where m is the number of electrons and f the fixed
> noise? [that is, you determine f from this]? In that case indeed your
> value for f would be the true read noise, because the deviation from
> the model caused by this clipping would be over a tiny range of values
> to the extreme left of your plot and wouldn't affect the fitting
> appreciably.
>
> Anyway, my D200 does clip the noise at zero (ie the stdev is
> abnormally low for very low signals). Not that this contradicts your
> results or has any practical significance (that I can tell).
I use the following noise model:
N = (P + r^2 + t^2)^(0.5),
Where N = total noise in electrons, P = number of photons,
r = read noise in electrons, and
t = thermal noise in electrons (effectively zero for short exposures).
Noise from a stream of photons, the light we all see and image
with our cameras, is the square root of the number of photons,
so that is why the P in equation 2 is not squared (sqrt(P)2 = P).
I track the signal and noise as a function of intensity, and watch for
deviations from the model. Deviations indicate other noise sources
are present, or other issues in the testing, or the camera and its
processing. At low signals, if the read noise was clipped significantly,
it would become obvious in the data as it would not fit well, showing
a change in read noise as a function of intensity.
Details are given here:
Procedures for Evaluating Digital Camera
Sensor Noise, Dynamic Range, and Full Well Capacities;
Canon 1D Mark II Analysis
http://www.clarkvision.com/imagedetail/evaluation-1d2
Roger >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Mar 23, 2006 Posts: 300
|
(Msg. 248) Posted: Wed Mar 21, 2007 8:50 pm
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Mar 22, 7:22 am, "Roger N. Clark (change username to rnclark)"
<usern... RemoveThis @qwest.net> wrote:
> acl wrote:
> > What I mean is this. As you say in your webpage
> >http://www.clarkvision.com/imagedetail/evaluation-nikon-d200/
> > the read noise at ISO 100 corresponds to about 1 DN; 10 electrons.
>
> Remember, a standard deviation of 1 means peak to peak variations on about
> 4 DN. It is not simply you get 1 and only 1 all the time.
>
I've written papers on stochastic processes, and I know perfectly well
what a standard deviation is; the point is that if this thing occurs,
it is confined to extremely low signals. Maybe I should have replaced
"when s=n" by "when the signal is of the order of the noise", to
prevent this. Anyway, not much point in talking about this, as I think
it's gotten to the point where everybody is talking past each other
and we're just creating noise ourselves [which by now exceeds the
signal, methinks  ]. I'll take some blackframes tomorrow and check
again.
> There is another issue with the Nikon raw data: it is not true raw, but
> depleted values. I think they did a good job in designing the
> decimation, as they made it below the photon noise.
The D200 (and more expensive models) have an option to save
uncompressed raw data. And yes, the resolution loss is indeed below
the shot noise (using your measured values for the well depth).
Although I guess it's now my turn to point out that this noise
obviously isn't always sqrt(n) so shot noise can exceed the resolution
limit (eg for a uniform subject it could be that you get zero photons
in one pixel and 80000 in the other; not terribly likely, though), but
never mind.
But keep in mind that Nikons do process their "raw" data. I once wrote
a short program to count the number of pixels above a given threshold
in the data dumped by dcraw. I ran it on some blackframes. For a given
threshold, the number of these pixels increases as the exposure time
increases, up to an exposure time of 1s. At and above 1s, the number
drops immediately to zero for thresholds of x and above (I don't
remember what x was for ISO 800), except for a hot pixel which stays
there. So obviously some filtering is done starting at 1s (maybe
they're mapped, I don't know).
It also looks to me (by eye) like more filtering is done at long
exposure times, but I have not done any systematic testing. Maybe
looking for correlations in the noise (in blackframes, for instance)
will show something, but if I am going to get off my butt and do so
much work I might as well do something publishable, so it won't be
this
Well, plus I am rubbish at programming and extremely lazy. >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Oct 04, 2005 Posts: 833
|
(Msg. 249) Posted: Wed Mar 21, 2007 9:17 pm
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
John Sheehy wrote:
> "Roger N. Clark (change username to rnclark)" <username.RemoveThis@qwest.net> wrote
> in news:45FE0C82.5010703@qwest.net:
>
>> John Sheehy wrote:
>>
>>> The Panasonic FZ50 collects as many photons at ISO 100 saturation,
>>> per unit of sensor area, as the 1DmkII. This is a real-world fact,
>>> that shows that your concern is pretty much a boogey-man story, in
>>> the range of current pixel sizes. And, even when miniaturization of
>>> the sensel *does* lead to photon loss per unit of area, it takes a
>>> huge difference in photon collection to make a difference in shot
>>> noise. Shot noise is not proportional to signal; it's proportional
>>> to its square root.
>> There is a simple reason for this "real-world fact."
>> The 1D Mark II is a CMOS sensor; CMOS sensors have lower fill
>> factors than CCDs. The FZ50 is a CCD, which generally have
>> larger fill factors.
>
> This I know.
>
>> You are comparing apples and
>> oranges.
>
> I am not "comparing" in the context you suggest. I am simply trying to
> demonstrate the fact that small pixels are not necessarily the bad thing
> they are made out to be by big pixel fanatics. Maybe you're not
> concerned, but I get very concerned about false information circulating
> as fact, or half-truths taken out of context like an evangelist quoting
> scripture for his own gain. There is a growing cult of people who
> believe that small pixels can not give good image quality, and your work
> is the most often-quoted Bible.
Me too!
>> The on pixel support electronics is why
>> there are no small pixel size CMOS sensors, because once
>> pixel size drops below about 4 microns, the active area
>> drops too much. CCD encounter similar problems around
>> 2 microns, only due to the inactive area between pixels.
>
> You don't need all of the amplification levels, though. If the pixel
> pitch halves to 4u, you can eliminate the ISO 100- and ISO 200-related
> circuit components.
This makes NO sense. As pixel size and active area drops,
the unity gain ISO drops. You don't need ISOs above unity gain ISO,
so it is the high ISOs that are not needed. The low ISOs give
you the full well range of the sensor. Dropping those low ISOs and
you just lose dynamic range, which you've already reduced by
using a smaller pixel..
> When you go smaller yet, there may be no more
> benefit in Canon's current technology at all. What if you could read 2u
> pixels with 4800 photons each with a single amplification with only 1.5
> electrons of read noise; what would be the point in having bigger pixels,
> especially if you had the option of the firmware downsampling or binning
> for you, if you didn't want all that data?
The problem with this scenario are multiple:
1) reduced dynamic range.
2) you want many more pixels, so the readout is slower and you lose
frames per second. You lose with fast action photography.
3) you lose high ISO performance.
> My main concern is that companies don't want to be bothered with higher
> pixel densities in DSLRs, and big-pixel fanaticism is exactly what they
> want people to believe, so that they don't have to move in the right
> direction for maximum IQ, or niche products.
Image quality is more than just megapixels. Signal-to-noise ratio
is very important, and that is what you are sacrificing with
smaller pixels. However, the one thing you have not thought
that does change the equation is QE. If QE could be increased
along with maintaining full well with smaller pixels, then
we would have a winner. See below.
> AFAIAC, there are huge gaps
> in current offerings. Where is the camera that takes EOS lenses that has
> a small sensor like the one in the FZ50? Imagine an FZ50 sensor
> capturing the focal plane of a 500mm or 600mm f/4L IS!
No, it would not be very good. See below.
> Imagine a more
> professional version with lower read noise. No bokeh-destroying TCs
> necessary; you can leave them home and get as much or better detail, with
> better bokeh.
The factors in image quality include resolution, and signal-to-noise ratio.
To get that wonderful quality with current QE and full wells gives
the sweet spot of about 6 to 8 microns. And that sweet spot also corresponds
to the sweet spot in 35mm camera lenses. WE ARE AT THE SWEET SPOT TODAY!
If you changed DSLR sensors to 4 microns, to give good image quality,
you would need to maintain full wells, increase QE by 3x (basically
to max: >90% QE), and improve all the lenses by about 2x in MTF
response. While all of this might happen, and I hope it does,
there are no indications of sensors that meet that criteria, and
lens designs for that improved MTF would not be cheap.
Its nice to dream of the future, but don't forget we have wonderful
performance right now. I imagine a 30D class full frame sensor,
about 22 megapixels, 5 frames per second.
That should come out soon.
Roger >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Oct 04, 2005 Posts: 833
|
(Msg. 250) Posted: Wed Mar 21, 2007 9:22 pm
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
acl wrote:
> What I mean is this. As you say in your webpage
> http://www.clarkvision.com/imagedetail/evaluation-nikon-d200/
> the read noise at ISO 100 corresponds to about 1 DN; 10 electrons.
Remember, a standard deviation of 1 means peak to peak variations on about
4 DN. It is not simply you get 1 and only 1 all the time.
There is another issue with the Nikon raw data: it is not true raw, but
depleted values. I think they did a good job in designing the
decimation, as they made it below the photon noise.
Roger >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Mar 07, 2007 Posts: 193
|
(Msg. 251) Posted: Thu Mar 22, 2007 12:06 am
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"Roger N. Clark (change username to rnclark)" <username.TakeThisOut@qwest.net> wrote
in news:4600A9A2.6020506@qwest.net:
> Here is a demo: See figure 9 at:
> http://www.clarkvision.com/photoinfo/night.and.low.light.photography
> Here is the original raw data converted linearly in IP, scaled by 128:
> http://www.clarkvision.com/photoinfo/night.and.low.light.photography/ni
> ghtscene_linear_JZ3F7340_times128-876px.jpg
> Now here is the same data with the bottom 4 bits truncated:
> http://www.clarkvision.com/photoinfo/night.and.low.light.photography/ni
> ghtscene_linear_JZ3F7340-lose-4bits_times128-876px.jpg
> You lose quite a bit in my opinion.
> It would be a disaster in astrophotography.
*You* do. I never have the blackpoint drift up like that when I
truncate/quantize data; the effect is usually subtle. The overall
intensity should remain almost the same. You are doing something wrong,
I think.
Part of the problem might be that you are using tools that hide what
they're really doing from you. I see references to "linear conversions"
in your texts. You should do all the steps yourself, under your control,
so you know *exactly* what is happening to the data at every step of the
way. IRIS, DCRAW with the "-D" parameter are the only, and loading the
RAW images from un-compressed DNGs are the only ways I know of that get
you the real RAW data. (MaximDL, as well, I think).
Note, I didn't say that an ISO 1600 suffers nothing at all from 8-bit
quantization; I said that it is still better than ISO 100, pushed to the
same EI.
--
<>>< ><<> ><<> <>>< ><<> <>>< <>>< ><<>
John P Sheehy <JPS.TakeThisOut@no.komm>
><<> <>>< <>>< ><<> <>>< ><<> ><<> <>>< >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Oct 04, 2005 Posts: 833
|
(Msg. 252) Posted: Thu Mar 22, 2007 12:06 am
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
John Sheehy wrote:
> "Roger N. Clark (change username to rnclark)" <username.TakeThisOut@qwest.net> wrote
> in news:4600A9A2.6020506@qwest.net:
>
>> Here is a demo: See figure 9 at:
>> http://www.clarkvision.com/photoinfo/night.and.low.light.photography
>
>> Here is the original raw data converted linearly in IP, scaled by 128:
>> http://www.clarkvision.com/photoinfo/night.and.low.light.photography/ni
>> ghtscene_linear_JZ3F7340_times128-876px.jpg
>
>> Now here is the same data with the bottom 4 bits truncated:
>> http://www.clarkvision.com/photoinfo/night.and.low.light.photography/ni
>> ghtscene_linear_JZ3F7340-lose-4bits_times128-876px.jpg
>
>> You lose quite a bit in my opinion.
>> It would be a disaster in astrophotography.
>
> *You* do. I never have the blackpoint drift up like that when I
> truncate/quantize data; the effect is usually subtle. The overall
> intensity should remain almost the same. You are doing something wrong,
> I think.
>
> Part of the problem might be that you are using tools that hide what
> they're really doing from you. I see references to "linear conversions"
> in your texts. You should do all the steps yourself, under your control,
> so you know *exactly* what is happening to the data at every step of the
> way. IRIS, DCRAW with the "-D" parameter are the only, and loading the
> RAW images from un-compressed DNGs are the only ways I know of that get
> you the real RAW data. (MaximDL, as well, I think).
>
> Note, I didn't say that an ISO 1600 suffers nothing at all from 8-bit
> quantization; I said that it is still better than ISO 100, pushed to the
> same EI.
>
Well, lets look at this another way. Go to:
http://www.clarkvision.com/imagedetail/dynamicrange2
4 bits is DN = 16 in the 0 to 4092 range. In 16-bit
data file, that would be 16*16 = 256.
Now go to Figure 7 and draw a vertical line at 256 on the
horizontal axis. Now note all the data below that line that
you cut off. Now go to Figure 8b and draw a vertical line
at 4 stops, and note all the data you cut off. Now go to
Figure 9D and draw the vertical line at 256 and
note all the data you cut off. (Note too how noisy the
8-bit jpeg data are.)
Pretty obvious.
Roger >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Mar 07, 2007 Posts: 193
|
(Msg. 253) Posted: Thu Mar 22, 2007 1:24 am
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"acl" <achilleaslazarides RemoveThis @yahoo.co.uk> wrote in
news:1174524772.426623.293260@l77g2000hsb.googlegroups.com:
> This would be invisible on the scale of figure 1. But if I understand
> correctly, you obtained the values for the read noise by measuring the
> output s and the noise n and fitting the noise curve to
> n(s)=sqrt(f^2+m) where m is the number of electrons and f the fixed
> noise? [that is, you determine f from this]? In that case indeed your
> value for f would be the true read noise,
Not necessarily. Many cameras have fairly significant noise that is
neither in the blackframe, nor is shot noise. There are basically three
components I've seen; the fixed, blanket noise (blackframe noise), the shot
noise, and noise that is directly proportional to signal. If the latter
type is significant, the camera will fail to reach the maximum S/N dictated
by the photon count. My XTi is certainly like this; the top 1.5 stops or
so at ISO 100 has the same S/N; about 100:1. Failure to account for it
leads to an estimation of lower photon count than the actual. When I
measure shot noise in low-ISO highlights, I divide signal in DN by standard
deviation in DN, of a completely OOF patch of a solid area with no texture
and shadows (like the color checker squares) in a single color channel of
the RAW data (treating green as two different, but similar, channels), and
square the result of the division. I consider this number to be the
*minimum* number of photons; not *the* number.
There may be some other noise correlations as well, which I have not
noticed yet (albeit low in intensity).
--
<>>< ><<> ><<> <>>< ><<> <>>< <>>< ><<>
John P Sheehy <JPS RemoveThis @no.komm>
><<> <>>< <>>< ><<> <>>< ><<> ><<> <>>< >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Oct 04, 2005 Posts: 833
|
(Msg. 254) Posted: Thu Mar 22, 2007 1:24 am
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
John Sheehy wrote:
> "acl" <achilleaslazarides.TakeThisOut@yahoo.co.uk> wrote in
> news:1174524772.426623.293260@l77g2000hsb.googlegroups.com:
>
>> This would be invisible on the scale of figure 1. But if I understand
>> correctly, you obtained the values for the read noise by measuring the
>> output s and the noise n and fitting the noise curve to
>> n(s)=sqrt(f^2+m) where m is the number of electrons and f the fixed
>> noise? [that is, you determine f from this]? In that case indeed your
>> value for f would be the true read noise,
>
> Not necessarily. Many cameras have fairly significant noise that is
> neither in the blackframe, nor is shot noise. There are basically three
> components I've seen; the fixed, blanket noise (blackframe noise), the shot
> noise, and noise that is directly proportional to signal. If the latter
> type is significant, the camera will fail to reach the maximum S/N dictated
> by the photon count. My XTi is certainly like this; the top 1.5 stops or
> so at ISO 100 has the same S/N; about 100:1. Failure to account for it
> leads to an estimation of lower photon count than the actual. When I
> measure shot noise in low-ISO highlights, I divide signal in DN by standard
> deviation in DN, of a completely OOF patch of a solid area with no texture
> and shadows (like the color checker squares) in a single color channel of
> the RAW data (treating green as two different, but similar, channels), and
> square the result of the division. I consider this number to be the
> *minimum* number of photons; not *the* number.
>
> There may be some other noise correlations as well, which I have not
> noticed yet (albeit low in intensity).
You are limiting the signal-to-noise ratio your derive because of
variations in the target you are imaging. E.g. the macbeth color
checker of make of paper, which has fine textures. Illuminate
the chart at a low angle and this will become more obvious.
Those small variations in the target translate to small
variations in intensity from pixel to pixel and result
in your lower S/N. I initially tried to do this too in order
to speed up testing, but hit this problem. I've encountered
this problem at work in testing sensors too (more difficult
when you are trying to evaluate sensors in flight on aircraft
and spacecraft). I have found the only reliable way is
the method used by the sensor manufacturers which uses
pairs of full field illumination. That method also avoids
scattered light which can also influence the lowest signal
measurements which impact correct dynamic range evaluations.
Details are available on my website and references therein:
Procedures for Evaluating Digital Camera
Sensor Noise, Dynamic Range, and Full Well Capacities;
Canon 1D Mark II Analysis
http://www.clarkvision.com/imagedetail/evaluation-1d2
Roger >> Stay informed about: low light |
|
| Back to top |
|
 |  |
External

Since: Mar 07, 2007 Posts: 193
|
(Msg. 255) Posted: Thu Mar 22, 2007 2:00 am
Post subject: Re: low light [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"Roger N. Clark (change username to rnclark)" <username DeleteThis @qwest.net> wrote
in news:4600B417.9010205@qwest.net:
> The ADUs (DNs) are errors introduced by 1) sensor noise + 2) analog
> gain amplifier noise + 3) A/D converter noise and converter errors.
> It's not a straight line increase because one of those three dominates
> at one end and another dominates at the other end of the ISO.
> #1 and 2 are strongly coupled. 1+2 dominates at the high ISO,
> #3 dominates at the low ISO in the above sensors. We are all
> hoping that #3 will be less in the new canon 1DMIII with the
> 14-bit converter. And Canon says that is the case.
> I hope they are right.
Here's the shadow area of a 1DmkIII ISO 100 RAW, at the original 14 bits,
and at quantizations to 12, 11, and 10 bits:
http://www.pbase.com/jps_photo/image/76001165
The demoasicing is a bit rough; it's my own quick'n'dirty one, but it is
applied homogenously to all quantization levels, and I gave the three with
extra quantization the same bit depth for demosaicing as the 14-bit (they
all have the same precision for processing). Gave them all a little USM
(0.5px/120%), which emphasizes the noise a little. These are all pushed
from ISO 100 to 3200; the full tonal range of these images is linear, and
represents the lowest 256 photonic levels (1024 through 1279) of the 15,280
usable levels of the ISO 100 RAW.
--
<>>< ><<> ><<> <>>< ><<> <>>< <>>< ><<>
John P Sheehy <JPS DeleteThis @no.komm>
><<> <>>< <>>< ><<> <>>< ><<> ><<> <>>< >> Stay informed about: low light |
|
| Back to top |
|
 |  |
| Related Topics: | More creative use of light - Following up on the last issue we're taking a look at "The Direction of Light" and how we can use it to create better photographs. You can view the latest issue of CreativePhoto by going to www.blairhoward.com/sample.html.
Best low light compact - I will be travelling in Europe and need to take photos inside relatively dark historical buildings, churches and museums. I prefer to use flash as little as possible, and in some cases it is forbidden. Yes, I will use a tripod, where required Can anyone...
Light metering - Hello there, I waw wondering how camera is actually doing light metering and adjusting proper exposure. In TTL metering light from the scene will be entering the camera through the lens. Once the light hit the light meter (or metering points/area) ,it..
Which is better; too light or too dark? - Is it better for a photo to be too light or too dark for subsequent retouching in Photoshop?
casio low light photography - I'm new to photography and have just bought a Casio Exilim EX Z750 for learning. I'm interested in improving my photos in low light situations. The flash on this camera is not particularly strong and it has no features for attaching an external flash. I.... |
|
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|
 |
|
|