Bayer close to limit, Foveon just started?

Excuses, excuses.

Foveon failed to properly reproduce the very thing you say it's good at, red/blue charts.
Since it "failed" in a way that was spectacularily better than the 10MP challenger, then I guess you'd refer to the Bayer sensor as an Uber Failure

Your definition, not mine. I would have said it did OK.
But that image brings up an opportunity to present a 10MP shot from a Bayer camera ( the D60 ) of the same target (200 upsampling again):
Big deal. So neither one can properly reproduce a red/blue chart.
Actually the Sigma did just fine, because at 100% you could tell the chart was blue and red despite some purple intermingling. The Bayer sensor failed to resolve it was fully a series of curves. Obviously the Sigma produced the result that was photographically more correct since it represented reality.
How often do you take photos of red/blue charts anyway? More often than you photograph that wall with varying red tones?
I take pictures of red leaves on blue sky all the time in the fall. Do you stall indoors all fall? How sad.
Bayer handles real world subjects very well, as millions of photos prove.
And millions more prove that Foveon handles them even better.

--
---> Kendall
http://InsideAperture.com
http://www.pbase.com/kgelner
http://www.pbase.com/sigmadslr/user_home
 
Well, you're Sigma apparently works in a different manner than the one DPReview tested. As for highlight retention, check the D3000 review for instance. They got around 2 stops.
just general observations

more bit depth will give better roll off and tonality and make the unblown parts more interesting, perhaps disguising to an extent blown parts. Fully blown clouds become uninteresting rather like this one of yours with that rather cr@p blue canon produces

i guess that covers it ;)

--
Riley

any similarity to persons living or dead is coincidental and unintended
 
But look at the figures for other cameras. What else has 4.5 stops of highlight? Its often as low as 2.5
JPEG--------: Shadows -4.6 EV Highlights 3.8 EV Total 8.4 EV
ACR Default Shadows -3.6 EV Highlights 3.5 EV Total 7.1 EV
ACR 'Best'-: Shadows -6.0 EV Highlights 4.5 EV Total 10.5 EV

That's 1.5EVs more in the shadows than the highlights. You get 0.7 in the highlights but 1.4 more in the shadows with RAW compared to JPEG. That means that if you've blown highlights, then they're likely beyond repair.
DPreview seem to say the opposite. Foveon sensors have a good range above middle grey but are poor in the shadows. That is what you would expect from noisy sensors. The Foveon seems to have pretty good dynamic range but not mind blowing as some seem to suggest. Those shadows do remain the achilles heel. Perhaps the new sensor will offer better noise control without affecting the higher end response. I hope so.

As far as the original question is concerned, overexposure blows out skies just the same as any other sensor. I'm sloppy with exposure and tend to bracket when in doubt but I have loads of examples of blown highlights from the DP1 and SD9.
I'd say they're exceptionally good at exposure. Even Kendall, who I've never seen post a single negative comment about Foveon sensors, said that the strength of the Foveon sensor is in shadow-preservation, not highlight-retention. This can also be seen from the DPreview measurements, where the shadow-latitude is much bigger than the highlight-headroom. They were actually only able to retain 0.7EV highlights over JPG in RAW.

From these measurements you can also see that the DR-performance is average.
i see that

but if you get a chance to look at more foveon images, they consistently show clouds with good detail, no part of them blown. Now either these guys are exceptionally good at exposure (which, no offence seems kinda unlikely in a consistent way), or there is something else going on here
--
Galleries and website: http://www.whisperingcat.co.uk/default.shtml
--
Galleries and website: http://www.whisperingcat.co.uk/default.shtml
 
well i dont have a sigma but hey..

--
Riley

any similarity to persons living or dead is coincidental and unintended
 
Im just saying there has to be a reason
Well, the first question would have to be how accurate is your observation in the first place. Is it really the case that Foveon sensors are less prone to blowing the highlights. When making that kind of statement a few comparative examples are good.
just general observations
yeah, well, general observations need a bit of evidence behind them.
so what is it, the bit depth or what?
The bit depth won'y make any difference to whether highlights blow or not.
more bit depth will give better roll off and tonality
no it won't so long as there's enough bits to cover the DR of the sensor plus read electronics, more bit depth makes no difference at all.
and make the unblown parts more interesting, perhaps disguising to an extent blown parts. Fully blown clouds become uninteresting rather like this one of yours with that rather cr@p blue canon produces



i guess that covers it ;)
Not really fair to blame Canon for my PP and treatment of the image.
--
Bob
 
The D3000 has 5.7 for instance, and it's using a old CCD sensor.
But look at the figures for other cameras. What else has 4.5 stops of highlight? Its often as low as 2.5
JPEG--------: Shadows -4.6 EV Highlights 3.8 EV Total 8.4 EV
ACR Default Shadows -3.6 EV Highlights 3.5 EV Total 7.1 EV
ACR 'Best'-: Shadows -6.0 EV Highlights 4.5 EV Total 10.5 EV

