X10: No RAW converter with full EXR support?

Interesting, but - it seems to show more about the vagaries/inadequacies of different 'third party' raw converters, and doesn't reveal that all that much about the camera itself.
Some general observations about X10 RAF files that I learned from this comparison, like always these are my personal observations and interpretations:

OOC JPGs are lens (distortion) corrected!
That's no surprise.

Early sample wide-angle shots looked far too 'straight' - I thought they were quite obviously 'corrected' in camera by software/firmware.

Many cameras use lens distortion correction these days - it's a lot easier/cheaper to fix this kind of thing in software/firmware than it is to design and manufacture better optics.

I remember seeing an uncorrected wide-angle shot of a Canon S95, and the barrel distortion was quite shocking.

I would almost guarantee that the camera also deploys quite significant lens vignetting compensation too, when required, and just possibly even some chromatic aberration correction.
Both 12 MP and 6 MP images (DR 100-400) store all information from both sensor halves in the RAW file which then needs to be properly decoded and combined by the RAW software. This is where all tested RAW converters fail compared to OOC JPG!
'Raw' should always 'ideally' record/save all sensor data where ever possible - ideally allowing the user to change choices/options later.
Only 6 MP RAWs of 9 mb filesize already contain the combined sensor information and thus don't rely on the RAW software for decoding. With DR 200/400 the 9 mb files are already noise-reduced and offer full color saturation (see below) in all RAW converters that can open them.
As you probably remember - I've previously suggested that it's likely that the camera may switch to a combination of software/ISO DR with 'pixel-pair binning' at higher ISO, instead of 'dual/split-exposure DR'.
It also seems like ISO based DR indeed uses only half the sensor for ISO/amplification tricks, which then has to be properly combined with the overexposed half just like EXPosure time based DR.
I don't think that is likely at all - I don't see your reasoning.

When the camera doesn't use it's 'dual/split-exposure' method, then all pixels are exposed the same, so they should all be the same signal/exposure and all equally useful and valuable.
 
Interesting, but - it seems to show more about the vagaries/inadequacies of different 'third party' raw converters, and doesn't reveal that all that much about the camera itself.
If you cannot analyze the cause then being able to get a better picture on the symptoms helps a lot already.
OOC JPGs are lens (distortion) corrected!
That's no surprise.

Early sample wide-angle shots looked far too 'straight' - I thought they were quite obviously 'corrected' in camera by software/firmware.
No surprise, no. But people kept disputing that in-camera and/or RAW converter lens correction would happen and now I know for sure. Additionally I have a way to see true lens distortion at various angles to make better educated decisions about what angle to use where high detail matters (digital correction means loss of detail).
'Raw' should always 'ideally' record/save all sensor data where ever possible - ideally allowing the user to change choices/options later.
I agree, and this is why I see the "10 mb RAW" file anomaly as a bug rather than a feature. But given how poorly all RAW converters work with full 18 mb DR 200/400 RAW images it currently is a bug that turned into a feature.
As you probably remember - I've previously suggested that it's likely that the camera may switch to a combination of software/ISO DR with 'pixel-pair binning' at higher ISO, instead of 'dual/split-exposure DR'.
I have not seen any indication yet that ISO DR uses different methods at different ISOs. There are indications for half the sensor being underexposed and indications for the full sensor being underexposed, but the outcome is pretty much consistent. Even high ISO 18 mb RAWs still need to be binned by the RAW converter as it seems (did a quick and dirty comparison of 10 mb vs 18 mv RAW at ISO 1600 + DR 400), so again no apparent difference as far as ISO is concerned.

Both ISO based DR and EXPosure based are a combination of hardware underexposure + curves. It doesn't really make sense to call one hardware and the other software. BTW, ISO DR 400 pulls down highlights by about -2.5 EV, not just 2 full stops. So it seems that after hardware ISO/amplification underexposure happened the highlights are further pulled down by curves (there is headroom left).
It also seems like ISO based DR indeed uses only half the sensor for ISO/amplification tricks, which then has to be properly combined with the overexposed half just like EXPosure time based DR.
I don't think that is likely at all - I don't see your reasoning.
The reasoning is that RAW converters have a hard time combining both halves of the sensor only with 18 mb RAW files , regardless of the camera setting! When ISO DR would expose both halves the same then I fail to see the reason why only 18 mb files under-saturate (plus increased noise) in RAW software, but not in pre-combined RAW/JPG.

