At long last, here’s the comparison of color rendering promised several weeks ago – between work and the display board in my main PC failing, this has taken longer than I’d expected. This post compares the color rendering of Lightroom, Aperture and Capture One versus a synthetic test image. That image was created by taking the raw image from a Leica M8, which is in DNG format, and then replacing the contents of the image with a synthetic version of a GretagMacbeth 24-patch color chart. This can be done because DNG format files contain all the color calibration information that’s required to go from the Camera’s raw image space to a real image in the two ColorMatrix matrices. So the synthetic image is built by taking the l*a*b* color values for the GretagMacbeth test chart, and reversing the calibration matrixes in the Leica DNG file. This, btw, is being done using a modified version of CornerFix – I’m currently debating whether to include the synthetic image creation functionality in the next official CornerFix release.

The synthetic test image is what a “perfect” M8 would show. But “perfect” here means an M8 that matches Leica’s calibration matrixes. However, there is no one single best calibration for a real camera. Pretty much all camera calibration is done via a three by three matrix. Using that, you can dial in any three particular colors exactly. So, for example, you can get the red, blue and green patch on the GretagMacbeth chart down to the last decimal point. If sensors were perfect, that calibration would also mean that every other patch would also be calibrated. However, in a real sensor, there are a whole lot of imperfections – among other things, the filters in the Bayer matrix aren’t ideal, so colors bleed between each other, and the sensitivity of the sensor itself varies with the frequency of the light striking it. So, even if you dial three patches in perfectly, the others will be out. So practically, what camera manufacturers and raw developer software writers have to do is to find a calibration that is a compromise across a whole range of colors. However, because people are more sensitive to certain colors being out (e.g., skin tone, foliage, etc) that compromise is often weighted in favor of the sensitive colors.

The M8 test images can be found here: http://chromasoft.googlepages.com/referenceimages

The charts below show the difference between the theoretical color values that we should see for a selection of six of the more important color patches, and what we actually get. So, for example, if the red bar of the “Cyan patch” shows a value of -5, that means that the actual measured value of the R component of the RGB values as read out by the software in question was 5 units less that the theoretical value as shown in the spreadsheet I discussed in the last post. In all cases, the scale is 0 to 100.

First up is Lightroom. It shows minimal deviations from the theoretical values – all the values are within 3 units. But this shouldn’t come as a surprise – Lightroom internally uses the exact same color model as the DNG file, and we know that Lightroom uses exactly the same color calibration as the Leica DNG’s have embedded into them. The minor deviations that we seeing are really just slight imperfections in the tone curve and in the color temperature interpolation process that Lightroom uses.



Next up is Aperture. There are three Aperture graphs, the first for Aperture V1.5.4. In addition I also have graphs for Aperture 2.0, which came out a few days ago. Aperture 2.0 provides four “Raw Fine Tuning” settings, “1.0”, “1.1”, “2.0” and “2.0 DNG”. I checked, and color rendering from the old 1.5.4 and what you get by setting “1.1” in 2.0 are indeed identical. Firstly, all of the Aperture settings have lot less green in the red patch than Lightroom, and less red in the blue and cyan patches. The 2.0 results are not much different to the 1.5 results; a little bit less red in the blue patch, a bit less green in the red patch, but far less blue in the yellow patch.


The “2.0 DNG” setting is more interesting. There doesn’t seem to be much documentation on what it does – the Apple aperture site itself is silent on the subject, and various third party sites have words to the effect of “changes to the image using the 2.0 DNG converter are made based on the DNG specification of the file”. This implies that rather than using the Aperture color conversion parameters, setting the DNG mode will give you the colors as set by the ColorMatrix values embedded in the DNG. As it turns out however, that’s just not the case – if it were, we’d see values that looked like Lightroom, but what we see are just some subtle changes to the “2.0” profile. Although visible if you change the setting on the fly, the change is actually more subtle than the change between 1.5 and 2.0.




