Accurate Camera Colour within Lightroom

Obtaining accurate camera colour within Lightroom 5, in other words making the pics in your Lr Library look like they did on the back of the camera; is a problem that I’m asked about more and more since the advent of Lightroom 5 AND the latest camera marks – especially Nikon!

UPDATE NOTE: Please feel free to read this post THEN go HERE for a further post on achieving image NEUTRALITY in Lightroom 6/CC 2015

Does this problem look familiar?

Accurate Camera Colour within Lightroom

Back of the camera (left) to Lightroom (right) – click to enlarge.

The image looks fine (left) on the back of the camera, fine in the import dialogue box, and fine in the library module grid view UNTIL the previews have been created – then it looks like the image on the right.

I hear complaints that the colours are too saturated and the contrast has gone through the roof, the exposure has gone down etc etc.

All the visual descriptions are correct, but what’s responsible for the changes is mostly down to a shift in contrast.

Let’s have a closer look at the problem:

Accurate Camera Colour within Lightroom

Back of the camera (left) to Lightroom (right) – click to enlarge.

The increase in contrast has resulted in “choking” of the shadow detail under the wing of the Red Kite, loss of tonal separation in the darker mid tones, and a slight increase in the apparent luminance noise level – especially in that out-of-focus blue sky.

And of course, the other big side effect is an apparent increase in saturation.

You should all be aware of my saying that “Contrast Be Thine Enemy” by now – and so we’re hardly getting off to a good start with a situation like this are we…………

So how do we go about obtaining accurate camera colour within Lightroom?

Firstly, we need to understand just what’s going on inside the camera with regard to various settings, and what happens to those settings when we import the image into Lightroom.

Camera Settings & RAW files

Let’s consider all the various settings with regard to image control that we have in our cameras:

  • White Balance
  • Active D lighting
  • Picture Control – scene settings, sharpening etc:
  • Colour Space
  • Distortion Control
  • Vignette Control
  • High ISO NR
  • Focus Point/Group
  • Uncle Tom Cobbly & all…………..

All these are brought to bare to give us the post-view jpeg on the back of the camera.

And let’s not forget

  • Exif
  • IPTC

That post-view/review jpeg IS subjected to all the above image control settings, and is embedded in the RAW file; and the image control settings are recorded in what is called the raw file “header”.

It’s actually a lot more complex than that, with IFD & MakerNote tags and other “scrummy” tech stuff – see this ‘interesting’ article HERE – but don’t fall asleep!

If we ship the raw file to our camera manufacturers RAW file handler software such as Nikon CapNX then the embedded jpeg and the raw header data form the image preview.

However, to equip Lightroom with the ability to read headers from every digital camera on the planet would be physically impossible, and in my opinion, totally undesirable as it’s a far better raw handler than any proprietary offering from Nikon or Canon et al.

So, in a nutshell, Lightroom – and ACR – bin the embedded jpeg preview and ignore the raw file header, with the exception of white balance, together with Exif & IPTC data.

However, we still need to value the post jpeg on the camera because we use it to decide many things about exposure, DoF, focus point etc – so the impact of the various camera image settings upon that image have to be assessed.

Now here’s the thing about image control settings “in camera”.

For the most part they increase contrast, saturation and vibrancy – and as a consequence can DECREASE apparent DYNAMIC RANGE.  Now I’d rather have total control over the look and feel of my image rather than hand that control over to some poxy bit of cheap post-ASIC circuitry inside my camera.

So my recommendations are always the same – all in-camera ‘picture control’ type settings should be turned OFF; and those that can’t be turned off are set to LOW or NEUTRAL as applicable.

That way, when I view the post jpeg on the back of the camera I’m viewing the very best rendition possible of what the sensor has captured.

And it’s pointless having it any other way because when you’re shooting RAW then both Lightroom and Photoshop ACR ignore them anyway!

Accurate Camera Colour within Lightroom

So how do we obtain accurate camera colour within Lightroom?

We can begin to understand how to achieve accurate camera colour within Lightroom if we look at what happens when we import a raw file; and it’s really simple.

Lightroom needs to be “told” how to interpret the data in the raw file in order to render a viewable preview – let’s not forget folks, a raw file is NOT a visible image, just a matrix full of numbers.

In order to do this seemingly simple job Lightroom uses process version and camera calibration settings that ship inside it, telling it how to do the “initial process” of the image – if you like, it’s a default process setting.

And what do you think the default camera calibration setting is?

Accurate Camera Colour within Lightroom

The ‘contrasty’ result of the Lightroom Nikon D4 Adobe Standard camera profile.

Lightroom defaults to this displayed nomenclature “Adobe Standard” camera profile irrespective of what camera make and model the raw file is recorded by.

