Skip to main content
Adobe Photoshop Family

9 Messages

 • 

526 Points

Mon, Apr 27, 2015 10:14 PM

Solved

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

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

Responses

3 Messages

 • 

90 Points

5 years ago

This reply was created from a merged topic originally titled Lightroom 6/CC and Nik Color Efex 4.

When exporting an image to Color Efex 4 from Lightroom the outgoing process is fine with a TIFF copy FILE created
When reimporting it back to Lightroom however any adjustments made in Lightroom thereafter keep being cancelled out. The screen flashes and the image reverts back to the state it was reimported in from Color Efex.
i have tried the same images in Lightroom 5 with no problems so clearly there is some issue with the processing of images in Lightroom 6.
Any ideas or similar problems found?

1 Message

 • 

60 Points

5 years ago

same problem for me following edit in Color efex. Every time I use the adjustment brush the screen refreshes and all brush strokes are lost.

2 Messages

 • 

70 Points

5 years ago

Same issue here with re-imports from Nik plugin. It was fixed in LR5, please lets get it fixed again.

8 Messages

 • 

140 Points

5 years ago

Me too, though it's intermittent for me. On the other hand, I am unable to edit the new HDR images in Viveza, Dfine, or either of the two sharpening programs. Get a message the the file could not be opened because it contains transparency information. Extremely disappointing and frustrating!

Adobe Administrator

 • 

8.2K Messages

 • 

117.4K Points

I don't think Google (Nik) is supporting 32 bit Tiffs yet.
 

Adobe Photography Products

Quality Engineering - Customer Advocacy

10 Messages

 • 

150 Points

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.

Adobe Administrator

 • 

8.2K Messages

 • 

117.4K Points

5 years ago

I was able to repro this on my machine and have forwarded it to the team.
 

Adobe Photography Products

Quality Engineering - Customer Advocacy

Employee

 • 

474 Messages

 • 

10.7K Points

5 years ago

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

43 Messages

 • 

686 Points

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.

43 Messages

 • 

686 Points

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 :)

43 Messages

 • 

686 Points

5 years ago

I'll give it a shot.

43 Messages

 • 

686 Points

ready

Employee

 • 

474 Messages

 • 

10.7K Points

Thanks, Richard, I've emailed you privately.

Employee

 • 

474 Messages

 • 

10.7K Points

5 years ago

"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

10 Messages

 • 

150 Points

5 years ago

The problem seems slightly different, depending on where the tiff file originates. I haven't tried it with any of the NIK software, but what happens with me is as follows:

1. Select a tiff file in Lightroom CC to edit in Photoshop CC.
2. Select "Edit a copy."
3. Make any changes in Photoshop and save.
4. Enter the Develop module in Lightroom and make any changes to the "-Edit" copy of the file that was just worked on in Photoshop. A few seconds after making the change, the image reloads, BUT, I don't lose the change I just made.
5. If I close and reopen Lightroom, the reload behavior stops for that file.

So apparently you get half the problem (image reloading) if the file is worked on in Photoshop, but not the worse half of the problem (losing Lightroom edits) as seems to happen if the tiff is worked on in some 3rd party software.

9 Messages

 • 

190 Points

5 years ago

Yes, Same problem. On Tiffs and will even sometimes reset things in History Like Spot Removal I made 10 steps previous. I do have Sidecars set on so will turn off till fixed

23 Messages

 • 

300 Points

5 years ago

Glad Adobe is working on this. It's VERY frustrating trying to edit. Having the same problems everyone else is having. My LR even changed from current version to a previous version after a slider move. ugh!

33 Messages

 • 

492 Points

5 years ago

Just want to add my case to the list. I'm having the exact same problem...flashes with tiff files and all edits lost (even though they still show up in history). It is VERY frustrating and basically unusable as is.

I'm glad adobe is looking at it. I don't understand how they can't duplicate it. I wonder if it has to do with the upgrade to older catalogs that they don't have. I upgraded directly from lightroom5 to lr-cc.

7 Messages

 • 

130 Points

I thought I'll give that a try, so I just created a brand new catalog and imported a few photos. Unfortunately it shows the same issue when auto-write XMP is turned on.

33 Messages

 • 

492 Points

Too bad that didn't work. Thanks for trying. I hope Adobe figures this one out. Weird that they can't duplicate it when so many of us have the problem, and a lot of different systems.

For the record I'm on an imac, OSX 10.9.5, with 8 GB of ram and an AMD Radeon HD 6970M 1024 MB GPU. (I see the problem with and without the gpu support, as others have seen).

23 Messages

 • 

300 Points

5 years ago

This reply was created from a merged topic originally titled Annoying refreshing in Lightroom 6 CC.

I'm running the latest version on my 27 inch IMac. Ever since my download of Lr 6CC I'm having problems in the develop module. I use Lr 6 CC as my base upload from my camera. When I take a photo out of Lr and export it to photoshop or other program and make adjustments then, bring it back to Lr, anytime I use a slider ( any slider) Lr screen turns grey for a moment as if to be refreshing. Sometimes nullifying any adjustments I make. I have turned off CPU and still does the same thing. I contacted Adobe support the other night and a tech took remote control of my Mac and made some adjustments. It didn't fix the problem though. It never did this in Lr 5. I'm a subscriber and this is very annoying. Do you have a fix? I would hate to go back and use Lr 5 but, at least 5 has no bugs. Thanks. Larry

10 Messages

 • 

150 Points

Welcome to the club, Larry. The only reliable work-around for this so far is to turn off "Automatically write changes into XMP" in the Catalog Settings/Metadata dialog. We are all waiting for a permanent fix to the problem.

23 Messages

 • 

300 Points

Thanks Joel, yeah I did that. Works fine like that but, don't like the idea of shutting off XMP. Hope Adobe gets a fix soon.

Employee

 • 

474 Messages

 • 

10.7K Points

5 years ago

I'm still hoping to get some info from folks on this thread. Specifically, if you quit and relaunch Lightroom, does the problem go away for a given file? I've got info from two people so far confirming that after they quit and relaunch, the problem no longer occurs with existing files (though it will still occur with new files). It would be helpful to know if that is the case, or not, for everyone who is experiencing this problem.

Thanks,
Ben

Employee

 • 

474 Messages

 • 

10.7K Points

5 years ago

Hi All,

Update: I am still not able to reproduce this using Photoshop, but I am able to reproduce it using NIK software. I've passed this info along to the Lightroom engineers. I'll update this forum thread as I get more info.

Thanks,
Ben

23 Messages

 • 

300 Points

Thanks a ton Ben. Glad you were able to see what all the fuss is about.