Lightroom 4.2 RC seems don't keep rendered preview

  • 1
  • Problem
  • Updated 6 years ago
Hello,

I have a little feedback about the new 4.2 RC, is seems that LR does not keep the 1:1 preview as mentionned in the settings.

My settings actually tells LR to keep 1:1 preview 30 days, yesterday I work on new imported photo, All 1:1 have been created at this time. In library looking a photo at 100% is fast and direct.

Today, I wake up the PC, I restart LR, want to look again at my work and all photos need a preview rendering : bad quality at 100%, loading message, cpu at 100%, waiting for the full quality view...you know.

Am I missed something or doing something wrong ? Is this, is a bug ?
Photo of Alban LEROUX

Alban LEROUX

  • 48 Posts
  • 0 Reply Likes
  • undecided

Posted 6 years ago

  • 1
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2632 Posts
  • 337 Reply Likes
The previews are for reviewing images quickly in Library mode.

In Develop things are always re-rendered from the current settings because in Develop you're there to change the settings...unless LR has just shown you the image and knows the settings haven't been changed.

Sometimes I wish it worked differently, too, on my slower computer.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
If the library previews were rendered, but got re-rendered without any change to develop settings, then you're being bit by a bug. Try deleting the previews, in case it's a data sensitive bug ( ... Previews.lrdata folder).

Note: If you *did* change develop settings, even if via Quick Develop, then the library previews *will* need to be re-rendered/"loaded" - that's normal.
Photo of Alban LEROUX

Alban LEROUX

  • 48 Posts
  • 0 Reply Likes
Yes, there is absolutely no change to developer settings. I'll delete previews, test and keep you aware.
Photo of Alban LEROUX

Alban LEROUX

  • 48 Posts
  • 0 Reply Likes
It seems I'm not able to reproduce the problem. However, my preview folder will be very heavy (more than 10 Go, 30 000 files) and win 7 64 failed to delete it completly in one pass. Is possible some file were corrupted ? Is it possible a lack of inode can cause this problem (did win not fail to run in this case or warn before it happens?) ?
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
|> "win 7 64 failed to delete it completly in one pass"

Maybe your hard drive is starting to fail. - consider running a disk diagnostic like chkdsk.
Photo of Alban LEROUX

Alban LEROUX

  • 48 Posts
  • 0 Reply Likes
I will, thanks for the advise Rob ! I think it's certainly time to close this thread now...