Importantly – you need to bare in mind that this ‘standard’ profile is camera-specific in its effect, even though the displayed name is the same when handling say D800E NEF files as it is when handling 1DX CR2 files, the background functionality is totally different and specific to the make and model of camera.

What it says on the tin is NOT what’s inside – so to speak!

So this “Adobe Standard” has as many differing effects on the overall image look as there are cameras that Lightroom supports – is it ever likely that some of them are a bit crap??!!

Some files, such as the Nikon D800 and Canon 5D3 raws seem to suffer very little if any change – in my experience at any rate – but as a D4 shooter this ‘glitch in the system’ drives me nuts.

But the walk-around is so damned easy it’s not worth stressing about:

  1. Bring said image into Lightroom (as above).
  2. Move the image to the DEVELOP module
  3. Go to the bottom settings panel – Camera Calibration.
  4. Select “Camera Neutral” from the drop-down menu:
    Accurate Camera Colour within Lightroom

    Change camera profile from ‘Adobe Standard’ to ‘Camera Neutral’ – see the difference!

    You can see that I’ve added a -25 contrast adjustment in the basics panel here too – you might not want to do that*

  5. Scoot over to the source panel side of the Lightroom GUI and open up the Presets Panel

    Accurate Camera Colour within Lightroom

    Open Presets Panel (indicated) and click the + sign to create a new preset.

  6. Give the new preset a name, and then check the Process Version and Calibration options (because of the -25 contrast adjustment I’ve added here the Contrast option is ticked).
  7. Click CREATE and the new “camera profile preset” will be stored in the USER PRESETS across ALL your Lightroom 5 catalogs.
  8. The next time you import RAW files you can ADD this preset as a DEVELOP SETTING in the import dialogue box:
    Accurate Camera Colour within Lightroom

    Choose new preset

    Accurate Camera Colour within Lightroom

    Begin the import

  9. Your images will now look like they did on the back of the camera (if you adopt my approach to camera settings at least!).

You can play around with this procedure as much as you like – I have quite a few presets for this “initial process” depending on a number of variables such as light quality and ISO used to name but two criteria (as you can see in the first image at 8. above).

The big thing I need you to understand is that the camera profile in the Camera Calibration panel of Lightroom acts merely as Lightroom’s own internal guide to the initial process settings it needs to apply to the raw file when generating it’s library module previews.

There’s nothing complicated, mysterious or sinister going on, and no changes are being made to your raw images – there’s nothing to change.

In fact, I don’t even bother switching to Camera Neutral half the time; I just do a rough initial process in the Develop module to negate the contrast in the image, and perhaps noise if I’ve been cranking the ISO a bit – then save that out as a preset.

Then again, there are occasions when I find switching to Camera Neutral is all that’s needed –  shooting low ISO wide angle landscapes when I’m using the full extent of the sensors dynamic range springs to mind.

But at least now you’ve got shots within your Lightroom library that look like they did on the back of the camera, and you haven’t got to start undoing the mess it’s made on import before you get on with the proper task at hand – processing – and keeping that contrast under control.

Some twat on a forum somewhere slagged this post off the other day saying that I was misleading folk into thinking that the shot on the back of the camera was “neutral” – WHAT A PRICK…………

All we are trying to do here is to make the image previews in Lr5 look like they did on the back of the camera – after all, it is this BACK OF CAMERA image that made us happy with the shot in the first place.

And by ‘neutralising’ the in-camera sharpening and colour/contrast picture control ramping the crappy ‘in camera’ jpeg is the best rendition we have of what the sensor saw while the shutter was open.

Yes, we are going to process the image and make it look even better, so our Lr5 preview starting point is somewhat irrelevant in the long run; but a lot of folk freak-out because Lr5 can make some really bad changes to the look of their images before they start.  All we are doing in this article is stopping Lr5 from making those unwanted changes.

Become a patron from as little as $1 per month, and help me produce more free content.

Patrons gain access to a variety of FREE rewards, discounts and bonuses.