That's 1.5EVs more in the shadows than the highlights. You get 0.7 in the highlights but 1.4 more in the shadows with RAW compared to JPEG. That means that if you've blown highlights, then they're likely beyond repair.
DPreview seem to say the opposite. Foveon sensors have a good range above middle grey but are poor in the shadows. That is what you would expect from noisy sensors. The Foveon seems to have pretty good dynamic range but not mind blowing as some seem to suggest. Those shadows do remain the achilles heel. Perhaps the new sensor will offer better noise control without affecting the higher end response. I hope so.

As far as the original question is concerned, overexposure blows out skies just the same as any other sensor. I'm sloppy with exposure and tend to bracket when in doubt but I have loads of examples of blown highlights from the DP1 and SD9.
I'd say they're exceptionally good at exposure. Even Kendall, who I've never seen post a single negative comment about Foveon sensors, said that the strength of the Foveon sensor is in shadow-preservation, not highlight-retention. This can also be seen from the DPreview measurements, where the shadow-latitude is much bigger than the highlight-headroom. They were actually only able to retain 0.7EV highlights over JPG in RAW.

From these measurements you can also see that the DR-performance is average.
i see that

but if you get a chance to look at more foveon images, they consistently show clouds with good detail, no part of them blown. Now either these guys are exceptionally good at exposure (which, no offence seems kinda unlikely in a consistent way), or there is something else going on here
--
Galleries and website: http://www.whisperingcat.co.uk/default.shtml
--
Galleries and website: http://www.whisperingcat.co.uk/default.shtml
 
Not really fair to blame Canon for my PP and treatment of the image.
Welcome to the world of Foveon image comparison - where every image flaw is obviously due to the inferior sensor of other cameras even when the details of how the image was shot/produced is not known.

--
Erik
 
But that image brings up an opportunity to present a 10MP shot from a Bayer camera ( the D60 ) of the same target (200 upsampling again):
Big deal. So neither one can properly reproduce a red/blue chart.
Actually the Sigma did just fine, because at 100% you could tell the chart was blue and red despite some purple intermingling.
In other words, it's wrong. There was no purple in the original.
The Bayer sensor failed to resolve it was fully a series of curves. Obviously the Sigma produced the result that was photographically more correct since it represented reality.
Only if you consider photographically more correct to mean have the wrong colours.
How often do you take photos of red/blue charts anyway? More often than you photograph that wall with varying red tones?
I take pictures of red leaves on blue sky all the time in the fall. Do you stall indoors all fall? How sad.
Skies are not a perfect saturated blue, nor are leaves a perfect saturated red. There's a mix of RGB in both, which is one reason why a red/blue chart is completely irrelevant.

And given the colour shift noted above, do your red leaves come out purple? You seem to think that drastic colour shifts are 'correct' somehow.
Bayer handles real world subjects very well, as millions of photos prove.
And millions more prove that Foveon handles them even better.
There are orders of magnitudes more photos taken with Bayer cameras.
 
A couple of observations:

The D60 shows the chart as red and blue, the DP1 show them in colors resembling pastel.

This chart is different from real-world shooting in the manner that few real-world subjects are so distinctively red or blue that they only affect those pixels, and no overlap occurs. This makes it the worst case scenario for Bayer sensors.

The Foveon has the advantage with the red-blue portion, but others are to my eye either equal, or in favor to the D60.
Since it "failed" in a way that was spectacularily better than the 10MP challenger, then I guess you'd refer to the Bayer sensor as an Uber Failure

Your definition, not mine. I would have said it did OK.

Actually the Sigma did just fine, because at 100% you could tell the chart was blue and red despite some purple intermingling. The Bayer sensor failed to resolve it was fully a series of curves. Obviously the Sigma produced the result that was photographically more correct since it represented reality.

I take pictures of red leaves on blue sky all the time in the fall. Do you stall indoors all fall? How sad.
 
Not really fair to blame Canon for my PP and treatment of the image.
Welcome to the world of Foveon image comparison - where every image flaw is obviously due to the inferior sensor of other cameras even when the details of how the image was shot/produced is not known.
It's the general case when people prefer to trust 'their own eyes' than properly collected evidence. Eyes, especially one's own, are very fallible.

--
Bob
 
Im just saying there has to be a reason
Well, the first question would have to be how accurate is your observation in the first place. Is it really the case that Foveon sensors are less prone to blowing the highlights. When making that kind of statement a few comparative examples are good.
just general observations
yeah, well, general observations need a bit of evidence behind them.
yep, thats why i made observations
so i would have some evidence
so what is it, the bit depth or what?
The bit depth won'y make any difference to whether highlights blow or not.
more bit depth will give better roll off and tonality
no it won't so long as there's enough bits to cover the DR of the sensor plus read electronics, more bit depth makes no difference at all.
well 'evidence' elsewhere suggests otherwise for the input side
and it may well be wrong but, hey thats evidence for you

