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

I have used LrC for ~ 1 year, Denoise AI worked very well.  But 2 days ago it was not available on Detail.  Instead a very simple denoise   dialogue appeared. It is slow, difficult to use and not AI.  I have tried uninstalling LrC and installing a new LrC dowload supplied by Adobe.  Denoise AI is still not available.   I have removed ~75Mb of files from my hard drive , which is the destination for my exported images, but still I have no Denoise AI.  Any suggestions on how to solve my problem would be very welcome.

No, this is not what I'm asking for. I want to be able to set the amount RIGHT FROM THE START without applying it, so it doesn't have to be recalculated. This is how the feature has worked until now so YES its a regression and not a good one. They made the feature worse. Everything you mention is still available if a user likes that workflow.

Bottom line- bad change for no reason.

@ExUSA 
We can take advantage of history,  Virtual Copies, Snapshots.

So yes we do start with Denoise at 50%  BUT then we can set Denoise X% ,  then Denoise Y% , then Denoise Z%, etc...

Each step is saved and nothing is lost...each step is pre-viewable via hover over and easily comparable with the active step of our choice.

We can use any steps as "Before" OR even we can create VC for different with Denoise Amount and use Compare to see which is best.
Or we can save each different Denoise Amount step or VC as a snapshots and preview them on the same image,

We can effectively have 100 different possible Denoise versions for ANY FILE, all at our fingertips, all editable, all non destructive, all available, all easily undoable.

This is no regression to me.

To achieve the same prior LrC 14.4 we had to crete X different DNG files with baked Denoise and compare each.
In all other softwares on the market we still have to bake Denoise...we must be pretty certain that the result we have chosen is the good one as there's no undoing of those edits

I find you have more power and options than before now.

.

No. This is a regression from the previous UI and process.

Adone can simply allow the slider to be adjusted before applying Denoise. Even with presets, you STILL have to keep applying them to figure out which one is best.

Editing one photo then going back and reapplying it doesn't work either, you have to juggle sync settings.

This is just a poor design.

@ExUSA There is no bug with syncing

The "Active Photo" has Denoise and it is rendered computed real time for that image.
When Auto Sync is enabled the edits are synced AFTER they have been committed to the active photo.

For Ai settings like Denoise I suggest to edit one image, then when you are finished and are sure abut the result "Sync Settings" the Denosie to the other images

This will spare you the tedious staring at the Modal "Update Ai Settings" progress scope window every time you move the Denise Amount slider.

@ExUSA Denoise starts at 50 as a starting point.

Unlike other sliders that start 0, no effect, it considered best to apply Denoise with a "middle ground" intensity.

Denoise DOES not keep the pervious Denoise amount as LrC has no means to know if the previous amount set would work for the current image, ergo it falls-back to default 50.
If you want the same Denoise amount applied to other photo then simple Copy or Sync it form a source and then apply it to other images.

You can also create "Develop Preset" with Denoise.

I suggest to create "Denoise Presets" at intervals: 10% 20% 30% 40% 50% 60% 70% ...up to 100%
You can thus start with the amount you want and think is best right of the bat...is valid workflow

In the end before the Denoise data il actually computed choosing any amount is purely a guess.

Until Denoise if fully real time we have to apply and see.

And I think there IS a bug, read my last paragraph.

Select multiple files with Auto-Sync enabled

Apply Denoise

Once all files have been updated, move the amount slider

Note that the count, in the update window, is one less than the total. It appears that that one file is not in fact updated