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

did you find the performance while doing 'everything' in the app during a background Denoise satisfactory when compared to the same tasks with no background Denoise running?

By @Rikk Flohr: Photography

I have previously commented many times on my dissatisfaction with how unexpectedly poorly Lightroom runs overall on my rather new and powerful gaming laptop, and have been consistently met with silence on the topic when I press for answers. (See this and this.)

That being said, yes, performance was of course affected. But once again, I think everyone here would agree that being able to do slower work is infinitely better than being able to do no work at all.

@Generous_view0D45  & @ronb2 

Thank you for the feedback.

For you two, specifically, I would ask, did you find the performance while doing 'everything' in the app during a background Denoise satisfactory when compared to the same tasks with no background Denoise running?

As Generous_view indicated, I did everything -- culled photos from other shoots, edited metadata, did adjustments to raw files, etc. I agree that this is an extremely silly question to ask. It's quite apparent that the team is not using the software as the users are if they felt that their regression was beneficial.

There's absolutely no reason for this to run in the foreground when a better solution was already in place. If the intent is to only make a subset of functionality available, then this is another failure. It'd be better to return to the 14.3.1 and earlier working method of denoising photos than to retain this mangled process.

I've been asked to find out what types of specific tasks you execute while Denoise runs in the background under the previous workflow.

 

It would be extremely helpful if you could respond with the types of Camera Raw and Lightroom tasks you performed while creating the background Denoise DNG.

By @Rikk Flohr: Photography 

This is a really odd question to be asked in response to this issue by anyone who has bothered to actually use the software themselves (speaking about whoever directed you to ask this question, not you). All of them? It used to run in the background so pretty much all editing features were fully available. You could work on anything else. That's the point everyone has been making.

I don't think the solution anyone here wants would change if more people were making lighting adjustments, making color adjustments, adding photos to albums, or culling.

Any solution that catered to just some subset of specific tasks being possible again would be worse than all tasks being available as before. This question just reeks heavily of "What's the least we could give back to you to make you stop complaining?"

While we're on the topic though, here's a suggestion. Go one step further and remove pop-up "processing" dialogs that block you from working on other things across the board. Why should we not be able to work on other things while AI masks are being recalculated or while settings are being bulk pasted? As many things as possible should be done in the background without interrupting the ability to work on other things.

The team is evaluating how best to remedy the workflow encumbrance this update has created for high-volume, high-ISO customers. I've been asked to find out what types of specific tasks you execute while Denoise runs in the background under the previous workflow.

It would be extremely helpful if you could respond with the types of Camera Raw and Lightroom tasks you performed while creating the background Denoise DNG. 

Thank you for your patience. 

Creative Cloud app - Apps on the left side - Lightroom Classic - three dots - Other versions - 14.3.1

To install 14.3.1 you can follow this Adobe help article here: https://helpx.adobe.com/download-install/apps/download-install-apps/creative-cloud-apps/install-previous-versions-creative-cloud-apps.html

I had to do this myself since the new process breaks my workflow horribly. I recommend everyone do the same as I'm sure this is a tracked metric.

Just wanted to add my frustration to this discussion, for all the reasons already mentioned. The latest update absolutely smashed my workflow to pieces. Whilst I appreciate the reasoning behind the change, the execution of it should have not been allowed to the wider community in it's current state. This is an application used by professionals and to impact them in this way is unacceptable. I've rolled back to 14.3.1 so that I can get on with editing photos! 

In my experience it is not only about the cumbersome use now but mor relevant for me the quality of the output. I was not able to get the same quality of the resulting file as I got with the dng Version. The clarity, sharpness and amount of detail I could not achieve with the new process. So I reinstalled LrC 14.3.1 and keep it just for that reason. Such a shame. That was the "One click" solution I was waiting for years and that was completely destroyed by this upadate.

Not sure why @Peter_Weimann7679's thread was merged here when it's about the quality of the current denoise process, and not the execution.

I haven't actually done any comparisons myself, so I can't confirm Peter's claim, but assuming there were any back-end changes to denoising, those could remain the same while reverting the front-end process to the former method (of running in the background). And vice versa, the back-end changes could be reverted while the front-end process remains the same.