Skip to main content
Known Participant
April 27, 2015

P: TIFF file reloads after each Develop edit, potential data loss

  • April 27, 2015
  • 123 replies
  • 2749 views

LR6 (CC), edit TIF file (imported from PS or NIK). Image "reloads" after almost every Develop module edit. In some cases, all previous Develop module settings are lost, and the image reverts to it's original appearance. Even though the previous Develop module edits are still shown on the History panel - they no longer have any effect. Result - total loss of all user edits.

Workaround: disable "Automatically write changes to XMP" in catalog settings. This is what appears to trigger the constant "reloads".

Note this does not appear to be related to GPU - the problem occurs exactly the same whether GPU is enabled or disabled. Also note, the problem does NOT occur when editing RAW files. So far, it appears to occur only with TIF files.

Lightroom CC, 2015 Release
Windows 7, 64-bit, all latest updates
AMD Radeon HD 7700, latest AMD drivers

This topic has been closed for replies.

123 replies

Participating Frequently
May 8, 2015
"I'll just add here that if I bring the TIFF back from Silver Efex Pro 2 and try to make changes directly - like split toning, it will do the flash and throw the changes away. If I exit LR, come back in - I can then make the same changes attempted previously on the same TIFF without incident. If I repeat the same NIK action on the same RAW again, the next TIFF brought back will behave the same in the same LR session. There appears to be something session specific from my observations."

Is this also what other people on this thread are experiencing? If you quit and relaunch Lightroom, does the problem go away, for a given file?

-Ben
Participating Frequently
May 8, 2015
I'll just add here that if I bring the TIFF back from Silver Efex Pro 2 and try to make changes directly - like split toning, it will do the flash and throw the changes away. If I exit LR, come back in - I can then make the same changes attempted previously on the same TIFF without incident. If I repeat the same NIK action on the same RAW again, the next TIFF brought back will behave the same in the same LR session. There appears to be something session specific from my observations. I tend to not want to get in and out of LR for every file 🙂
Participating Frequently
May 8, 2015
Thanks, Richard, I've emailed you privately.
Participating Frequently
May 8, 2015
I thought I was responding to you - missed it by THAT MUCH.
I have a file for you in dropbox - not sure how to email you directly on this site.
Participating Frequently
May 8, 2015
ready
Participating Frequently
May 8, 2015
I'll give it a shot.
Participating Frequently
May 8, 2015
Hi All,

Obviously this is an issue, given the number of people who have reported the problem. Unfortunately, we've been unable to reproduce the problem internally. (As it turns out, Rikk was not actually able to reproduce exactly the problem described in this thread, although he has been able to reproduce a similar issue which may be related.)

In any case, if we can't reproduce the problem ourselves, it makes it very difficult to fix. So, I'm hoping some folks on this thread might be willing to help us track down the problem. We'd like to start by seeing if we can figure out whether or not the problem is specific to certain files. So, it would be great if someone could try the following:

1. In Lightroom, select a file that exhibits this problem.
2. Go to File>Export as Catalog...
3. In the Export as Catalog dialog, select the checkboxes for "Export selected photos only" and "Export negative files" (the status of the other two checkboxes shouldn't matter).
4. Open the newly created catalog. It should contain just the one file that you selected in step 1. Verify that you are still able to reproduce the problem in this new catalog (if auto-write XMP is necessary to cause the problem, make sure that auto-write XMP is turned on for this new catalog).
5. Assuming you can still reproduce the problem in this new catalog, upload the catalog, and its one image file, to a service such as Dropbox, and send me a link so that I can download it. Then I'll see if I'm able to reproduce the problem using your specific file and catalog.

If anyone is willing to try this out, let me know. I'll contact you privately so that you can email me a link directly, instead of posting it on the forum.

Thanks,
Ben
Rikk Flohr_Photography
Community Manager
May 6, 2015
I was able to repro this on my machine and have forwarded it to the team.
Rikk Flohr: Adobe Photography Org
Participating Frequently
May 5, 2015
I can confirm that this problem also occurs with TIFF file that come from Adobe's own Photoshop. So this is not a problem with third-party plugins (Nik in this case) but a general issue with the handling of TIFF files.
Participating Frequently
May 5, 2015
I'm glad to see an "Official Rep" (Rikk Flohr) is now adding comments to this thread. I hope we will hear soon that Adobe acknowledges there is a problem, and some update on the status of a fix. This isn't just an issue for those exporting to NIK software, or other 3rd party programs, either. I'm seeing it with tiffs edited in Photoshop CC as well.