Skip to main content
Inspiring
October 21, 2020
Answered

Edit in Photoshop no longer includes Lightroom adjustments

  • October 21, 2020
  • 13 replies
  • 6807 views

Hi! I just upgraded to Lightroom Classic 10 (for Mac OS) and suddently Lightroom adjustments aren't  applyed when sending a file to Photoshop using "edit in Photoshop". Specifically, the profile I've applied in Lightroom is removed and replaced with the regular Adobe color profile. Has anyone else seen this? Is there a solution? I'm on Mac OS 10.15.7.

This topic has been closed for replies.
Correct answer hertze

So, after looking at this, Adobe's engineering team concluded that this is an intermittent issue affecting Mac users. They're working on a patch to be pushed out with a future update. Until then they simply suggested rolling back to the previous version. 

13 replies

gregb13536095
Participant
September 30, 2021

Hi its not just Mac users...when i work in lightroom and then click to open in photoshop none of the editing work i have done in lightroom is on the image when it opens in photoshop

Participant
October 8, 2021

+1 Same here.
I think this is happening again since from the last update on Mac.

Community Expert
March 29, 2021

If (for whatever reason) a profile which does work for Lightroom Classic, does not work for ACR on the way into Photoshop: there is a workaround.

 

You can take ACR out of the picture by having Lightroom Classic itself complete the job and save result as a file (that is immediately imported to LrC). Then PS opens this directly ready for any further editing and resaving. You can tell the difference because the title of the PS document already shows a TIFF / PSD filename; it does not still reflect the Raw source's filename, as it would when still unsaved to disk.

 

An external editing preset bypasses the normal route via ACR: it "forces" the Render-by-Lightroom method.

 

Just as, when a non-compatible ACR version is detected; or, with any editor app other than Photoshop. 

sageb62028076
Participant
March 29, 2021

Try right clicking on the image > Metadata > Save Metadata.

This is what FINALLY worked for me!

noellenchris
Participating Frequently
March 29, 2021

Yes, I think I got it to work again by not changing the Metadata / keywords on import.  I will try it again with saving the Metadata.  Thanks!

 

Participant
February 2, 2021

Hi there , 

same issue for me using Big Sur . 

"creative profiles with lookup tables in them are not applied correctly when using the Edit in Photoshop command"

really hope they come with a fix soon !

 

 

noellenchris
Participating Frequently
December 13, 2020

Same issue here on Windows.  I've been troubleshooting it for hours today.  I also have the Canon R5 and using a custom profile from Color Fidelity as Adobe has not updated theirs for the R5 yet.  Well, at least I can take a break from troubleshooting it as others seem to have the same issue and Adobe is aware.  

noellenchris
Participating Frequently
December 13, 2020

Ok, I changed the Profile in LR to the stock Adobe Standard from my sync'd CF Standard and it works as it did before.  Hope they get this fixed or update the Canon R5 color profile.

 

noellenchris
Participating Frequently
December 13, 2020

Disregard using default profile.  I was wrong.

aminphoto
Participating Frequently
November 21, 2020

Im having this same issue, but on Windows

Participant
December 13, 2020

Im having the same issue on mac now. It just started and it's ruining my workflow. Has there been any update adressing this issue or is it still a work in progress?

 

hertzeAuthor
Inspiring
December 13, 2020

As far as I know, the issue persists. The most popular workaround seems to be to save the metadata with the file (cmc+s on a Mac, so ctrl+s on windows?). It works as long as you don't want to treat different versions in PS.

hertzeAuthorCorrect answer
Inspiring
October 24, 2020

So, after looking at this, Adobe's engineering team concluded that this is an intermittent issue affecting Mac users. They're working on a patch to be pushed out with a future update. Until then they simply suggested rolling back to the previous version. 

JohanElzenga
Community Expert
Community Expert
October 24, 2020

The previous version of what? Lightroom Classic? Photoshop? ACR? All three? As you have upgraded your catalog you cannot simply go back to Lightroom Classic 9, because that means you would also have to go back to your pre-upgrade catalog (and lose what you have done since the upgrade). I would rather use the workaround with smart objects that I suggested and you confirmed can be used (by switching to another profile and back in ACR)...

 

-- Johan W. Elzenga
hertzeAuthor
Inspiring
October 24, 2020

The suggestion was to roll back LrC to version 9. It would be feasible in my case--I still have the v.9 catalog and haven't done any critical work since upgrading (I had been warned about this particular issue, but hoped it wasn't a bug but something fixable on the user end). I will take another route, and simply not use roundtripping to PS as part of my workflow. 

JohanElzenga
Community Expert
Community Expert
October 22, 2020

Try this: instead of using Edit in Photoshop, use the menu further down to open the image in Photoshop as a smart object. Then you can open the smart object in Camera Raw by double clicking the layer. Camera Raw should show you the exact same edits as you applied in Lightroom, so it should become more obvious what is going on.

 

-- Johan W. Elzenga
hertzeAuthor
Inspiring
October 22, 2020

Ok, I've tried what you suggested, but the issue is the same. The BW photo is what it looks like in LrC, the color one how it opens. It looks the same (color) when I open the smart object in ACR.

It seems Adobe is aware of the issue and is investigating, but support had no work-around for now.

hertzeAuthor
Inspiring
October 23, 2020

So double-click on the smart object and check what's missing in Camera Raw compared to Lightroom. If it's just the profile that didn't come over, then this is a workaround you can use until Adobe solves this: Open as smart object, open the smart object in Camera Raw and apply the profile. Done. You can flatten the image if you no longer want the smart object.

 


@JohanElzenga It seems only the profile is different (all adjustments look the same), but there're still subtle differences in color when I (re)apply the profile in question. Weird! Thank you for your suggestion, though. For the moment I'll simply use a workflow not involving roungtripping images to PS. 

Just Shoot Me
Legend
October 22, 2020

With all your replies you have noth bothered showing us Screen Shots of what you are actually taking about.

 

That would help to either Solve your problem, Which I think doesn't really exist, or show you where you have things confused. See my other Recent Reply to your post about "I should Add, Adobe RAW Profiles work for me".

 

https://community.adobe.com/t5/lightroom-classic/edit-in-photoshop-no-longer-includes-lightroom-adjustments/m-p/11529453#M208105

 

 

You are confusing Camera Profiles and Color profile and Presets.

hertzeAuthor
Inspiring
October 22, 2020

Ok, this is what the image looks like in LrC:

and this is how it looks in Photoshop immediately after clicking "Edit in Lightroom":

JohanElzenga
Community Expert
Community Expert
October 22, 2020

This is normal. When you edit in Photoshop, a new RGB file is created and sent back to Lightroom. Lightroom will 'start from scratch' with this new RGB file. All the edits you made on the image before it was sent to Photoshop are 'baked into the pixels' of the new image, including the choice of profile. Because the returned file is a TIFF or PSD, not a raw file, you also do not get the choice of raw profiles for this image. This is nothing new for Lightroom Classic 10, by the way. It has always been this way.

 

-- Johan W. Elzenga
hertzeAuthor
Inspiring
October 22, 2020

Yes, but now the profile is no longer baked into the dng when sent over to PS. This is new (for me, and a few others it seems) since upgrading. 

Just Shoot Me
Legend
October 22, 2020

Ps can't actually open DNG files and when Ps returns either a PSD ot TIF image all of the Edits you have done to the DNG file are Baked Into that New file.