Skip to main content
Adobe Photoshop Family

8 Messages

 • 

412 Points

Thu, Oct 19, 2017 1:52 AM

Not a problem

Lightroom Classic: Noise reduction effect not displayed in Develop mode

Noise reduction effect not displayed in Develop mode when image is smaller than 1:1. Enlarged is ok, but when I set FIT or FILL, image displayed without noise reduction settings applied (I think so).

Responses

22 Messages

 • 

490 Points

3 years ago

There was an LR update....which didn't really address any of the issues...for me at least. I wonder if the LR people actually see this....cos its a photoshop feedback thingy.

According to the update webpage, if it don't work use LR 6....which pissed me off :)

13 Messages

 • 

504 Points

3 years ago

7.01 doesn't appear to have done anything for this bug.  Still present

6 Messages

 • 

152 Points

3 years ago

This reply was created from a merged topic originally titled The develop module shows a lot of grain when the gpu processor is active.

When I enter the develop module, the image starts to appear dim and with lots of noise, but after a few seconds, everything is "normal".
However, since the last update, the image never gets "normal" unless I disable the GPU. This had not happened before (last version).
This may be more or less noticeable, depending on the image, but in all of them, a grain increase occurs when the GPU is active.
I have already confirmed and my drivers are up to date.
I am using a GeForce GTX 960M (notebook) and RAW files are from a Canon 6D Mark II

150 Messages

 • 

2.9K Points

3 years ago

if I use smart previews it is ok (noise reduction is applied to the preview) if I use no smart previews then the problem exists. W10 GTX 980Ti latest nvidia drivers from 30/10/2017. in 1:1 noise reduction is ok at all times.

20 Messages

 • 

244 Points

3 years ago

This reply was created from a merged topic originally titled Preview rendering post-batch edit.

I'm having a very unusual problem with preview rendering in LR classic on Win 10. I'm working on a timelapse and edited one photo in the series. I then synced the edit to the rest of the ~300 photos. The sync was completed, but the previews were then rendered as very pixelated. The only way I can get them to render properly is to click on each photo one-by-one in the develop module and wait for a couple seconds, or build 1:1 previews. I have tried disabling GPU and restarting LR, as well as restarting my computer. I have left LR idle for a while, and my CPU is idle, so nothing is happening in the background. The pixelated images do get incorporated into my timelapse, when using a timelapse preset I downloaded and added into the slideshow module. However when I export individual photos they look fine. Here is an example of before and after building a 1:1 preview. Look at the sky to see what I'm talking about.

251 Messages

 • 

6K Points

Every time you do any edit on an image, all of the previews are invalidated, which is why it usually doesn't make sense to generate 1:1 previews as in many cases they will get invalidated anyway very quickly. 1:1 previews only make sense for very high volume shooters that as their first step select only those images that are correctly in focus.

For this case, check what is set for your standard preview size. Make sure it is big enough for your display. Usually the Auto setting works well. This is done in Catalog Settings -> File handling. It usually takes a few seconds to generate new previews after any change to the Develop settings and in the intervening time the preview in Library will look pixelated.

20 Messages

 • 

244 Points

Thanks, I'm an experienced user and understand 1:1 previews. I usually don't bother to pre-render them. My standard previews are set to auto.

Rendering is happening just fine in the develop module, but fails in the library module. When I batch edited my photos, only the ones that I subsequently clicked individually in develop looked ok in library.  All the rest were heavily pixelated in the library, and remained so until I forced a build of 1:1 previews for all the photos. This is definitely a new bug that is unrelated to noise reduction. My post should not have been merged into this noise reduction thread.

30 Messages

 • 

666 Points

3 years ago

This reply was created from a merged topic originally titled LR Classic library previews not updating after develop edits.

In library module the preview of an image is not updated after returning from developing module. The only way to get it to update from pixelated/lined view is by either rebuilding the 1:1 preview (i built those on import already) or by zooming in. So i have to 'force' LR to do this by performing an action. Waiting for it to happen without doing anything is not working.
I developed an image with a (very) blue sky in develop module. If i go back to that image it takes a bit for the blue sky to 'smooth out' it looks lined and pixelated at first.

Mac 10.11.6
LR Classic 7.0
32gb ram/i7
for now gpu unticked because of the noise reduction bug (NVIDIA GeForce GTX 780M 4096 MB)

474 Messages

 • 

10.5K Points

I very much wonder if the various merged threads are the same issue, but in response to one of them:

My edits in Photoshop are often not visible after I return to Lightroom. I haven't figured out any rhyme or reason to this. The Photoshop files are large (1-3 GB), but with Lightroom CC 2015 they updated soon after Photoshop was done writing the file. Now, not always.

I haven't figured out how to trigger an update — rebuilding previews seems to do nothing, as Lightroom seems to believe that preview is up to date, and I can't convince it otherwise. Even "touching" the file (changing the file modify date) does not seem to help. Then, sometimes after few minutes, the preview will update in Lightroom.

Lightroom CC Classic 7.0.1 + Mac OS Sierra 10.12.6.

1 Message

 • 

80 Points

3 years ago

I can also confirm this is happening to my system as well after updating to Classic. I see grainy/noise in FIT view, and turning off using GPU resolved the issue, but this is unacceptable to me. Hopefully there will be a fix for this from Adobe, there's way to many different variables and system configurations in this thread for it to be graphics card issue/driver.

3 Messages

 • 

110 Points

3 years ago

Any updates on this issue? It's really starting to get under my skin, it's having a massive impact on slowing down my workflow by having to have GPU acceleration off

2 Messages

 • 

100 Points

3 years ago

