P: Bring back the ability of Enhance to run in the background. (LrC)

The best solution is to let users choose which noise cancellation method to use.

I agree wholeheartedly. The most productive way to Denoise is how it is in 14.3 - and they should return it to the state where you can continue to edit other image files while an image is rendering in Denoise.  Otherwise, this is a major productivity issue for my work flow.  Anything else - the current Lightroom Classic updates - make it almost impossible to meet client deadlines. Freezing the whole app while it denoises an image is nonsense!

The solution satisfying everyone, I think, as discussed in the beginning, would be to optionally enable the previous denoise version, which creates dng files. Every user could decide for himself and nobody would need to stay on an old LC version.

I would immediately and glady return to the previous denoise, but which was better, with that small preview window etc. 

@Generous_view0D45

I am not trolling.

All Ai models block Ui, is not just Enahnce 

The team has not decided all of a sudden to do something different.for Denoise and SuperRes.

Blocking Ui has been the chosen method when runningn Ai models since 2021 (when Ai Masks arrived first)

Some of us (few isolated voices) complained about Ui blocking years ago, long before non destructive Denoise arrived.

Now after years, everyone is seeing the issusse.

Small problems inevitably grow into bigger problems.

Now inevitably the ACR needs to find a solution.

Are you trolling? 

The reason why denoise completely stops you from doing everything right now is because they don't want it to be run concurrently with a handful of other tools. So they implemented a global block instead of graying out a handful of options while denoise runs. So yes, it is as simple as that.

@Generous_view0D45

You said :

"yeah, it is pretty much as simple as graying out those options while Denoise is running."

Is clearely not as simple as that.

Literally nothing you just said goes against anything I said and nothing I've said is contrary to what you said.

I fail to see how I've underestimated anything.

@Generous_view0D45

You are underestimating the problem.

Suppose you're editing ONE image.

You have done all your Ai settings and everything is perfectly up to date for this image.

Then you sync to 100 or even just 10 other images other images.

As a now there is nothing you can do: now you cannot edit or do metadata, you cannot do anything beside wait.

If AI processes was done in background we could do some other operations but we could still not edit the images processed in background else risk breaking the update Ai process.

So it's not like we could do anything we want, we could do something.

Also in order to allow editing in foreground as backgrounds AI runs something needs to be scaled down.

LrC cannot allocate 100% of resources to foreground editing and 100% of resources to background editing.

One of the two will have to be slower.

I think the price for background Ai processes would be that it will take more time to compute the results but at least we could still work to some extent in foreground.

I think most of us would be happy and prefer that to the total UI paralysis we have now.