Skip to main content
Inspiring
May 5, 2022
Question

Behavior when moving between Lightroom and Photoshop

  • May 5, 2022
  • 2 replies
  • 1304 views

PC, windows 11 pro, current Lightroom and Photoshop versions.

This came up in a Lightroom class I've been involved in, and I'm not sure what's actually happening.

 

Open RAW in Lightroom, do processing, Edit in Photoshop.

Photoshop opens, image shows up, add an adjustment layer, make changes, do SAVE.

Back in Lightroom, psd file shows up, can see the changes made in PS.

 

Make changes in Lightroom, and Edit in Photoshop - this time "Select Original" to preserve the layers.

Over in Photoshop, the image I'd originally opened from Lightroom is sitting there, and a popup that says "The disk copy of xxx.psd was changed since you last opened or saved it.  Do you wish to update it?"  Select "Update".

What SHOULD happen at this point?  I can't see the changes I made in Lightroom (normal), but they SHOULD be applied automatically when I get BACK to Lightroom, right?

 

Make MORE changes to the open file in Photoshop - This time add a pattern to the image.  So another layer.  Do Save.

Back in Lightroom, my changes from Photoshop show up, BUT the changes made in Lightroom before the second visit to Photoshop, DON'T. 

I tried selecting "Cancel" in response to the question about updating the disk copy.  Same result when I got back to Lightroom.

 

SO FAR, the only way I've been able to get the multiple-round-trips to work is to CLOSE the file in Photoshop every time I go back to Lightroom.  As long as I DO that, I don't see the Lightroom changes in Photoshop, which is normal, but I DO see them when I get back to Lightroom.

 

I DON'T recall having to do this in the past.  It seems to me that I was always able to leave the image OPEN in Photoshop, and keep going back and forth between Lightroom and Photoshop without any problem.  Is the current behavior a change, a setting I may have wrong, something due to Windows 11, or has it ALWAYS worked this way and I'm completely off-base?

 

This topic has been closed for replies.

2 replies

TheDigitalDog
Inspiring
May 5, 2022

To add, you can catalog layered images in LR but as soon as you try editing them there, it's all happening on a flattened 'version' so to speak which is again why I also agree, don't round trip from LR to PS after you've applied edits, certainly on layers in PS. Catalog them, print them, all fine. Draw a line in the sand when you are done parametric (instruction) based editing in LR or ACR, then pixel edit selectively in PS on layers etc, then you're done with all processing in LR/ACR. 

Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
Inspiring
May 6, 2022

I generally DON'T do multiple round trips.  But, it does happen, and thus, the question was asked. 

 

So, can someone answer the original question about handling the situation when it does occur? 

Is it necessary to close the image in Photoshop prior to editing the "Original" again?

And for those who DO make more than one trip to Photoshop, do you use Edit a Copy or stay with Edit Original?

Inspiring
May 9, 2022

I have seen other forum posts in the past where inconsistencies occur with the LrC<>Ps workflow, but I have no answers other than suggestions.

Have you tried-

1) To [Close] the image in Photoshop after each time you [Save]?  (Don't "Delete" or do you mean "Close" Ctrl+W?)  This means that LrC will always be opening/sending a 'saved' version of its "original" Ps (TIF,PSD) file.

2) After a return of the Ps image to LrC- Have you tried clicking/selecting the last edit shown in the Develop History panel?

eg. This should have recovered the first  -3 Exposure setting you tried.

 

You are going against common advice that advises to only [edit-in] Ps as the last step in editing workflow.

You may be better to [Open as a Smart Object] so that you have easy access to ACR adjustments within Photoshop, 

thus eliminating repeated jumps LrC<>Ps.

 

 


I have seen other forum posts in the past where inconsistencies occur with the LrC<>Ps workflow, but I have no answers other than suggestions.

Have you tried-

1) To [Close] the image in Photoshop after each time you [Save]? (Don't "Delete" or do you mean "Close" Ctrl+W?) This means that LrC will always be opening/sending a 'saved' version of its "original" Ps (TIF,PSD) file.

 

Yes.  Until about 30 minutes ago when I hit your question 2.  Until then, closing the image in Photoshop was the ONLY way I'd found to ensure changes are reflected by Lightroom when the psd gets back. 

 

I HAVE noticed some things don't work the same in Windows 11, or my system configuration, or my Lightroom configuration OR SOMETHING - Auto Sync for example, DOESN'T change the non-active images until I move the mouse. There are other differences too, but I don't know which part of the mess is causing the oddities.

 

After a return of the Ps image to LrC- Have you tried clicking/selecting the last edit shown in the Develop History panel?

eg. This should have recovered the first -3 Exposure setting you tried.

 

Unbelievable...  I just mentioned that other operations require me to do some kind of mouse hokey-pokey...  This time when I got back to Lightroom and NOTHING got updated I looked at the history.  Everything is SITTING in there.  BUT, I tried going back one step, nothing.  So I went to the BOTTOM - the import, clicked it, THEN jumped to the LAST line of the history, clicked and VOILA, Lightroom updated.

 

I'll have to try the same thing on the laptop to see if it acts the same way or not.  If not, it's something screwy on my desktop.

Thanks for pointing me in the right direction...  It's still WEIRD, but it's a better weird than it was.

 

D Fosse
Community Expert
Community Expert
May 5, 2022

The underlying problem is that Lightroom doesn't support layers and can't read them.

 

But if you have Photoshop set to "maximize compatibility", Photoshop will insert a flattened composite layer in the file, and this is what Lightroom reads and makes adjustments to.

 

I'm not going into all the potential ramifications of repeated roundtrips, but understanding this basic mechanism makes it easier to follow what actually happens.

 

Personally, I'm deeply skeptical to the whole concept of roundtripping between these two apps, because they operate so differently. I never do it (and frankly, I don't see why it would ever be necessary). Once the raw file is edited in Lightroom, the RGB file goes to Photoshop and all further RGB editing happens there. I know some people do go back and forth, and are apparently comfortable with it, but it clearly requires strict discipline.

 

If the Lightroom controls are needed on the RGB file, I use the ACR filter, which accomplishes exactly the same thing.