Lightroom: Losing adjustments after re-open in PS

  • 5
  • Problem
  • Updated 2 years ago
  • Acknowledged
  • (Edited)
Hi everybody.

I have just noticed the following issue:

1) I do first development in LR, open the photo in PS and do Black/White conversion. Save and close it.

2) Adjust few sliders, add vignette and Export the photo.

3) Check the exported photo, see some small issues which need to be fixed in PS, open the photo in PS, fix everything I need, save and close it.

4) When the photo being updated in LR, all the previous changes I have done (I mean really all, including adjustment brushes, etc.) will be gone, regardless that they are listen in History list. I need to click on the last item prior to Export operation. Only then all previous operations will be restored.

See the attached screenshots.
Photo of Alexey Soloviev

Alexey Soloviev

  • 11 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 5
Photo of Rikk Flohr

Rikk Flohr, Champion

  • 1359 Posts
  • 318 Reply Likes
This is a known issue and a bug report has been filed. No ETA yet on a fix.

As a workaround, I save a Snapshot of the image before sending it back to PS a second time. That way, I can reapply it as soon as it comes back into Lightroom.
Photo of Alexey Soloviev

Alexey Soloviev

  • 11 Posts
  • 0 Reply Likes
Thank you Rikk for your reply. Even if I restart the LR, and re-open a photo in PS, still LR loose all adjustments. That is absolutely sucks! Hope that will be fixed soon.
Photo of Gerald amEnde

Gerald amEnde

  • 2 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Lightroom CC Local Adjustments Lost after returning from Photoshop CC Edit.

I have an TIFF image with local adjustments in Lightroom.

1) Edit in Photoshop CC 2015...
2) Edit Original
3) Make some changes and return to LR
4) Local adjustments are lost even though they appear in history.

Tried GPU on/off to no effect.

This appears to be the same problem detailed here: (and claims to be fixed.)

Below is my system info.


Lightroom version: CC 2015.3 [ 1052427 ]
License: Creative Cloud
Operating system: Windows 10
Version: 10.0
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 2.3 GHz
Built-in memory: 16104.2 MB
Real memory available to Lightroom: 16104.2 MB
Real memory used by Lightroom: 1411.9 MB (8.7%)
Virtual memory used by Lightroom: 1847.4 MB
Memory cache size: 576.4 MB
Maximum thread count used by Camera Raw: 8
Camera Raw SIMD optimization: SSE2,AVX,AVX2
System DPI setting: 120 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:
GeForce GT 750M/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 359.00
Renderer: GeForce GT 750M/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler

Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: C:\Users\Jerry\Pictures\Lightroom\Lightroom Catalog.lrcat
Settings Folder: C:\Users\Jerry\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) Canon Print Studio Pro
2) Canon Tether Plugin
3) Facebook
4) Flickr
5) HDR Efex Pro 2
6) Leica Tether Plugin
7) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : fe4
Subsystem : 380117aa
Revision : a1
Video Memory : 1992
Adapter #2: Vendor : 8086
Device : 416
Subsystem : 380117aa
Revision : 6
Video Memory : 70
Adapter #3: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
Direct2DEnabled: false
GPUDevice: not available
OGLEnabled: true
Photo of Nico Kaiser

Nico Kaiser

  • 22 Posts
  • 0 Reply Likes
And i always thought this was by design...

Going back in history to the last export point is the first thing i do after additional changes to the original file...

Would be great to have a fix here!
Photo of Alexey Soloviev

Alexey Soloviev

  • 11 Posts
  • 0 Reply Likes
Hi Niko. I believe this issue has appeared in last LR Update ... or maybe 2 updates ago. Before that was possible to do changes in LR with a TIFF file without loosing anything while opening it many times in PS - was no problems at all. Hope the fix will come soon.
Photo of mikerolls75


  • 2 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Lightroom: Edits on TIFFs are lost after editing in Photoshop.

A bit convoluted.. After editing an image in PS from LR the TIFF is created in the Lightroom Collection. Any LR changes I now make to this TIFF are then lost if I subsequently edit it in Photoshop. Why?
I'm told in Photoshop I need to save it from PS as a different name, or edit with LR changes when going to Photoshop. This makes no sense at all, whiy don't the Lightroom edits remain on the TIFF after PS edits?
(Hope this makes sense)
Photo of Josef Kissinger

Josef Kissinger

  • 7 Posts
  • 0 Reply Likes
This reply was created from a merged topic originally titled Lightroom: When I Edit In Photoshop, then save it, Lightroom edits get reset.

Here are some example photos. First i make an edit in lightroom. Any edit. In this case i burned the corners and the center.

Next i open it in photoshop:

I do some adjusting in photoshop. In this case i added some text, flattened the image, and then saved over the original jpeg:

Back in lightoom you can see that my original edits are gone. THe corners and the center of the image are no longer burned. Now look at the history. Its not selected:

Now when i select the history, it shows back up:

This process of having to select the history every time has really slowed down my workflow. Can this bug be fixed soon? Thanks.
Photo of Alexey Soloviev

Alexey Soloviev

  • 11 Posts
  • 0 Reply Likes
Hey guys. 

I've got some help regarding this issue - if I activate the option "Automatically write changes into XMP", then all works as it should be. But that is just a work-around, problem still exists and still need to be fixed!

Photo of Richard Wahlstedt

Richard Wahlstedt

  • 4 Posts
  • 0 Reply Likes
I can confirm that this works for me