Sun, Aug 23, 2020 1:51 AM
6 m ago
7 m ago
Updates for the Adobe Photography Products were officially released on 10.20.2020 that include fixes for these issues. Please install the most recent update and confirm that your issue is now fixed. Please let us know if you encounter any issues.
If you have large numbers of affected previously-edited images you can:
Thank you for your patience.
Quality Engineering - Customer Advocacy
Thanks for the update. I'm in the process of looking at the results now.
The problem now is that previous R5 images which I have applied an increase in exposure to compensate for the bug now appears overexposed when re-exported from Lightroom Classic 10. Luckily I do not have too many of them. R5 RAWs that were converted to DNGs prior to import into Lightroom do not seem to be affected.
When will adobe have camera matched profiles for the latest canon cameras .... can adobe please make a statement as to what the issue with this is? Thanks
@Rikk Thanks so much for this quick fix.
@Rikk Thanks Rikk, very useful to provide the retrospective steps to fix the malalignment.
This is my signature. There are many like it, but this one is mine.
9 m ago
Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)
8 m ago
When you open RAW files from the R and the R5 of the same image using Canons DPP the
exposures are fairly equal. When you open those two flies using LrC 9.4 the R5 files are about 1/2 a stop darker.
Yes, it can be adjusted in PP...
it seems like Adobe isn't accurately rendering the exposure on-screen and thus requiring additional adjustments.
I noticed that if I instead use a camera-generated JPG, the exposure retains that 1/2 to 2/3 stop greater brightness.
Of course, you lose the dynamic range benefits of the RAW file that way
I shoot raw because it has additional latitude over the JPG image, but the camera's rendition of what the final JPG will look like is very good.
@Rikk just wondering, has this been addressed in the latest release of Lightroom? Applying additional settings at import time isn't the end of the world, but would be great to get Lightroom's default rendering to be closer to that of the CR3 embedded previews.
It has but the solution breaks all existing edits brought over from v9.4 as they are now made brighter. So it's roll back to 9.4 until Adobe fixes the fix.
@Andy_Jones_SppThere isn't an additional fix planned. Images will need to be modified in Lr 10 if they were edited previously.
Apologies for this.
Sorry Rikk but it needs to be fixed because the behaviour of images brought over from v9.4 is unacceptable. When selected in the develop module they get brighter. When de-selected they darken again. This is only seen on R5 images.
@Rikk I've made a short video showing the effect in action. This is in the develop module, every time I switch image it first shows a darker (how it looked in v9.4 version) before jumping the brightness up for the v10 look. If it did this just the first time it wouldn't be so bad, sure we'd have to re-edit images, but the effect happens every single time I choose an image that came from v9.4, even after subsequent edits in v10. The library view also reverts to the darker version. Whilst it might fix the brightness issue from 9.4 the issues it introduces are severely affecting workflow.https://drive.google.com/file/d/1QAtjkRzKsOamhMOZGxU2zpVxSSEdr3gN/view?usp=sharing
Have you tried rebuilding your Preview Files in Library.
Yes, it makes no difference. Files imported into v9.4 just keep doing the flip between how they looks in 9.4 and the brighter v10 version.
Readjust the brightness. Zero effect on the actual data.
@andrew_rodney that's not the issue. Even if I fix the brightness I still see the image get darker again when it's not selected. Watch the video and you'll see the effect, there's no way I can find to stop the brightness only being correct when the image is selected in Dev.
The only way I can think to describe it is when LR detects a file from v9.4 it knows it should increase the brightness but then for whatever reason the fix isn't persistent.
What if you disable GPU?
Do so in the preferences. Any better?
If not, recalibrate and build a new ICC display profile, the old one might be corrupted.
If you are using software/hardware for this task, be sure the software is set to build a matrix not LUT profile, Version 2 not Version 4 profile.
If turning OFF GPU works, it's a GPU bug and you need to contact the manufacturer or find out if there's an updated driver for it.
See the Cache purge comments here: https://community.adobe.com/t5/lightroom-classic/r5-raw-pictures-turn-out-a-lot-brighter-in-lightroom-classic-10/td-p/11522079?page=1
@andrew_rodney this is only happening with R5 raw files so I can't see how it could be GPU or ICC profile specific.@Rikk bingo! Clearing the cache and deleting the previews folder seems to have sorted the issue, thank you.
Adobe’s default NR and detail settings are far less than ideal for most uses, even if they are scientifically more accurate.
The process to create a variable ISO preset (hacking a text file) is hardy a simple process.
Raw digger is lovely n all, but the in camera histogram is what people have to use on location
Although they are not 1990s blue chip ones obviously.
I knew you’d bite at “scientifically” my point was they are “rawest” -looking without being shockingly ugly.
At one time yes, no longer Ash; please read how this now works.
Thanks for that genuinely useful bit of information.
I just noticed a really annoying bug with LRC 10.0 : the brightness of my images is different when I look at them in the Library or Develop menu. In the library menu they are 1/3 f-stop darker. When I switch to the Develop menu, they are displayed with the same brightness at first, but after a few moments they become 1/3 f-stop brighter. This happens only with the CR3 files of my Canon EOS R5, with the CR2 files of my Canon EOS 5DSR, the brightness remains the same in both modules. Now, I don't know which display is correct and relevant for the output.
The issue was that LR classic 9.4 was rendering R5 RAWs underexposed by default. 10.0 does it correctly now but unfortunately the images you corrected manually in 9.4 are now re-rendered overexposed once you enter the Develop Module. I had to dial back the exposure in Develop but then the previews in Library will appear too dark. Rebuilding the previews in Library seems to solve this problem.
Note: In the official post I have included instructions to correct your previously edited photos,
@Rikk I missed that. Thanks!
How can we improve?
No tags available