Lightroom 7.3.1: Often not updating rendering in full res in develop module

  • 4
  • Problem
  • Updated 3 weeks ago
  • (Edited)
It happens very often (but not always) in develop module: Image quality is not updated correctly (full res rendering) when modifying settings. You see banding color artifacts of low res rendering. It usually can be fixed during zooming in 1:1 temporarily.  This is a little annoying as you need to do this quite often. This effect appears usually after having done multiple editing and switching between different viewing modes (e.g., compare or grid view and back to loupe mode).
Lightroom Classic version: 7.3.1 [ 1167660 ]License: Creative Cloud
Language setting: en-DE
Operating system: Mac OS 10
Version: 10.13.4 [17E202]
Application architecture: x64
Logical processor count: 4
Processor speed: 3,2 GHz
Built-in memory: 24.576,0 MB
Real memory available to Lightroom: 24.576,0 MB
Real memory used by Lightroom: 7.174,0 MB (29,1%)
Virtual memory used by Lightroom: 16.986,0 MB
Memory cache size: 1.372,6MB
Internal Camera Raw revision: 933
Maximum thread count used by Camera Raw: 3
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 2581MB / 12287MB (21%)
Camera Raw real memory: 2646MB / 24576MB (10%)
Displays: 1) 2560x1440

Graphics Processor Info: 
Metal: NVIDIA GeForce GT 755M
Photo of Sven Kohle

Sven Kohle

  • 38 Posts
  • 13 Reply Likes

Posted 1 month ago

  • 4
Photo of Nick Robinson

Nick Robinson

  • 1 Post
  • 0 Reply Likes
Same here on Windows 10.
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 3846 Posts
  • 1271 Reply Likes
Do you have "prefer smart previews for editing" checked in Preferences > Performance, by any chance?
Photo of Sven Kohle

Sven Kohle

  • 38 Posts
  • 13 Reply Likes
yes, indeed it is in certain situations. please see my post further below....
Photo of Johan Elzenga

Johan Elzenga, Champion

  • 1047 Posts
  • 402 Reply Likes
Yes, I see this too sometimes. It seems that Lightroom does not always re-render the library preview at full resolution, so you have to zoom in 1:1 to force it. I don't use 'prefer smart previews for editing', so that does not seem to be the reason.
Photo of Ed Wolpov

Ed Wolpov

  • 3 Posts
  • 0 Reply Likes
Same here.
Photo of Sven Kohle

Sven Kohle

  • 38 Posts
  • 13 Reply Likes
indeed - I checked with and without 'use smart previews instead of Originals for editing' on Mac version - both ways the issue is often there. Actually it seems to be never rendered in full res until the image is zoomed into once.
(Edited)
Photo of Patrick Philippot

Patrick Philippot

  • 289 Posts
  • 42 Reply Likes
I just noticed something that could be related to this issue : when hovering the presets, I observed that some of them had absolutely no effect. Very strange. Until I understood that if the settings modified by the preset are located in a development panel that is disabled (switch button set to Off), the live preview doesn't take these settings into account.

This is questionable. The live preview should show the full effect of the preset by temporarily re-enabling the setting panels that are switched off. Otherwise, this doesn't make much sense.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3170 Posts
  • 518 Reply Likes
@Patrick Philippot - that is an interesting observation. I will ask the team for a ruling on expected behavior. 
Photo of Sven Kohle

Sven Kohle

  • 38 Posts
  • 13 Reply Likes
This issue is really happening very very often and annoys me. I noticed that in develop module in reference mode the not updated full res rendering is showing in both images, but only in the active image zooming in/out resolves that issue for the current image. It does not help in the reference image - never a full res image after zooming in/out again. The image is full of artifacts which does not really allow to compare image quality. It happens with and without having GPU rendering enabled. As it is so easy to reproduce at least on my machine, is there any news or feedback that this behaviour can be reproduced?
Photo of Sven Kohle

Sven Kohle

  • 38 Posts
  • 13 Reply Likes
Another interesting observation - maybe it can help to pin down the root cause:

In "library/compare" mode:
  - the images are shown in low res/low quality until you zoom in/out (or maybe if you have already by some other means forced LR to compute full res image)
  - both in "select" and "candidate" image views this happens, in both views full res can be forced by zooming in/out again
  - it does not depend on GPU activation
  - it does not depend on preference setting: "develop - use smart previews instead of originals"

in "develop/reference" view:
  - the images are shown in low res/low quality until you zoom in/out (or maybe if you have already by some other means forced LR to compute full res image)
  - both in "reference" and "active" image views this happens, but only in "active" view full res can be forced by zooming in/out again, it does not help in "reference" view
  - it does not depend on GPU activation
  - it does not depend on preference setting: "develop - use smart previews instead of originals" - if unchecked, after a delay of a second full res image is rendered

So, Victoria is right in certain situations. It seems that smart preview use is not properly implemented/tested on all the many different combinations of views/modules. It was not an issue in earlier versions, however. So I really would appreciate if this could be fixed - it is really slowing down processing workflow for me.
Photo of Sven Kohle

Sven Kohle

  • 38 Posts
  • 13 Reply Likes
another place where the images don't get rendered in full quality:
slideshow - neither preview nor in the play mode full screen :(

both in library mode and in dedicated slideshow module.
(Edited)