Finally, there is Capture One. During the course of this process, Capture One 4.0.1 came out; the results shown here are for 4.0.1, but they are identical to those for 4.0; as far as I can tell, no changes have been made to color rendering between versions. Capture One provides two profiles, one Generic, and one UVIR, designed to match to the M8’s color rendering when mounted with a UVIR filter. While the differences between these two are there, they are quite subtle. Overall however, there are significant differences to the rendering of either Lightroom or Aperture. Capture One shows less red for most patches, especially the red patch, but more red in the cyan patch. Finally, there is generally somewhat less saturation for most colors. This is broadly consistent with most people’s views on Capture One’s rendering as being “less red” than Lightroom.

In the next post I'll show the same charts for actual rather than synthetic images.
2

View comments

Good news in a difficult year - all the macOS apps that I support - AccuRaw EXR, AccuRaw Monochrome, pcdMagic, CornerFix, dcpTool (both the GUI and command line version), DNG cleaner and pcdtojpeg - now are all available with native Apple Silicon versions for blazing fast performance on Apple's new "M1" processor. Download are in all the usual places.

Enjoy.

There's a whole slew of new camera support, including for Canon's new CR3 format.

Updates of AccuRaw EXR, AccuRaw Monochrome, PhotoRaw are now available on the Apple App Store.

pcdMagic for Windows - the only currently available app that can convert Kodak Photo CD images with correct color and at full resolution - is now available on the Microsoft Windows Store.

This great news for users:

The Windows Store version has a free trial mode that allows the app to be tested without any commitment. The Windows store handles all updates automatically. There's no need to keep track of license codes. The Windows store only supports the latest versions of Windows 10.
2

As usual when new Leica cameras come out, I took a quick look inside a DNG from one of Leica's new Leica CL  cameras:

The camera name shows as "LEICA CL" The image data is 14-bit. There is no compression used in the DNG I looked at.  The DNG version is 1.4, with a "backward version" of 1.3. There is a reason for this - DNG 1.3 allows for opcodes, which Leica use for lens correction.
2

So finally, after many years of searching, I have an answer to the question that torments all who go down the digital color rabbit hole.

This is from XKCD, brought to my attention via an article on the Digital Transitions website about the Phase One IQ3 100mp Trichromatic.

Back in January, when the new Leica M10 was introduced, there were claims that the improvement in dynamic range from the Leica M240 to the M10 was of the order of 1.5 to 2 stops.  At the time, I wrote that just by eyeballing the published images, I believed the improvement to be "closer to 0.5 stops than 1.5-2".

Much to my surprise, given what I had thought to be just a basic explanation of why dynamic range is a tricky concept, the post generated a lot of push-back. And I mean a LOT.

dcpTool has been available for quite a while as a command line application for Windows and the Mac. But now it available in the form of an easy to use Mac app, with powerful batch processing capabilities. dcpTool for the Mac is available from the App Store.

dcpTool allows you to:

Decompile DNG Camera Profile (DCP) files in XML. The XML can then be read and edited with a simple text editor. Recompile edited XML into DCP files Remove "Hue twists" from camera profiles.
11

Many cameras embed lens corrections into raw the raw files that they produce. Generally, that's a good thing - straight lines stay straight, etc. For an example of lens corrections in practice, take a look at this post about the Leica SL.

But, as the saying goes, "there is no free lunch". Lens corrections also have some downsides:

Lens corrections result in a small reduction in sharpness.

Those of you that have read the Leica M10 raw file analysis post will know that M10 DNGs have more baggage in them that is typically the case for a Leica DNG. I've put together a little app to clean them up, called DNG Cleaner (Mac only for the moment).

AccuRaw users might have gotten a bit of a surprise recently - AccuRaw has turned into AccuRaw EXR, and is now at version 3.

The reason for the name change is that the focus of the AccuRaw product has changed a bit, based on what users were actually doing with it. AccuRaw has always been focussed on having highly linear color response, with no "hue twists" or other surprises in the color rendering.
1
Popular Posts
Blog Archive
About Me
About Me
My Photo
Author of AccuRaw, PhotoRaw, CornerFix, pcdMagic, pcdtojpeg, dcpTool, WinDat Opener and occasional photographer....
Loading