Adobe have just released a new update for Lightroom CC2015 & Lightroom 6.
This update is of particular relevance to Nikon users who were suffering with the missing lens data information I posted about previously.
The new update is touted as fixing the problem, and it certainly does so for new imports from what I can see. But for images that are already in your catalogue and are showing the “unknown lens” tag in your metadata and filter bar, you are going to need to do a bit of extra work!
Adding the update does NOT fix the existing issue! WTF……….??
So here is how to FIX the problem.
Open your catalogue Library Module in Lightroom CC2015.5.1 or 6.5.1
Click on All Photographs in your Catalogue Panel (top left below Navigator)
Hit the backslash ( \ ) key to bring up your filter bar
Select All Dates together with All Cameras & All Lenses, and select the Unknown Lens category
Head up to the contextual menu and go Select All – all cells should now be highlighted
Go to Metadata in the contextual menu and select Save Metadata to Files
Go back to Metadata in the contextual menu and select Read Metadata from Files
Once you click READ you will see your images sequentially vanish from the selected UNKNOWN LENS view as Lightroom updates its metadata records.
HOWEVER – this does NOT work with ANY Virtual Copies, Proof Copies or video files that you have within said catalogue.
To correct these, you have to make new virtual copies, then select the old ones and copy all Develop Settings from the old ones to the new ones! And don’t ask me what you do with video files because I can’t work that one out.
What a bloody carve-up!
If you want the official instructions from Adobe they are HERE
Creative Cloud subscribers should also take the new Photoshop CC 2015 update – this adds camera support and fixes to CameraRAW.
On a lighter note the new update has also added new camera support for the Pentax K1 and Sony DSCRX10M3
We all know how good Lightroom is – but it’s also a total pain in the arse!
Ages ago, I did a post about Lightroom 5 and accurate colour HERE and, according to this blogs page-view stats, that post still gets a large global viewing figure every month – so it’s something of an on-going problem for a lot of users.
But things have moved on a bit since then, and we are now working with the v5 release of Lightroom 6/CC 2015 – and things haven’t got any better, sadly, from the perspective of actually “seeing what you captured”.
The problem lies in the fact that Lightroom, for a long time, ceased to be a “neutral” RAW handler. It uses a variety of ‘behind the scenes’ algorithms to add what it thinks are good adjustments in terms of exposure brightness and contrast. In other words Lightroom adds hidden adjustments which we cannot see because they are not registered on the adjustment sliders under process version 2012.
Why does it do this – God only knows!
But when I take into account the support Lightroom currently offers for mobile phone cameras, cloud synch etc, I can’t help thinking that Adobe are trying to give Lightroom some sort of mass-market appeal by adding what the designers and coders think is some sort of WOW-factor to image previews – though I might be wrong!
But whatever Adobes reasoning, the fact remains that SOME OF US want to see our raw files for what they are – straight gamma 2.2 encoded versions of what the sensor recorded. Only by learning how to Neutralise Hidden Exposure Compensation can we actually arrive at a suitable starting point for the development process.
The Case To Answer
Firstly, a lot of you might be wondering WTF I’m ranting on about – your RAW image previews look great before you start doing anything to them – mmmmm….
If that’s the case then NEWS FLASH – RAW files should look as flat as dish-water pre-process, and you have do some work to make them look good. So believe me, if your raws look “nice ‘n punchy” from the get-go then something is wrong somewhere!
Out there in photography land there are two RAW file handlers that are notorious for being “neutral” in their initial raw render – Raw Digger, and Iridient Developer.
Let me demonstrate the “case to answer” by using the same image I used the other day when giving Canon an indirect slagging off over lossless compression:
Raw file opened in Lightroom with no user adjustments BUT WITH Lightroom ‘hidden exposure compensation’.
Now let’s open the same file in Raw Digger:
Raw file opened in Raw Digger with no user adjustments.
And now in Iridient Developer:
Raw file opened in Iridient Developer with no user adjustments.
And now, just for good measure, my Lightroom-processed version of the image:
Raw file processed in Lightroom WITH user adjustments.
Both RAW Digger and Iridient Developer give the user a much better processing start point simply because they are neutral and don’t go about making contrast-loaded ‘background adjustments’. And I’m sure you can see that the final Lightroom processed version of the image bares more resemblance to the RAW Digger and Iridient screen grabs than the Lightroom ‘as is’ preview.
Now if you are a total maniac then you can go and download either of the two aforementioned raw developers and get yourself super-confused or you can learn how to ‘neutralise’ the Lightroom background adjustment ‘crap’ – which is far easier!
How to Neutralise Hidden Exposure Compensation in Lightroom.
Step 1. Scroll down to the Camera Calibration Panel in the Develop module and switch the Process Version from PV2012 to PV 2010:
Step 1 in Neutralising Lightroom Hidden Exposure Compensation.
Step 2. Scroll up to the Basics panel (a very different looking one if you never used Lightroom 3!) and make the following changes:
Blacks from 5 to 0
Brightness from +50 to 0
Contrast from +25 to 0
Step 2 in Neutralising Lightroom Hidden Exposure Compensation.
Step 3. Move to the Tone Curve and change the Medium Contrast tone curve to Linear:
Step 3 in Neutralising Lightroom Hidden Exposure Compensation.
DO NOT concern yourself with the fact that your image has gone dark and flat, it’s to be expected!
Step 4. Scroll back down to Camera Calibration and switch the process version BACK to PV2012, then scroll back up to the Basics Panel:
Step 4 in Neutralising Lightroom Hidden Exposure Compensation.
Step 5. Yes I know it still looks awful, but if you now change that -1EV to 0 on the exposure slider you’ll get a great process start image:
Step 5 in Neutralising Lightroom Hidden Exposure Compensation.
Looking at the before and after images you can see that we have got contrast under control – in other words we have removed the excess contrast added to the image with the Lightroom hidden background shenanigans.
Indeed, we can see exactly how much contrast has been removed with this ‘by the numbers’ process by looking at the -33 Contrast value – DO NOT RESET THIS BACK TO 0!!!!
The process has decreased contrast still further by lifting the Blacks value to +25. You need to check the shadow areas on the image in this respect. If they are looking a bit noisy (Hello Canon!) you might want to drop the blacks value to maybe +5 to +10 and open the shadows a bit more with a small positive adjustment to the Shadows slider in the basics panel.
And so processing is just a matter of a few subjective tweaks until I’m happy with the image:
Click to view larger image.
In the Tone Curve panel you can see the multi-point Custom Curve the process has added. If you click the up/down arrows to the right of the word Custom you will see a menu giving you the option to save the curve:
Saving the custom curve.
I save the curve with the name 2010to2012 – by default it saves as an .xmp file, and to the user/Library/Application Support/Adobe/CameraRaw/Curves file path (Mac).
Saving the curve is useful as it makes for a very quick adjustment of further images.
However, there is a caveat (isn’t there always!) and it’s this:
The majority of adjustments in Lightroom are specific to camera sensor and ISO. In simple terms the same numeric value of adjustment to any control slider can have differing effects depending on the sensor it was made by and the ISO at which it was shot. It’s very important that you wrap your head around this fact.
The curve I’ve produced here is correct for a Canon 1DX at the shot ISO which was 1000 or 800 if my memory serves correctly. I could apply this curve to a 100 ISO image shot with a Nikon D800E, and it would do a good job, but I might get a slightly better result if I go through the whole process again to produce a custom curve for the D800E using a 100 ISO shot to begin with. But even if that new curve visually gives a different result it will still have the same numeric values in the basics panel!
If I save the curve and then apply it to another image via the Tone Curve panel the contrast and blacks Basic Panel values do NOT change – but you will get a better distribution of contrast.
You may want to generate and save at least a low and high ISO variant of the curve for each of your camera bodies; or you could be a smart-arse like me by just using one curve and eye-balling the finer tweaks.
You can also create the curve and then save the settings as a User Develop Preset and then apply it to future imports via the import module.
So there you have it, how to Neutralise Hidden Exposure Compensation in Lightroom and see you images properly – have fun folks!
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.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.