This reply was created from a merged topic originally titled Lightroom Classic CC Develop module Noise Problem.

When viewing an image in Develop Module it does not show any noise reduction you have done, in fact it seems to add noise. If viewed in library, then it shows, it’s correct, as does the export. In 1:1 you also see the noise reduction. Also, if viewing in Develop Module and you move a slider, for a split second it shows the correct image with noise reduction.

If you turn off the GPU then it acts as it should. I had a chat with Adobe and he saw the problem, but was at a loss. Then he said it was a driver issue. I am running a 5k 2017 iMac with Radeon 575, and also replicated the problem on two MacBook Pros. I called Apple, and they confirmed all drivers are up to date. The Adobe guy disappeared.

I am convinced this is an Adobe issue, as up until the updates a couple of weeks ago everything was smooth.

Just need clarification from Adobe that they are aware of the problem, but I have seen other users on other forums with the same issue, and the same response from Adobe support.

When editing higher ISO images with night skies or blacks it is critical to see the image as is in Develop Module.

8 Messages

 • 

184 Points

I also think Adobe people should officialy aknowledge this problem, and tell us if they're actually working on int. I can confirm everything you said in your post.

13 Messages

 • 

398 Points

It’s so frustrating, updates to the new cloud version went out yesterday but not to classic. Sign of things to come I guess...

Champion

 • 

5.8K Messages

 • 

102.5K Points

Luke, don't worry, that was just a minor double-dot release to fix a crash bug. Classic actually got the same fix a couple of weeks earlier than CC.

8 Messages

 • 

184 Points

3 years ago

So, anybody knows if Adobe is working on a solution? Is obviously not a driver problem, not a certaing gpu problem, I'm using a gtx 1060 and I've read people with different gpus, brands, and os systems having the issue, so it's obviously a Lightroom problem as many people have already stated. We're abandoned?

560 Messages

 • 

11.9K Points

Hey Ander, they are and I believe it would be released soon. It's nothing to do with your hardware and a confirmed bug. 

8 Messages

 • 

184 Points

Thanks for your answer Jerry, and I truly hope you're right. But I'm not so confident, since a month has gone by, and still yesterday on adobe forums some kind of moderator was still telling me that might be a problem with my hardware or drivers, when obviously it's not. We'll just have to wait and see...

22 Messages

 • 

490 Points

3 years ago

gpu driver update 388.31 - no bueno

8 Messages

 • 

184 Points

It's not related to those drivers or to a certain driver update. Has happened to people on mac and on windows, and with very different gpus (radeon, gtx, etc.). There's people who has even tried installing 4 different drivers and still no luck.

3 Messages

 • 

100 Points

3 years ago

I have exactly the same problem on MacBook Pro (mid 2017) with Radeon Pro 560 (High Sierra 10.13.1) and LR CCC (7.01).
With GPU disabled everything is ok, but with GPU enabled noise reduction is not visible in Develop module FIT view (only visible in 1:1) and also very often previews are not updated in Library module when exiting from Develop module.

Everything worked perfectly ok on the same hardware with LR CC 6.x

br, pawel

20 Messages

 • 

244 Points

I also have the problem with previews not being updated in the library module. The only solution I have found is to force a build of 1:1 previews. I'm certain this is a separate issue than the noise reduction bug. I've reported this as a different bug. It got merged into to this thread by the admins but I've reposted it. It would be helpful if you could add a a comment to the thread.
https://feedback.photoshop.com/photos...

13 Messages

 • 

398 Points

3 years ago

So they confirm they’re working on it but no specifics on when... https://twitter.com/lukedyson/status/...

8 Messages

 • 

184 Points

Thanks for the info Luke, we'll see if this is a priority for them or not...

Employee

 • 

1.7K Messages

 • 

32.4K Points

3 years ago

A fix for this issue has been made for the next scheduled Lightroom update.

Principal Scientist, Adobe Lightroom

20 Messages

 • 

244 Points

That's great news. Thanks for the update. What about the problem with previews not rendering properly in the library module?

Employee

 • 

1.7K Messages

 • 

32.4K Points

>What about the problem with previews not rendering properly in the library module?
Could you help pointing to the thread that report the issue? Just want to be sure which one you are referring to?

Principal Scientist, Adobe Lightroom

20 Messages

 • 

244 Points

Here is a post on this bug. Kitty and I discovered it together. It happens consistently. If I make an edit in develop and then switch over to library, the preview doesn't render properly in library. Solid blue color in particular appears very pixelated. It only renders correctly if you force a rebuild of 1:1 the preview.
https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-library-preview-not-showing...

3 Messages

 • 

100 Points

Yep, exactly. It happens almost every time (completely pixelated nad banded sky). In my case independent of GPU enabled or not.
Zooming into 1:1 waiting till "loading...." disappears and zooming out solves problem for currently viewed picture.

br,pawel

Champion

 • 

2.2K Messages

 • 

36.9K Points

Simon will this also fix the issue with noise reduction not being applied in the Library module when using any of the pyramid Zoom View settings except 1:1 and 1:2?

https://console.getsatisfaction.com/photoshop_family/conversations/lr-classic-noise-reduction-effect...

2 Messages

 • 

92 Points

3 years ago

This reply was created from a merged topic originally titled Display bug when "Use Graphics Processor" is selected.

When "Use Graphics Processor" is selected (Preferences > Performance), all images in the develop module appear very grainy as if shot at an extremely high ISO, regardless of original image or sharpen settings. This grain is not present when exporting the final image, or opening in any other program (including Photoshop).  When the box is de-selected, the grain disappears and the images displays as it should. 

Windows 10
Lightroom Classic 2018
NVidia Quadro M2000M