N

4 Messages

 • 

160 Points

Wed, Oct 21, 2020 2:20 PM

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

[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... 

Responses

4 Messages

 • 

90 Points

6 m ago

Today Photoshop 2021 update to 22.0.1.73

this version fix it?

38 Messages

 • 

438 Points

@cyfoto I just installed and tried it and the problem is still there.  I think the issue is in Adobe Camera Raw, so I am hoping that the next update of that component will resolve?

Champion

 • 

5.8K Messages

 • 

101K Points

6 m ago

It appears this bug is limited to creative profiles (.xmp) using LUTs.  I can't reproduce the problem with creative profiles that just use develop settings, and I and Andrew can't reproduce the problem using custom camera profiles (.dcp).

 

Apparently, when you edit a raw with a LUT creative profile in PS, and there is no .xmp sidecar, the LUT is getting dropped on the floor.  Perhaps this is a bug in the hidden mechanism by which LR passes develop settings to PS when there isn't a sidecar.

 

The example DNG posted by @dprosk involves a creative profile with a LUT. Here's what the relevant internal LR develop settings look like:

CameraProfile = "Base Profile V4", 
Look = {--table: 2
    ...
    CameraModelRestriction = "Canon EOS R5", 
    Name = "CF Landscape V4", 
    Parameters = {--table: 3
        CameraProfile = "Base Profile V4", 
        ...
        RGBTable = "5F18C8C737DCE48D81659D934F9C9D35", 

Champion

 • 

5.8K Messages

 • 

101K Points

Thinking a little more about this, almost certainly the LUT is getting dropped on the floor unless there's a .xmp sidecar.

When there's a creative-profile LUT, the .xmp sidecar contains the actual encoded LUT, e.g.

crs:Table_43CE5AF1D6EC3B3338CDB7A0CB099BA6="Lir00.ks!*{EZHy|E35{f2.M{CyyQaOV:pl#x]zq*gVp2BMFuBD(2{nYG$WKWHQ#prLX0+kTr-QTh$'nQ=NtnM{%'ns.?Kq|16/Q`MmF5R:3(yOp4UVDGxEfpAerO2f*6KB-1t/Rt03}^+kLt9D-8)8riaqNzqN[gC4n%H'^ThDC4Fd6p]
...

But internally, LR's develop settings just contain a reference to the LUT, which is cached in the Camera Raw engine:

RGBTable = "5F18C8C737DCE48D81659D934F9C9D35"

LR must be passing just the reference to the cached LUT, not the contents of the LUT (unless there's a sidecar).  If PS has been freshly started, it won't have the LUT in its cache.  But if you first open the raw directly in PS, it will have the LUT in its cache, and when you later edit the raw from LR, PS will find the LUT in its cache.

2.1K Messages

 • 

25.1K Points

So no issues using DNG?

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

Champion

 • 

5.8K Messages

 • 

101K Points

I can't replicate the problem with DNGs. DNGs contain their develop settings in an XMP metadata section in the file (just like TIFFs and JPEGs), the same XMP contents as would be in a sidecar. I confirmed with @dprosk's DNG that it contains the actual LUT, not a reference, just like a .xmp sidecar.

2.1K Messages

 • 

25.1K Points

DNGs contain their develop settings in an XMP metadata section in the file (just like TIFFs and JPEGs)

Exactly and probably why I can't replicate since I'm just working with DNGs. So in the meantime, converting to DNG could be the fix. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

38 Messages

 • 

438 Points

Exporting to DNG and opening into PS (through ACR) definitely works.  Multiple workarounds exist:

  • Downgrade to ACR v12.4
  • Save metadata (.xmp) prior to "Edit in PhotoShop 2021"
  • Use "Open as Smart Object in PhotoShop" then double-click on layer
  • Export as DNG, open the DNG in PhotoShop

That said, the issue in ACR should still be fixed so that "Edit in PhotoShop 2021" works as expected and as it used to.  My preferred workaround until the issue is resolved is the save metadata just prior to editing in PhotoShop.  But hopefully I won't have to use it for long!

Thanks @John_R_Ellis for the thorough analysis!

4 Messages

 • 

90 Points

6 m ago

I am having the same problem.
I am using custom profiles, which I have created and using for the last 2-3 years.
After finishing globla editing on lightroom I am pressing CTRL+E to edit the photo on photoshop, but unfortunately the profile is disappearing.
I tried checking "Automatically Write Changes Into XMP" without success.
Below you can find my sytem info on both lightroom anf photoshop

Stavros Habakis 
visual storyteller



36 Vouliagmenis St, Hellinikon
16777, Greece
t: +30 210 9600988
m: +30 694 5551000
e: info@stavroshabakis.com
 
stavroshabakis.com

Champion

 • 

5.8K Messages

 • 

101K Points

Are these camera profiles (ending with .dcp) or creative profiles (ending with .xmp)?

Also, let us know if any of these additional workarounds help:

https://feedback.photoshop.com/conversations/lightroom-classic/lightroom-classic-editing-raw-file-in-ps-from-lr-loses-profile/5f9043b035f40c2520b9e964 

8 Messages

 • 

130 Points

6 m ago

Hi everyone.

Problem solved for me by updating Photoshop to the latest version as at 17-November-2020

Custom and 3rd party Profiles now carry over if you use the Edit in Photoshop option from Lightroom Classic.

Photoshop version: 22.0.1

Camera Raw Version: 13.0.2
OS Verison: Windows 10 20H2 (build 19042.630)

Champion

 • 

3.5K Messages

 • 

59.5K Points

Interesting. This error is not listed as solved, and when I quickly tried it yesterday I found it was not solved. That was on a Mac, however.

(edited)

Johan W. Elzenga,

http://www.johanfoto.com

Champion

 • 

5.8K Messages

 • 

101K Points

The bug recipe still provokes the bug on my LR 10.0 / PS 22.0.1 / Windows 10.

@koketso, perhaps you could upload one of your custom profiles to Dropbox or similar and post the sharing link here? We can see if the issue happens on other installations with your profile.

8 Messages

 • 

130 Points

@koketso 

Update on my working solution:

This seems to now work in conjunction with XMP sidecar files on.

It previously didn't even with XMP files on - and I can confirm the XMP was being written but Photoshop was not reading it or not reading it correctly. Again, only happened with .CR3 files.

Here is a profile for testing: https://mega.nz/file/GdpiiBpR#d0cPt45T5WjyfUF7DfZkT3th8EoY3J9jUFQDBKu9ZLQ

cc @JohanElzenga @John_R_Ellis 

Champion

 • 

3.5K Messages

 • 

59.5K Points

I see the bug on all types of raw files, not just on .CR3. Saving metadata to file before you send the image to Photoshop does indeed seem to work. 

Johan W. Elzenga,

http://www.johanfoto.com

Champion

 • 

5.8K Messages

 • 

101K Points

@koketso , using the profile you uploaded (Evanous 01), I was able to reproduce the bug with both PS 22.0.0 and 22.0.1, and doing Metadata > Save To File avoided the bug with both versions too. 

3 Messages

 • 

80 Points

Hi John,

I am still experiencing the same issues that was discussed above. I am on the latest LR and PS which were updated a week ago. 3rd party profiles are not going across.

Appreciate any suggestions. 

Regards

Satya

(edited)

3 Messages

 • 

80 Points

I tested the edit in into other external editors and the transfer worked fine with the 3rd party profile embedded. Hence I think the issue is the handshake transfer between lightroom and photoshop only.

Waiting for lightroom to write the xmp files. before testing. Its taking a long time as I have a lot of photos.

Hope that Adobe find a long term solution instead of a work-around.

(edited)

7 Messages

 • 

132 Points

1 m ago

When sending an image to PS for editing 3rd party develop profiles are being ignored. 

I've tested this on an Intel based Mac running OSX Mojave and a M1 Mac running Big Sur. The problem is the same so not OS or Architecture related.

When applying a develop profile (Adobe Color, Adobe Landscape, Adobe Vived etc) and then sending the image to PS for editing the profile is ignored unless the profile is one that shipped with LR. ie I can apply any profile from Adobe, Modern, Vintage, B&W and the profile is honoured when sent to PS. If I apply a 3rd party profile from say On1 or 3rd party film emulation profiles of my 3rd party camera profiles then these profiles are ignored. 

I can export the image to any file format with 3rd party profiles and that works perfectly, I can send an image to Luminar, NIK collection etc with a 3rd party profile and that works perfectly but when sending to PS, the profile is ignored. 

I suspect that the issue has manifested itself when Adobe changed the way images are sent to PS. Previously a PSD of TIF file would be generated and then that file was sent to PS for editing. Recently a TIF or PSD is not generated and the file format displayed when the image opens in PS is the raw format eg. CR2 or CR3. 

I have created a video which shows the issues which you can find here

https://www.youtube.com/watch?v=ezlyqkAsGMk

I have no idea if this issue persists in Windows machines as I do not have access to one. 

Note: This comment was created from a merged conversation originally titled Profile issue when sending image to PS for editing from Lightroom

2.1K Messages

 • 

25.1K Points

There is a known issue with LUTs in some presets. 

Author “Color Management for Photographers" & "Photoshop CC Color Management" (pluralsight.com)

7 Messages

 • 

132 Points

@andrew_rodney If this is the case, it's a pity the support staff don't know about it. I spend 20 minutes on a live chat with some idiot telling me it's the 3rd party developers fault. Then sent me an email about colour spaces.  

Champion

 • 

5.8K Messages

 • 

101K Points

Adobe customer support has a reputation for saying anything to close a call when they don't know the answer, unfortunately.

7 Messages

 • 

132 Points

1 m ago

I've just discovered this bug too and actually reported in in a separate thread before finding this one. It seems that Adobe are forcing us into a lot of "work-arounds" just lately. It's unacceptable!

3 Messages

 • 

80 Points

Hi,

after reporting it above and then had Adobe call me. yep, definitely an issue with transfer of 3rd party profiles. The work around mentioned in this forum works. LR takes a while to create the xmp files. Other option is to right click the photo you intent to transfer clicking - metadata- save metadata to file/ update DNG preview. 

Support said he would make a note. not sure if anything will happen

2 Messages

 • 

122 Points

17 d ago

When opening an image in Photoshop, from the "edit in Photoshop" command in LR Classic, the image is grossly oversaturated. However, if I first export the image as a PSD file, then open that file in PS, it matches the look in LR. Up to date on both LR and PS. Working on a Mac, with Mojave OS. Have not changed any of my preferences in either program. Problem just appeared today, after a lifetime of always matching. Any suggestions?

Note: This comment was created from a merged conversation originally titled Lightroom Classic: Images opened in Photoshop, directly from "edit in Photoshop" command are way too saturated!

George Simian

1.1K Messages

 • 

12K Points

With my limited experience opening images from Lightroom, I get the best results by opening as layers. I just use it for focus stacking and experimenting with Super Resolution but I don't experience your problem. I'm using Windows, not sure that matters and I only send raw images to Photoshop.

For MacOS, make sure you are on 11.2 or newer or pre-11.0.

Champion

 • 

3.5K Messages

 • 

59.5K Points

Did you apply a custom camera profile to this image? There is a bug in Lightroom/Photoshop that such a profile is not applied when using Edit in Photoshop. Search for it here in the forum; there should be a very long thread including some work around suggestions. I don’t think that bug is fixed yet.

Johan W. Elzenga,

http://www.johanfoto.com

Adobe Administrator

 • 

10.2K Messages

 • 

137.2K Points

This thread is being merged into an existing authoritative thread for better tracking and response. Please review the official answer (if any) in the second post on the thread for more information. 

Adobe Photography Products

Quality Engineering - Customer Advocacy

953 Messages

 • 

14.4K Points

17 d ago

Je teste ce 21 avril 2021 - macOS 11.2.3 LrC 10.2 PS 13.2

SI le profile est appliqué depuis LrC, et un fichier .xmp existe ou est créé, ce profile n'est pas enregistré dans le .xmp, donc si on uvre le RAW directement avec PS, donc recherche des paramètres dans le .xmp ce profile ne pourra pas être appliqué puisque celui-ci ne sera pas enregistré ou mal reproduit dans le .xmp
Après ces km d'explications, vois la situation résumée en quelques lignes, merci de corriger ceci dans une proche prochaine version !

8 Messages

 • 

130 Points

5 d ago

Aaaaand we're back to where we began - this time even with XMP files saved next to their raw files (Catalog Settings > Metadata > "Include Develop settings...")

"Edit in Photoshop" does not carry over the Profile, even though the profile can be selected from both Lr and ACR.

Photoshop 22.3.1
ACR 13.2

Lightroom Classic 10.2
Windows 10 20H2

Champion

 • 

5.8K Messages

 • 

101K Points

I just tested the workaround with LR 10.2 / PS 22.3.1, and it works for me.

Note that the setting Catalog Settings > Metadata > Include Develop Settings In Metadata doesn't ensure that a photo's most recent metadata is saved to the file or .xmp sidecar.  It just specifies that whenever metadata is saved, the Develop settings will be included.

To ensure the most recent metadata is saved before editing in PS, do Metadata > Save Metadata To File or set Catalog Settings > Metadata > Automatically Write Changes Into XMP.

(edited)