Lightroom Classic: Can't see Develop adjustments after I delete other images

  • 1
  • Problem
  • Updated 3 weeks ago
  • (Edited)
Using LR Classic 7.5.

While working in the develop module, after I delete some images from the catalog, I can then no longer see the effect of develop settings on the remaining images and cant see changes I make being made, although the settings are applied and are visible after a program restart. The only solution is to restart the program to get normal functionality.

Behavior is only visible in Classic 7.5.
Photo of Chris Hitchcock

Chris Hitchcock

  • 4 Posts
  • 1 Reply Like

Posted 3 weeks ago

  • 1
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4379 Posts
  • 1602 Reply Likes
Which OS Christopher?
Photo of Chris Hitchcock

Chris Hitchcock

  • 4 Posts
  • 1 Reply Like
Windows 10 Home.

Photo of Tom Mickow

Tom Mickow

  • 300 Posts
  • 100 Reply Likes
I've experienced that behavior myself, although I never associated it with the step of image deletion.

I've had a number of instances where I'm working in Develop and suddenly the previews stop updating.  I'm able to move all the sliders, but they show no effect on the screen.  Moving back & forth between Library & Develop and zooming in to 1:1 & out does nothing to change the displayed previews.  Manually discarding & rebuilding 1:1 or standard sized previews does nothing to change the displayed previews.  The only thing I've found that works is to close & reopen Lr.  Then I see the updated previews with the adjustments applied.

I'll have to pay more attention the next time it comes up to see if I happen to be deleting images before the problem occurs.

Lr Classic CC 7.5 - Win10 - NVidia GPU currently on, but I'm pretty sure I've seen the behavior with it off too.

Lightroom Classic version: 7.5 [ 1186149 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Enterprise Edition
Version: 10.0.17134
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 2.7 GHz
Built-in memory: 16375.2 MB
Real memory available to Lightroom: 16375.2 MB
Real memory used by Lightroom: 1236.5 MB (7.5%)
Virtual memory used by Lightroom: 1004.1 MB
GDI objects count: 735
USER objects count: 2460
Process handles count: 1842
Memory cache size: 227.3MB
Internal Camera Raw revision: 1001
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2
Camera Raw virtual memory: 211MB / 8187MB (2%)
Camera Raw real memory: 211MB / 16375MB (1%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1200, 2) 1920x1200
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No
Graphics Processor Info:
OpenGL: GeForce GTX 960/PCIe/SSE2
Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 399.07
Renderer: GeForce GTX 960/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler
Total Video Memory: 2048 MB


Photo of John R. Ellis

John R. Ellis, Champion

  • 3780 Posts
  • 988 Reply Likes
"While working in the develop module, after I delete some images from the catalog, I can then no longer see the effect of develop settings on the remaining images and cant see changes I make being made, although the settings are applied and are visible after a program restart. "

By "no longer see the effect", do you mean in the Library thumbnails and Loupe view, or in Develop, or both?

If it's just Library you can't see the effect, try selecting the recalcitrant thumbnails in Library and doing Library > Previews > Build Standard-Size Previews. Do they now show the effect?  Obviously, you shouldn't have to do this, but the outcome could help narrow down the problem.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3780 Posts
  • 988 Reply Likes
And if it's just Develop (and not Library), try disabling the option Preferences > Performance > Use Graphics Processor.
Photo of Chris Hitchcock

Chris Hitchcock

  • 4 Posts
  • 1 Reply Like
It's both develop and library modules. It also makes no difference if I use the graphics processor or not.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3780 Posts
  • 988 Reply Likes
Some more troubleshooting steps:

- Update your graphics driver by going directly to the manufacturer's Web site (more up-to-date than Windows update): 
https://helpx.adobe.com/lightroom/kb/lightroom-gpu-faq.html#main-pars_header_2

- See if your display profile is corrupted or incompatible.  Windows has a nasty habit of silently replacing your current profile with one that won't work with LR.  This is less likely to be the cause but easy to test:
http://www.lightroomqueen.com/articles-page/how-do-i-change-my-monitor-profile-to-check-whether-its-...

- Reset LR's preferences (another less-likely but easy to test): 
https://www.lightroomqueen.com/articles-page/how-do-i-reset-lightrooms-preferences/

Photo of Chris Hitchcock

Chris Hitchcock

  • 4 Posts
  • 1 Reply Like
The display drivers work fine until I delete images in the catalogue. They still work fine after I delete the images, they just don't show the develop changes to the files. Restarting LR (not the PC) solves the issue which indicates the issue is with LR and not the display drivers.
Photo of John R. Ellis

John R. Ellis, Champion

  • 3771 Posts
  • 985 Reply Likes
There are other reports on these forums of graphics drivers failing on subsequent images but not the first.  LR pushes the envelope with respect to graphics drivers and hardware and often trips over bugs in manufacturer's drivers.  It's not hard to imagine a bug in a driver that reports wrong or confusing information to LR that causes its subsequent use of the driver to fail.
Photo of Pavan Kumar

Pavan Kumar

  • 6 Posts
  • 0 Reply Likes
Hi, 

I have tried a few workflows on Win10. I deleted('remove' and 'delete from disk' operations both) a few pictures from develop and library module and tried editing other images. Edits are getting applied on the images properly. Looks like I am missing something important here. Could you attach a video so that it will be easy for us to reproduce this issue?

Thanks,
Pavan Kumar
Adobe Lightroom team
(Edited)