Edit in Photoshop not working properly

Inspiring

The worst part is that this has been a known issue for many months. It's nearly impossible to get anyone from Adobe to respond, and they have not addressed it. When you call Adobe support, they either aren't aware of it, or if they are, they tell you to enable Rosetta in both Lightroom and Photoshop (if you're on a Mac). That seems to help sometimes but the results are still inconsistent for me. It's absurd that a company as large as Adobe, with as many resources as it has, can't fix this issue after almost a year. Their software simply isn't working as advertised—it's not like we're doing anything crazy here, we're trying to do a very simple thing that Adobe says should be possible.

P

Peter Kremmer

Participating Frequently

Ok, but at least I know, that its not that I am doing something wrong.
Oh... and I also have the message when I close Lightroom hours later, thats its in the process of getting the file back from Photoshop, but the process never completes.
Anyway, I hope it gets sorted soon.. it did work just fine before Photoshop update

Inspiring

I am experiencing the exact same issue that the OP described, only in my case, it is with all images—color, B&W, RAW, JPEG, etc.

What's more, the same thing is happening in my case that @Jim Wilde described: when I hit "Command-S" for save, it acts as if I am doing "Save As...": I see a dialog box asking me which compression options to choose, etc. This never happened before.

Here is the process I'm following exactly:

Select image in Lightroom
Choose File > Edit in Photoshop
Perform edits in Photoshop
Choose File > Save or "Command-S"
Close the file

When I get back to LR, the image is nowhere to be found. However, I can open it again in Photoshop. It appears under the "Recent" heading on the Photoshop splash screen.

Any ideas?

I

interesting_work5C99

Participating Frequently

Same issue.

https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-bugs/p-image-does-not-return-from-photoshop-to-my-lightroom-desktop-catalog/idi-p/12593368

Inspiring

I just noticed that the initial report of this problem is now an "acknowledged bug":

I'm very glad to hear this.

yann_seznecAuthor

Participating Frequently

I've still not had any solution for this, anyone else running into this issue?

JohanElzenga

Correct answer

Community Expert

I looked at your video again and I suddenly noticed something that may be the cause. Lightroom normally works with RGB files, but the file you are sending to and saving from Photoshop is greyscale. I wonder if that has something to do with it. Try again with a color photo and see if that behaves differently. If it does, then this may be a bug and should be reported in the Bugs section.

-- Johan W. Elzenga

yann_seznecAuthor

Participating Frequently

oh wow, ok, something of a breakthrough here: it seems like this is actually only happening with some photos!

As you suggested, I checked to see if it was happening with color photos and sure enough it was editing and saving in Photoshop as I expected (not asking me for a save location, and updating the edits in Lightroom). Then, just to be double sure, I picked another B&W photo to try and it also worked! So, it turns out that this is happening for a handful of different photos, all of which were the ones that I was initially testing 😄

I haven't yet worked out what it is that characterizes the photos that won't edit in Photoshop correctly, but if I figure it out I'll post here.

Thanks for the clue, it really helped!

yann_seznecAuthor

Participating Frequently

Here's a video showing the issue in action, starting with attempting to File->Save and save it locally, followed by attempting to close the file and save to the cloud.

Jim Wilde

Community Expert

What I don't understand from your video is why, when you use the "Save" command, PS initiates the "Save As" process instead. On my setup, when I use "Save" there is no dialog box at all, the Tiff is saved automatically (there's a save progress bar at the bottom of the screen), and it appears in Lightroom as soon as I close the saved image in PS.

I don't know PS well enough to figure this out, hopefully someone with more experience will be able to help.

yann_seznecAuthor

Participating Frequently

yes! that's the behaviour I would expect too, it certainly worked that way on my last computer...

Jim Wilde

Community Expert

When you have finished editing in PS, the image needs to be closed in PS, not just saved. You can either save then close, or close first and it will ask that you save.....regardless, the Tiff does not return to Lr until it has been closed as well as saved in PS.

yann_seznecAuthor

Participating Frequently

Hi, thanks for your response.

However this doesn't seem to make a difference for me - when I save the edits in Photoshop (locally or on the cloud) and close Photoshop the edits never appear in Lightroom.

JohanElzenga

Community Expert

You should not save the photo 'somewhere', but in the cloud.

-- Johan W. Elzenga

yann_seznecAuthor

Participating Frequently

Thanks for your answer - however this makes no difference in my case. When I save the edits from photoshop to the cloud there is no update to the photo in Lightroom.

Furthermore, am I wrong in thinking that this workflow is different from what it used to be? Previously I never had to choose a save location at all, locally or on the cloud, I could just "save" in Photoshop and the edited version would appear in Lightroom.

yann_seznecAuthor

Participating Frequently

has no one else had this issue?

G

Giannivegas

Participant

Im having this issue currently. Was there ever a fix. I working with and HDR iamge stack and a flash shot blending them together. It is also not pulling them back into lightroom. Acutally, Sometiems it does pull it back in and sometims it doesnt. Takes significantly longer to edit things now. I also tried uninstalling and reinstalling the apps. Same thing. Any guesses? I also bought a new MacBook and dont know if that was the issue or if the issue was when i downloaded the apps it was the newest firmware and THAT is the issue.