Lightroom: Changes in Lightroom Develop Module do not appear in Library Module

  • 1
  • Problem
  • Updated 7 years ago
  • (Edited)
I imported (converting to DNG) a recent photo shoot into Lightroom as usual (Lightroom 3.4.1, Mac OS 10.6.7). I went into the Develop module, and made some edits. When I went back to the Library module, the edits don't appear. When I go back to the Develop module, they display. I'd done this with multiple photos in that import, with the same results. If I do the same thing (Library->Develop->apply edits->Library) on a previous import, it works as it always has. The problem only seems to be with the most recent imports.

I always test integrity/optimize/backup the library on exit, which doesn't seem to help

The only change that I had made between imports that "worked" and the ones the exhibited this behavior, was an upgrade from LR 3.4 to 3.4.1.

I tried creating a new catalog, and then importing the folder containing the newly imported images into the new catalog. I found the same behavior in the new catalog. I also tried deleting the folder from Lightroom and then reimpoting it. No change. I also deleted the photos from Lightroom, and the disk, then reimported them to the disk and Lightroom. No change. I also tried deleting the photos from the catalog and reimporting them without converting to DNG (as NEF). Still the same behavior.

When I reinstalled Lightroom 3.4, everything reverted to working correctly.
Photo of Eric Feigenson

Eric Feigenson

  • 4 Posts
  • 0 Reply Likes
  • annoyed

Posted 7 years ago

  • 1
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
If you're game, try reinstalling Lr 3.4.1 again and see if the problem returns. My theory is that there was an install problem, not a version problem.
Photo of Eric Feigenson

Eric Feigenson

  • 4 Posts
  • 0 Reply Likes
I reinstalled 3.4.1 and... the problem returns! Back to 3.4 and it goes away.

Good suggestion though!
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
I'm surprised. This is the first I've heard of this problem.
Photo of Eric Feigenson

Eric Feigenson

  • 4 Posts
  • 0 Reply Likes
It does seem to be very strange. Is there any other information I can get that will help track this down?

Thanks!
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 379 Reply Likes
I'm out of ideas - maybe somebody else can help...
Photo of Mark Sirota

Mark Sirota

  • 146 Posts
  • 29 Reply Likes
Since it seems that you can reliably reproduce this, the next step is to minimize it as much as possible -- can you do it with a single image?

Since it appears to be related to previews, does it happen if the newly created catalog and associated previews are on a different disk?

Once you've got it minimized, the next step is to post the recipe for others to try to reproduce, possibly including your original image file(s) if that turns out to be important.
Photo of Eric Feigenson

Eric Feigenson

  • 4 Posts
  • 0 Reply Likes
Good ideas... I'll get on that when time permits

Thanks!
Photo of Benjamin Warde

Benjamin Warde, Employee

  • 483 Posts
  • 72 Reply Likes
It sounds like it might be a problem with previews. I would suggest throwing out the previews file to see if that fixes it. By default, the previews file is called "Lightroom 3 Catalog Previews.lrdata" and is located in the Lightroom folder in your Pictures folder. If you named your Lightroom catalog something else, or put it somewhere else, the name or location of the previews file may be different than what I've described here.

Quit Lightroom. Move "Lightroom 3 Catalog Previews.lrdata" to the trash (or desktop - that way you can put it back later if you wish to for any reason). Relaunch Lightroom. This will force Lightroom to regenerate previews for all files, which may solve the problem.

-Ben