Some further and more detailed tests would have to be done to take a closer look at this. If you've got spare time on your hands, feel free to to some of your own. I specifically need to take a look at DR 100 18 mb files, too. ;)
When the camera doesn't use it's 'dual/split-exposure' method, then all pixels are exposed the same, so they should all be the same signal/exposure and all equally useful and valuable.
Yes, they should. But since the outcome is very different this is an indication that ISO DR might also be using split exposure for the sensor halves.
 
'Raw' should always 'ideally' record/save all sensor data where ever possible - ideally allowing the user to change choices/options later.
I agree, and this is why I see the "10 mb RAW" file anomaly as a bug rather than a feature.
Not necessarily. If pixel binning combines the analog measurements prior to the conversion to a digital value then there may only be 10 MB of data for the RAW file.
 
Yes, but if analogue binning would happen (which I doubt) then it would happen for all ISO + DR combination and not only some of them and not only when RAW + JPG is used.

And a different process would also show as a different outcome in JPGs, which does not seem to be the case.
 
OOC JPGs are lens (distortion) corrected!
That's no surprise.

Early sample wide-angle shots looked far too 'straight' - I thought they were quite obviously 'corrected' in camera by software/firmware.
No surprise, no. But people kept disputing that in-camera and/or RAW converter lens correction would happen and now I know for sure. Additionally I have a way to see true lens distortion at various angles to make better educated decisions about what angle to use where high detail matters (digital correction means loss of detail).
There is so much 'digital processing' that occurs anyway - I really don't think that lens distortion correction is any worse than all the other routine de-mosaic interpolation, diagonal> orthogonal re-sampling, NR, sharpening, etc, that are always carried out anyway.
'Raw' should always 'ideally' record/save all sensor data where ever possible - ideally allowing the user to change choices/options later.
I agree, and this is why I see the "10 mb RAW" file anomaly as a bug rather than a feature. But given how poorly all RAW converters work with full 18 mb DR 200/400 RAW images it currently is a bug that turned into a feature.
I see it to be quite the opposite - the fact that the raw data halves in size, is most likely only done for some good and sound reason. Not a bug, nor a feature as such, but a rational/logical result of a process like internal 'pixel binning'.
As you probably remember - I've previously suggested that it's likely that the camera may switch to a combination of software/ISO DR with 'pixel-pair binning' at higher ISO, instead of 'dual/split-exposure DR'.
I have not seen any indication yet that ISO DR uses different methods at different ISOs.
...except where the RAF files change by almost a half in size - that's certainly an 'indication' of something.
There are indications for half the sensor being underexposed and indications for the full sensor being underexposed, but the outcome is pretty much consistent. Even high ISO 18 mb RAWs still need to be binned by the RAW converter as it seems (did a quick and dirty comparison of 10 mb vs 18 mv RAW at ISO 1600 + DR 400), so again no apparent difference as far as ISO is concerned.
When looking at the raw data - 'ISO DR' data will always 'appear' like underexposure, indistinguishable from the under-exposed half of the 'dual exposure-time DR' method.

Also, it is possible that the camera could employ 'dual-ISO DR' - which would produce identical data to that of 'dual exposure-time DR'.

One sure way to differentiate the two possible methods, as you know, is to detect the dual shutter speed timings the way you've done previously with a moving highlight subject/target.
Both ISO based DR and EXPosure based are a combination of hardware underexposure + curves. It doesn't really make sense to call one hardware and the other software.
Yes, indeed I mostly agree there - although it is sometimes necessary to use terms that others here are more familiar with.
BTW, ISO DR 400 pulls down highlights by about -2.5 EV, not just 2 full stops. So it seems that after hardware ISO/amplification underexposure happened the highlights are further pulled down by curves (there is headroom left).
I'm not convinced - I wonder if you may be mistaken there. It's complicated/confusing to try to evaluate 'EV' within 'curved' data.

It doesn't make sense to shift the 'normal exposure's highlights down further than the extra EV/DR gained by the lesser-exposed part.
It also seems like ISO based DR indeed uses only half the sensor for ISO/amplification tricks, which then has to be properly combined with the overexposed half just like EXPosure time based DR.
I don't think that is likely at all - I don't see your reasoning.
The reasoning is that RAW converters have a hard time combining both halves of the sensor only with 18 mb RAW files , regardless of the camera setting! When ISO DR would expose both halves the same then I fail to see the reason why only 18 mb files under-saturate (plus increased noise) in RAW software, but not in pre-combined RAW/JPG.
O.K. - I'm seeing the way you're thinking a bit more clearly now.

