Skip to main content
Inspiring
October 21, 2020

P: Lightroom Classic: Editing raw file in PS from LR loses profile

  • October 21, 2020
  • 146 replies
  • 4309 views

[See here for how to reproduce the bug and an easy workaround:

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-editing-cr3-files-in-ps-from-lr-lose-color-profile/5f9043b035f40c2520b9e964?commentId=5fb3495d014b4c3c8a0da305 -- John Ellis]

 

Editing a picture in Photoshop 2021 from within LR 10.0 makes the color profile disappear and the image loses all it's vibrancy... Any idea how to fix that? Top image is what I see in LR. Bottom is how it shows up in Photoshop... 

This topic has been closed for replies.

146 replies

Participating Frequently
November 12, 2020

Left image - Lightroom, Canon R5 photo, CRAW CR3, Third party color profile applied

Middle image - Photoshop "Edit in Photoshop 2021" from LR, note that color profile is gone, color profile not visible in ACR, importing color profile fails saying it is already loaded.

Right image - Photoshop "Open as Smart Object in Photoshop", double clicking layer to enter ACR does show the color profile as being present, along with other third party profiles that are loaded in Lightroom

What's going on with ACR?  It never used to do this...



TheDigitalDog
Inspiring
November 12, 2020

*ricardomoura What version of LR? There was an issue in older versions rendering newer CR3 files, it's been fixed. If you still see this in the latest version, does it change if you disable GPU in preferences? 

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
Participating Frequently
November 12, 2020

And a further update...the problem is BACK with the most recent Camera Raw update as of a couple of days ago.  The Johan workaround still works for a single image, but no longer "solves" the problem for subsequent images.  Something is definitely going on with the ACR component in PhotoShop.

Inspiring
November 12, 2020

I noticed the following related issue.

When importing CR3 file (from Canon EOS R5) to LR I apply a custom profile (but also happens with Adobe) and when shifting from Develop module to Library the histogram increase about 1-stop... The exported JPEG files also do not match my editing. You can notice the exposition variation on this LQ gif below.

I don't see this issue with CR3 from EOS R camera files.

Inspiring
November 12, 2020

I have exactly the same issue - and I "solved" it by downgrading to camera raw V12. So from my pov it should be an issue with the actual camera raw version. 

Inspiring
November 7, 2020

@Rikk hello sir, any information that this kind of "bug" will be fix with the next update?

Inspiring
November 7, 2020

Hmm... after research it for awhile. Lightroom default should have saved the settings to catalogue. The option "Automatically write changes into XMP" should be used only if you want to share the RAW file to someone and the setting along with it.

For normally workflow like LR > PS, should leave it uncheck for better performance.
And this must be the Photoshop 2021 "bug" or something, because i test with PS 2020 there's no problem with custom camera profile...

Inspiring
November 7, 2020

YES!!! Thank you. It worked like it supposed to be.
But i wonder if that auto write to xmp then when i open the raw file in other application, will it auto apply the setting as well...

Participant
November 7, 2020

I find that by selecting 'Automatically write changes into XMP' in 'Catalog Settings' in Lightroom, the color profile works when exporting to Photoshop

Inspiring
November 7, 2020

Hello - whenever I edit a picture in LR 10 and I use a custom color profile (NOT the adobe standard profiles) and parse the picture to PS 22.0.0 with "Edit in ...", the picture has lost the color profile completely. The first pic was graded with a custom color profile only and after "Edit in Photoshop 2012" the picture shows up as you can see in the second pic.

The only workaround that helps right now, is to downgrade camera raw to V12 - but this can't be the answer for long. Any idea or solution?