Skip to main content
Participating Frequently
October 19, 2017

P: Noise reduction effect not displayed in Develop mode

  • October 19, 2017
  • 108 replies
  • 2003 views

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).

This topic has been closed for replies.

108 replies

Inspiring
October 28, 2017
7.01 doesn't appear to have done anything for this bug.  Still present
Inspiring
October 27, 2017
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 🙂
Todd Shaner
Legend
October 27, 2017
I am seeing an 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 with LR Classic on Windows 7 and Nvidia Quadro 600 graphics card.

The issue is observed when 'Use Graphics Processor' is unchecked or checked in Preferences. To duplicate what I'm seeing select a high ISO raw image with noise. Apply Sharpening Amount 100, Luminance 25 and Color 25 Noise Reduction. Next select 1:3 Zoom View and switch between the Develop module and Library module. It could take up to 15 sec. for the Library image to appear without noise reduction, but it will every time on my system! I'm guessing this is a Direct X vs Open GL rendering issue.

Update: The same issue can be observed using a JPEG export file of the above raw image file. Since no settings are applied to the JPEG this is strictly a display path rendering issue. I confirmed that LR CC 2015.12 does NOT exhibit this issue.

Participating Frequently
October 26, 2017
turn off graphic processor
Participating Frequently
October 26, 2017
Same problem solved turning off the graphic processor AMD Radeon HD 7900 Series latest driver
Known Participant
October 26, 2017
The noise issue remains the same. It doesn't matter if you enable or disable GPU! And it remains the same that as soon as you move a slider the process version changes automatically to version 4. That classic release is just garbage. Sorry to say that.... oh yes, and in process version 2 the noise issue is not there....
Known Participant
October 26, 2017
Update: This error only occurs in process version 3+4 (i.e. as soon as you move any slider in version 3 the process version automagically adjustes to version 4!!!

When I switch to process version 2 the noise is gone and everything works as before Classic. So what is the real reason of process version 4???
Victoria Bampton LR Queen
Community Expert
Community Expert
October 26, 2017
I wouldn't set too much store by what the phone/chat support say. They have been known to get stuff wrong. There's a few people with different cards suffering the same issue, and engineers busy on the thread looking into it, so I'd wait and see what they say.
Victoria - The Lightroom Queen
Inspiring
October 26, 2017
Its garbage, reading this thread alone people are using many different GPUs ranging from 1-2 years old to released a few months ago and have the same issue.
The odds on all these cards (which dont forget ALL previously worked on lightroom) suddenly not supporting it are remote.  Its most likely that LRCC doesnt support THEM.  Which given it used to means its a bug.

If that is the official support response im very disappointed as they clearly haven't read this thread or collated any information at all and seem to be content to ignore the problem.  What we have here is a repeatable with 100% accuracy issue affecting a large variety of video hardware on many different drivers and rarely for bugs, exhibits on both PC and Apple.  All of those hint to a code issue.

Capture 1 is looking more and more tempting albeit its more expensive.  The main thing holding me back is the nightmare of converting, changing over and learning a new work flow.  That and i still need PS for some tasks so its an additional cost per month rather than a replacement.
Jerry Syder
Inspiring
October 26, 2017
It has been confirmed as a bug