I agree it is possible that the 'ISO DR' could use two different ISO/amplification settings - although the actual 'exposure' is still the same (same shutter speed and aperture), so there is no "overexposed half" as such.
Some further and more detailed tests would have to be done to take a closer look at this. If you've got spare time on your hands, feel free to to some of your own. I specifically need to take a look at DR 100 18 mb files, too. ;)
I'm currently writing some code that enables me to directly access and analyse X10 RAF files' sensor data.

Unfortunately I don't own an X10 (or any other Fuji camera) - but I have downloaded a few RAF files to work on.

Maybe you'd like to volunteer to supply me with some more specific 'DR' sample files - if, as and when, I'm ready/able to analyse them...?
When the camera doesn't use it's 'dual/split-exposure' method, then all pixels are exposed the same, so they should all be the same signal/exposure and all equally useful and valuable.
Yes, they should. But since the outcome is very different this is an indication that ISO DR might also be using split exposure for the sensor halves.
Split gain/ISO, yes, quite possibly - but that's not split 'exposure' - the 'exposure' (EV) is the same.

If the 'gain/ISO' is split then I should be able to see and confirm this using the code I'm working on.
 
CO v. 6.3.3 has a preliminary support of the X10 so things like distortion corrections, fringing, etc. might still be corrected when (/ if?) it receives the full support treatment in some future release. What seems unlikely, though, is getting combined 12MP files in CO -- I doubt this proprietary information concerning the operation of the EXR technology is going to be shared with 3rd party converters -- see this explanation of how PhaseOne treats this type of files:
http://forum.phaseone.com/En/viewtopic.php?f=41&t=11599&st=0&sk=t&sd=a#p53235

