P: Allow ability to adjust Denoise slider value prior to Denoise running (LrC)

---

@ExUSA wrote:

In both Lightroom and ACR, the Denoise amount cannot be adjusted before applying it. This is a regression from the previous preview UI where the amount could be changed before applying Denoise.

 

This means that Denoise must be applied before changes are possible, and the result must be recalculated if a change IS made. This is very, very poor behavior and a huge waste of time for anyone using (for example) different cameras or ISO settings which may need different Denoise amounts. This is made worse because it appears that Denoise amount always starts at 50 and doesn't use the previous setting (unless that can be changed.)

 

It also appears that this only happens if multiple files are selected, and the most selected file is NOT updated? If I select three files with Auto-Sync, apply Denoise, change the slider, the update dialog only shows two files being updated. 

---

@Bianca31783367or78 , The Denoise AI functions are evolving over the past two years and I am pleased to see that the function has evolved to function as a non destructive editor and preserves the original image and stores the edits in the Catalog file and support data files,

There is no necessity to create XMP sidecar files for RAW images or store Metadata to DNG, Tiff, JPEG or other images.

Yes the Denoise now sets the slider to the default 50%, however adjusting the slider is available to adjust as soon as the Denoise is complete, the adjustments are applied instantaneously an you can see the results.

You as the user can export any number of image file type for use in sharing, printing and other requirements.

I you prefer to use XMP sidecar files and store edits with the file you can use the Alternative Raw processing Adobe Camera Raw.

I just want to say that I find the changes to how the denoise works really bad. Having a lot of trouble with it and it's taking so much longer than it used to! Why can't I choose the amount of denoise i want BEFORE applying it? Now I have to process it twice to get the correct setting. I also noticed it doesn't create a stack with DNG and OG file anymore and i find it unpractical too, sometimes i want both files, or multiple settings. I'm seeing lots of users complaining about this! I hope Adobe does something about it 

Slim was referring to the narrow approach fixing only the multi selected photos vs also addressing single photo denoise. No matter, one is fixed the other still remains and apparently is considered a feature? 

I guess the biggest frustration is that it was working better before they fixed it. LOL story of computing in a nutshell.

@m cs16279208: "very slim line but techniqcally accurate regarding the slider changes was in ref to just multiple images."

I wouldn't call it "slim" -- the bug with Auto Sync, forcing Denoise to be recomputed again when changing the slider, was a big factor (but not the only one) in the frustration expressed by users ExUSA and part and others in other threads that their workflows with the new design were much slower.

 The first post says,

"This means that Denoise must be applied before changes are possible, and the result must be recalculated if a change IS made."

" . This means that – after applying Denoise, changing the amount on a batch of images at once is much faster now."

I checked this with a small batch of images which had Denoise applied at default and reduced to 36% on my Win system and it happened almost instantly.

With the advent of LrC 14.5 , performing Denoise AI to a batch of images the following applies.

Copied from Adobe employee @Rikk Flohr: Photography  above.

"Update 08-13-2025:
The current behavior has been modified, and now we avoid recalculating the result when the denoise amount is changed on multiple images at a time. This means that – after applying Denoise, changing the amount on a batch of images at once is much faster now.

To maintain consistency with other AI features, the amount will be set to its default value when applied."

Ok, very slim line but techniqcally accurate regarding the slider changes was in ref to just multiple images. However, reading through all the comments it becomes quite clear the 'by design' of forcing the single photo use of AI Denoise to be at 50% by not allowing the user to modify it first is a poor design in many peoples' minds. Me included. 

Thanks for fixing the multi photos part, now let's get the first image part fixed!

@m cs16279208: "Please note I loaded the new update and it DOES NOT allow the user to set the AI Denoise procedure instead it automatically runs at 50%. Your comment makes little sense."

Rikk's comment made sense, but my mistake for only quoting the first sentence (in an attempt to show that he was correcting the original marking of this Idea as implemented).

The original post and subsequent discussion raised two separate points:

1. The new UI design didn't allow the Denoise Amount slider to be set before first invoking it.

2. Auto Sync of changing the Amount slider recomputed Denoise (many seconds) instead of just changing the amount (very quick).

Under Adobe's definition of "bug" and "idea", the first point, asking to change the UI design, is an "idea", since the LR 14.4 UI was deliberately designed the way it was. 

The second point was a "bug", since clearly it wasn't intended that Auto Sync of changes to the Amount slider would recompute Denoise, while changing the slider manually didn't recompute. That bug was fixed in LR 14.5:

https://community.adobe.com/t5/lightroom-classic-bugs/p-auto-sync-of-changed-denoise-slider-recomputes-denoise-instead-of-just-changing-the-slider/idi-p/15393402

@johnrellis 

The Pinned summary left off much of what I posted (those three little dots at the end...)

"Update 08-13-2025:
The current behavior has been modified, and now we avoid recalculating the result when the denoise amount is changed on multiple images at a time. This means that – after applying Denoise, changing the amount on a batch of images at once is much faster now.

To maintain consistency with other AI features, the amount will be set to its default value when applied.

This bug has been converted to a feature request. "