http://forums.dpreview.com/forums/read.asp?forum=1032&message=25654838

heres a few tips for that image
http://www.cambridgeincolour.com/tutorials/bit-depth.htm
http://www.luminous-landscape.com/tutorials/bit-depth.shtml
http://paintbynumberkits.com/
and make the unblown parts more interesting, perhaps disguising to an extent blown parts. Fully blown clouds become uninteresting rather like this one of yours with that rather cr@p blue canon produces



i guess that covers it ;)
Not really fair to blame Canon for my PP and treatment of the image.
you used Program mode and pulled the trigger,
by and large thats the problem here

--
Riley

any similarity to persons living or dead is coincidental and unintended
 
Kendall Helmstetter Gelner wrote:

The railings clearly show in front of the left (bent) leg. The area around the right leg is too busy to make out the railing even against the black pants.
They still fade out in the bent leg.
If it's CA at work, what lens gives you flesh colored CA?
If you have a blue object on a red background as here, the blue will run into the red and vice versa.
But the same happens again skin too, which again is not really red at work.
Can you do the resizing again using nearest neightbour interpolation
They appear to be about 2-3 pixels wide.


I said the resolution limit of the "sensor". Bayer sensors have the lowest resolution for red / blue, that's well established in colour resolution charts. Your images are consistent with my "supposition".
I'm not sure, since the railings are a little wider than just a pixel.. but for sure the lower red/blue resolution is playing a part there, I would say for sure in the case of the box and somewhat less in the case of the runners legs.
Indeed there is some color bleed through, but not an outright vanishing as with the railings against legs - instead the falloff is more natural.
The red lines also did not vanish in the equivalent D60 image.
Ahh, but they do show dropouts in the middle, randomly, which I would argue is actually less preferable to a simple dropoff because it's more notable.
Interesting that you have not brought out the equivalent Foveon image for that railing scene to extoll the virtues of Foveon instead of just bashing Bayer. How did Foveon fare in that scene now, really?
I would love to - but despite the M9 and D3X images coming from camera reviews on two totally different sites (one is DPReview, the other Imaging Resource) neither of them bothered to use that same scene with any Foveon based camera!

The next time I'm in London I'll seek to replicate the shot at different focal lengths to get near a single pixel width for the railings. Or, if I can find any blue railings locally I may try some tests. Blue railings are harder to find than you would think.
Well that's what happens when you shoot a DP-1 and overexpose reds, later cameras did not have this issue. Also the JPG conversion (in camera JPG I think used for the reviews) may have altered the tone a bit.
DP1, D60, etc. They were all shot in jpeg.
Right, but everyone knows the bayer cameras have a lot more advanced JPG processing engines, certainly moreso than the DP-1 at the time that was taken.

I was hoping they would have an X3F fie with the review for that image but I could not find one. Im looking to produce a red/blue color chart to see if in raw the effect would be the same or as pronounced.
It's aliasing, clearer if you look at the small circle. Happens to Foveon too on the similar patterns if the sensor resolution limit is exceeded, which in this case it's not.
I'm not talking so much about the spatial aliasing causing the odd patterns, more like single pixel dips into the larger red bands making them look kind of choppy.
So we have established that
  • when the resolution of the sensor (or the lens) is exceeded, colour errors occur in colour line pairs regardless of sensor technology (simple in the Foveon case: if you have red and blue lines denser than the pixel density, you will have both red and blue on every pixel.
I don't think that's what is happening in either image though, since you see the purple show up in the foveon image earlier than the single pixel case.
  • the colour resolution limit of Bayer for some colour pairs (especially red / blue) are lower than half the Foveon pixels, so red / blue line pairs will start to run together earlier than expected, especially when you zoom to 200% (when you really ought to be zooming down to 70.71% to halve the pixel count to make a "Foveon equivalent")
I didn't want to go off even powers of magnification so as not to introduce artifacts, which is actually also why I chose bicubic for upsampling as I thought it would be most representative.
  • on the other hand, it will resolve more than half the Foveon pixels' worth of line pairs with less colour, and resolve much more than half for black and white line pairs.
  • therefore, on average Bayer resolves the equivalent of 50% the amount of Foveon pixels. Of course, it may resolve rather less than that for a person with a fixation on red and blue line pairs ;)
Sounds about right.
  • there is nothing special to Bayer about the loss of detail or colour shift around colour line pairs that isn't compensated for overall by extra resolution in more favourably coloured areas. As per point 1, Foveon sensors also colour shift under similar conditions, it just has a higher threshold (but a lower threshold for monochrome lines)
Again, I'm not sure the railings are small enough for that to be quite what is happening. But it's an interesting case to examine.

--
---> Kendall
http://InsideAperture.com
http://www.pbase.com/kgelner
http://www.pbase.com/sigmadslr/user_home
 

Keyboard shortcuts

Back
Top