Basically they think that the 12MP mark is reached by interpolation and they prefer not to offer it with the 100% output setting (which sounds logical, providing that their premises are right, which I'm not so sure about). Those issues aside, I still think CO offers one of the best white balancing and tonal output, certainly better than Adobe.

As for Timur's OP -- I've been wondering how the in-camera raw conversion compares to the OOC jpegs. Logically, they should be the same (given the default settings) but with this EXR technology nothing seems to be sure any more...
--
Marcin
http://flickr.com/photos/sankos/
 
Glad you can use it. I don't own the DNG converter or Photoshop, but just got the trials/betas of all versions I tested here. Does it even support Fuji RAF files?
Adobe's DNG Converter is free. http://www.adobe.com/support/downloads/product.jsp?product=106&platform=Windows

It converts X10 RAF files to DNG (Adobe Digital Negative) format which is a RAW format recognized by a number of converters and editing programs. The resulting DNG files open as 4000x3000 images if the come from a "L" RAW (19Mb) file and as a 2816x2112 image if they come from a "M" RAW (10Mb) file. Whether these L and M images are correctly converted, or what happens with EXR files in 19Mb RAWs is beyond my ability to really test effectively, but I'd be curious to know what (if anything) you might be able to find out.

--
Victor Z

 
CO v. 6.3.3 has a preliminary support of the X10 so things like distortion corrections, fringing, etc. might still be corrected when (/ if?) it receives the full support treatment in some future release. What seems unlikely, though, is getting combined 12MP files in CO -- I doubt this proprietary information concerning the operation of the EXR technology is going to be shared with 3rd party converters -- see this explanation of how PhaseOne treats this type of files:
http://forum.phaseone.com/En/viewtopic.php?f=41&t=11599&st=0&sk=t&sd=a#p53235

Basically they think that the 12MP mark is reached by interpolation and they prefer not to offer it with the 100% output setting (which sounds logical, providing that their premises are right, which I'm not so sure about).
'PhaseOne' appear to be showing quite some ignorance...

They are right as regards the old 'S3' - but they are quite wrong as regards the 'X10'.

The 'S3' and 'X10' sensors are very different...

The 'S3' only has 6MP of 'normal' pixels (but supplemented by 6MP of smaller/lower sensitivity pixels that only extend highlight capture).

The 'X10' has a full 12MP of 'normal' pixels (but half can ' optionally ' use a lower exposure time to extend highlight capture).

The 6MP to 12 MP 'interpolation' that they refer to, was something Fuji always used to do for their 'Super CCD' sensors as a consequence of the need to translate their diagonal pixel layout to the standard 'orthogonal' layout that image files/processes require.

It seems that Fuji have more recently dispensed with this 'interpolation data-doubling' and are now effectively 're-sampling back down' to an 'equivalent real resolution' after any de-mosaic interpolation - possibly simply because 24MP output files would be considered too unwieldy/wasteful of space and post-processing speed resources.
 
The 'S3' and 'X10' sensors are very different...
That's what surprised me in Drew's comment, where he seems to be making no distinction between the two distinctly different sensor technologies.
The 'X10' has a full 12MP of 'normal' pixels (but half can ' optionally ' use a lower exposure time to extend highlight capture).
So in practical terms, it is a 6MP camera if you want to maximize its potential for high DR scenes or for low light situations (the famous M-size / DR400 or M-size / DR100 jpeg formula respectively). The problem seems to me that CO treats those 6MP as 'regular' ones, thus wasting the potential. I realize why this is so -- it's unlikely that Fuji will share with P1 the EXR know-how and it's not practical for them to do the reverse-engineering on this camera as it would be really time-consuming to investigate all the options involved in countless combinations of settings (i.e. all the variations of focal length, ISO, aperture, exp. time, DR setting, size, etc.). I suspect this "EXR magic" might be the reason behind the firmware delays that seem to be plaguing this camera since its launch (remember the delay connected with finalizing the firmware?).

All of this makes me think that the X10 might really be a 6MP-jpeg camera in practical terms, I mean in the way I would be likely to use it -- that's something I was wary of accepting back in October, when AdamT pointed this out to me. I've been shooting raw exclusively since going digital and having to switch to jpeg for this camera sounds like a shame (more so than the resolution drop).
--
Marcin
http://flickr.com/photos/sankos/
 
I realize why this is so -- it's unlikely that Fuji will share with P1 the EXR know-how
That seems rather self-defeating.

In other words, unless Fuji develops it own RAW processor (and not Silkypix which is licensed) they will NEVER produce RAW files that photographers can actually use.

I agree with your assessment that this seems a jpg camera. As a confirmed RAW shooter it's problematic for me at the moment.

--

“There is only you and your camera. The limitations in your photography are in yourself, for what we see is what we are.” Ernst Haas

http://garyp.zenfolio.com/p518883873/
 
There is so much 'digital processing' that occurs anyway - I really don't think that lens distortion correction is any worse than all the other routine de-mosaic interpolation, diagonal> orthogonal re-sampling, NR, sharpening, etc, that are always carried out anyway.
Any signal processing gets less transparent (more artifacts) a towards the extreme values, so less distortion means one variable less to worry about. Look how the simple test charts look so different from different RAW processors (especially with diagonal lines). Once I find time I will take a look at possible differences.
I see it to be quite the opposite - the fact that the raw data halves in size, is most likely only done for some good and sound reason. Not a bug, nor a feature as such, but a rational/logical result of a process like internal 'pixel binning'.
I do not question the size being a result of pixel binning, I question that only half the information (aka binned) is stored when all information is available. The camera produces 18 mb files when using the very same settings and very same DR methods, just the RAW vs. RAW + JPG part is different. It's inconsistent in all possible aspects and images don't seem to reveal any sound reason for that. Raw should be Raw, not halfway Jpg.

But the current state of Raw software turns the anomaly into a useful and desirable thing.
As you probably remember - I've previously suggested that it's likely that the camera may switch to a combination of software/ISO DR with 'pixel-pair binning' at higher ISO, instead of 'dual/split-exposure DR'.
I have not seen any indication yet that ISO DR uses different methods at different ISOs.
...except where the RAF files change by almost a half in size - that's certainly an 'indication' of something.
Only of the available full information not being saved when it was possible. 10 mb Raw files are preprocessed one step further than they should be. And Raw processors should offer far more control over the individual halves (like indiv. Highlight control, different methods and levels of blending etc).
When looking at the raw data - 'ISO DR' data will always 'appear' like underexposure, indistinguishable from the under-exposed half of the 'dual exposure-time DR' method.
Only when amplification/ISO of the whole sensor is decreased, not when only half is decreased. It's a harder task to combine nominally differently exposed halves (counting Iso as image exposure) than combining equally exposed ones.
Also, it is possible that the camera could employ 'dual-ISO DR' - which would produce identical data to that of 'dual exposure-time DR'.
Isn't the question if ISO DR is using separate ISO on both sides what we are talking about? I wrote that the Raw software behavior (aka output image) is one indication for split Iso.
One sure way to differentiate the two possible methods, as you know, is to detect the dual shutter speed timings the way you've done previously with a moving highlight subject/target.
Several people on this board seem to disagree, but once you understand what "time difference" means in practice it's rather obvious. But the saturation and noise artifacts of Raw converters having to handle DR 200/400 are the very same for both DR methods.
Yes, indeed I mostly agree there - although it is sometimes necessary to use terms that others here are more familiar with.
But terms are I'll-chosen, because they judge one method as being "true" and the other as being "just a simple software trick". Combine that with the wrong folklore that M size always uses "hardware DR" and you only get confusion on what really happens.
I'm not convinced - I wonder if you may be mistaken there. It's complicated/confusing to try to evaluate 'EV' within 'curved' data.
I meant in Jpg. Dr 400 stronger clipping/highlight protection than corresponding Dr 100 shots at 2 stops lower Iso accomplish, appr. 2.5 stops total (until clipping areas match).
I agree it is possible that the 'ISO DR' could use two different ISO/amplification settings - although the actual 'exposure' is still the same (same shutter speed and aperture), so there is no "overexposed half" as such.
Yes, I used bad wording there. I only meant split operation and different outputs of both halves. That exposure of the photo sites to photons remains the same is understood (and the reason why Iso Dr cannot help against blooming induced orbs).
Maybe you'd like to volunteer to supply me with some more specific 'DR' sample files - if, as and when, I'm ready/able to analyse them...?
Sure, if it doesn't take me too much time. I expect every Exr Raf to be more or less the same, so you should be able to use non X10 files, too, though.
If the 'gain/ISO' is split then I should be able to see and confirm this using the code I'm working on.
If it's not split then shame on Raw software developers to get such bad output out of the 18 mb files.
 
Moreover the X10 metering in RAW+JPEG seems to overexpose 2 stops, based on this test:
No, it does not! Except for the very specific (and unique) combination of using A-perture priority mode with non Auto Dr (aka "enforced" Dr) + non Auto ISO + ISO lower than 400 + ISO lower than DR + exposure time longer than 1/4.

In this very special case nominal ISO is increased and the metering does not shorten exposure time accordingly (likely because metering comes first and then the user enforces fixed and "wrong" Dr and Iso values).

Switch to Iso 400 and all turns normal again (Iso 100 + Dr 400 = Iso 400 + Dr 400).
 
Moreover the X10 metering in RAW+JPEG seems to overexpose 2 stops, based on [KimL's] test [but note, he returned his X10].
No, it does not! Except for the very specific (and unique) combination of using A-perture priority mode with non Auto Dr (aka "enforced" Dr) + non Auto ISO + ISO lower than 400 + ISO lower than DR + exposure time longer than 1/4.
OK, thanks for the correction.

I believe the X10 overexposes, as does my F550, so I would permanently set -.3 EV or something. I really don't see the point of buying an EXR camera if it blows highlights.

Earlier this month I complained about blown highlights with the X10, but it didn't get much reaction.

http://forums.dpreview.com/forums/read.asp?forum=1012&message=40225814
 
What seems unlikely, though, is getting combined 12MP files in CO -- I doubt this proprietary information concerning the operation of the EXR technology is going to be shared with 3rd party converters -- see this explanation of how PhaseOne treats this type of files:
Since Lightroom, Silkypix and in the future DXO support this - even when faulty - it seems save to assume that either the information is available from Fuji or it's at least possible to extract it from the RAF files.
As for Timur's OP -- I've been wondering how the in-camera raw conversion compares to the OOC jpegs. Logically, they should be the same (given the default settings) but with this EXR technology nothing seems to be sure any more...
I can give it a shot, but I expect it to be the same.
 
So in practical terms, it is a 6MP camera if you want to maximize its potential for high DR scenes or for low light situations (the famous M-size / DR400 or M-size / DR100 jpeg formula respectively).
Not so necessarily. EXPosure time based DR is only available within a limited subset of setting and ISO based DR is available for both M and L size images. Noise reduction by using DR 100 M size images mostly only affects the jump from ISO 400 to 800 (have yet to check DR 200/400 M vs. L). And at least at DR 100 you do get more detail out of images in L (again yet have to check DR 200/400).

When you are shooting RAW only there is no M vs. L anyway, you will always get the full 12 MP information and your RAW converter software has to be able to handle it. Unfortunately none of the software I tested does that in a proper way.
 
There is so much 'digital processing' that occurs anyway - I really don't think that lens distortion correction is any worse than all the other routine de-mosaic interpolation, diagonal> orthogonal re-sampling, NR, sharpening, etc, that are always carried out anyway.
Any signal processing gets less transparent (more artifacts) a towards the extreme values, so less distortion means one variable less to worry about.
My point was that it is just a form of fractional 're-sampling' - and that's something that is routinely happening anyway, and it's far from being anything extreme.

Fractional re-sampling of 'real world' digital camera images makes little or no perceptible difference to naked eye image quality.
Look how the simple test charts look so different from different RAW processors (especially with diagonal lines). Once I find time I will take a look at possible differences.
Examining 'test charts' usually has very little bearing on the outcome in 'real world' images.

The technicalities/technology involved is certainly interesting - but people really shouldn't obsess over these kind of things, as they are rarely if ever of much significance in 'real world' images.
 
I see it to be quite the opposite - the fact that the raw data halves in size, is most likely only done for some good and sound reason. Not a bug, nor a feature as such, but a rational/logical result of a process like internal 'pixel binning'.
I do not question the size being a result of pixel binning, I question that only half the information (aka binned) is stored when all information is available. The camera produces 18 mb files when using the very same settings and very same DR methods, just the RAW vs. RAW + JPG part is different. It's inconsistent in all possible aspects and images don't seem to reveal any sound reason for that. Raw should be Raw, not halfway Jpg.

But the current state of Raw software turns the anomaly into a useful and desirable thing.
Why do you say "...useful and desirable..." ..?
As you probably remember - I've previously suggested that it's likely that the camera may switch to a combination of software/ISO DR with 'pixel-pair binning' at higher ISO, instead of 'dual/split-exposure DR'.
I have not seen any indication yet that ISO DR uses different methods at different ISOs.
...except where the RAF files change by almost a half in size - that's certainly an 'indication' of something.
Only of the available full information not being saved when it was possible. 10 mb Raw files are preprocessed one step further than they should be. And Raw processors should offer far more control over the individual halves (like indiv. Highlight control, different methods and levels of blending etc).
You are assuming that the 'two halves' of data are processed and available separately.

If the two halves (pixel pairings) were combined in hardware/electronically then the available quantity of RAW data would halve.

That said, however - I've not actually ever seen any evidence/statement that supports hardware/electronic pixel signal addition - and as you say, the 'RAW + JPEG' v 'RAW only' anomaly still remains.

Nevertheless, the fact that this 'anomaly' is also seen in previous 'EXR' cameras, and is also still present in the later X10 - seems to suggest to me that it's something done for a reason, but a reason we just don't know, as yet.
 
Why do you say "...useful and desirable..." ..?
...
You are assuming that the 'two halves' of data are processed and available separately.
My perception and interpretation (and the basis for this thread) is that 18 mb RAW files always hold the information of both sensor-halves separately and that it is the job of the RAW converter software to combine them into a final image (be it a 12 MP one or a 6 MP one, be it with or without DR).

Capture one only makes use of the information of one half while completely ignoring the other (even when it's available), Silkypix and Lightroom seem to use both halves, but with very questionable results as soon as DR 200/400 is used (and slightly less detail at 12 MP + DR 100).

Since RAW software does so bad at combining sensor halves' DR information from the 18 mb RAW file it is "useful and desirable" to get 10 mb RAW files for some RAW+JPG combinations. That is because 10 mb RAW files are pre-combined in-camera by the obviously advanced EXR algorithms of the camera and then written at 6 MP resolution (half the information) to the RAF file.

And you still can do a lot of things with this half-resolution but higher bit-rate RAW that would not be easily possible with lower bit-rate and lossy compressed JPGs (the camera seems to use 98% for fine compression btw). So a good quality 6 MP RAW workflow is better than a bad quality 12 MP one.
 
Examining 'test charts' usually has very little bearing on the outcome in 'real world' images.

The technicalities/technology involved is certainly interesting - but people really shouldn't obsess over these kind of things, as they are rarely if ever of much significance in 'real world' images.
You are absolutely right, which is why I have to do some detail shots of more mundane things before deciding if it's even worth the hassle. ;)
 

Keyboard shortcuts

Back
Top