8 thoughts on “Accurate Camera Colour within Lightroom

  1. So um, all the work I do to get my Nikon photos right in camera shouldn’t matter, since I can try and tweak Lightroom to make my photos look the same as in Nikon’s View NX2? I’m not asking that Lightroom 5 have available every camera profile for every camera. It is NOT demanding too much to expect Nikon and Canon profiles to be auto detected on import, and the thumbnails and previews be displayed without interference by Lightroom. If it is so hard to accurately display what’s on the back of the camera, then how come Photo Supreme 3 and Perfect Photo Suite 9 can do it without me having to tweak anything?
    Shame on Adobe

    • Hi Greg – all the Nikon and Canon profiles are detected, and listed in the camera profile drop-down menu; it’s just that Lightroom defaults to it’s own version, which I imagine to be some sort of bastardised hybrid – perhaps someone like Adobes Eric Chan might throw more light on this if you need it.

      A raw file isn’t “cooked” with the camera profile/picture control settings you have dialled into the camera – these are stored as side car files.

      Because of the nature of a raw file – gamma 1.0 – it is intrinsically a low contrast image with bags of mid and upper tone information.

      Apart from neutral, most camera profiles throw too much contrast into the image when it’s converted on the fly to gamma 2.2 – including the Adobe Standard profile for the D4, D800E, and to my eye, the Canon 1Dx and 5Dmk3.

      Contrast build-up is the constant enemy when you are processing – hence my tome on Correct Colour; increase contrast and you shift colours in saturation and quite often in hue as well.

      Having said that, the Adobe Standard always seems to give a fairly neutral rendering of an older D3 file for example.

      You can’t judge how an image looks from the crappy jpeg you see displayed on the back of the camera because that is effected by all the picture style settings in-camera, and the big visual constraint is it’s small screen size; if you shoot raw these are relatively meaningless anyway. If Lightroom was to read these and apply them to the image then you would have no real clue as to what’s been applied to the image because those settings would NOT show as slider adjustments in the Dev module.

      Far better to just keep the internal settings of the camera set to neutral, then import, neutralise hue/colour, take contrast to an acceptable level, banish chromatic aberration, then start to process from there – that’s the way I like to work anyway.

      i invariably teach a workflow that’s heading towards a printed output. You can’t print a black much below 20,20,20, and the brightest white in a print is paper white which is rarely above mid 240’s at best, so and shadow areas below 20, or highlights above 240 will be lost. The secret is to make the images have good contrast in the midtones while keeping the black and white points within that loosely 20 to 240 range. That style of processing approach gives you images that look good displayed in all mediums.

      So Greg, I tend to cuss Adobe for exactly the reasons you point out. While their errors have little to no effect on my own work flow ‘cos I just ignore/override the initial Lr default adjustments, what does annoy me is the fact that not everyone is as acutely aware of the visual impact of these profile errors, so Adobe should do something about it.

  2. Great article. As a recent adopter of LR5 I have been really struggling with a large batch of D200 RAW files and the different rendition between LR vs View NX2. As an LR newbie I am really struggling to get the images to look good in LR when logic states it should be possible, it’s just a combination of sliders. One quick specific question. Should the WB value show the same in View NX2 as it does in LR because it doesn’t in mine! Many thanks, Steve

    • Hi Steve

      View NX always shows you the recorded white balance, Lightroom by default displays white balance simply as “As Shot”.

      In theory the image should look the same in both applications, but in practise that won’t be the case because of the manner in which they interpret the raw data.

      White balance in camera is something I never worry about – I just set all my cameras to “Cloudy B1” and shoot. If I need critically accurate colour/white balance I include a ColorChecker Passport in a test shot once exposure is sorted.

      Lenses effect recorded colour, as does your ISO setting so together with the fickle vagaries of light they all conspire to make a critically accurate white balance setting in camera something of a moving target – so why bother trying!
      The beauty of shooting RAW is that nothing is “committed” and so fine tuning of white balance is best done at the processing stage.

      Cloudy B1, a modification of the general “Cloudy” camera WB setting, makes a good “knock about” setting so that the preview jpegs on the back of the camera look OK.

      • Hi Andrew,

        Many thanks for your response and your advice. I will persevere with Lightroom for now. it’s a pity that Adobe didn’t make a better job of D200 profiles but I guess it is a good learning experience – even if it does drive me mad and I hit that reset button a lot! A lot of the images I am currently working on were taken in the Grand Canyon, Monument Valley and Bryce Canyon where the colours are particularly difficult to get right.

        Moving forward I have just purchased a D750. Adobe have made a much better job of the profile and a change from Adobe Standard to Camera Standard gets things just about right.

        Steve

  3. I have a D3 and lately have been very unhappy with the final quality of my images using Lightroom 5.

    On reading your blog and installing the Nikon D2X Modes (using Mode 3 right now) the quality of images has improved to a point where I am now happy again as they look the way I intended them to.

    I also found that I’d gotten into a bad habit of increasing the contrast too much which in itself was spoiling the images. It was one of those things that I’d just let happen over a period of time and wasn’t aware of how it was degrading the image.

    I now have contrast at ‘0’ and just use the Tone Curve to give Medium Contrast.

    Thank you for putting me back onto track; it’s very much appreciated… 🙂

Add your comments and feedback

This site uses Akismet to reduce spam. Learn how your comment data is processed.