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

[adventure_photo]

I just updated to Lightroom Classic 14.4 and although I do like the fact that I can Denoise without creating a DNG file, I still would like the option to select a series of images and menu: Photo>Enhance... to let it create dngs in the background which enables me to work on other images while it;s doing those. Currently, in 14.4 it takes a long time, especially if I have multiple images that I am denoising and I cannot do anything elese while it's doing that process. Is there still a way possible to do it the old previous way of creating a DNG Denoised file? Seems like an oversight when implementing this new way and slows down my whole workflow.

[ExUSA]

Adobe knows. This isn't the first time they have botched an update. Lightroom IMHO has a LOT of UI problems but itsa what we have. Hopefully someone who actually uses this in production will talk some sense into the product managers. But until then we are all just stuck.

[britney_9122]

This new system to batch denoise is horrible it doesn't work.  Says it is on but photo does not look denoised unless I take it off and put it back on each individual photo. Its taken me 2 months now to complete a wedding that should have taken me 2 weeks. Please bring back the option to batch denoise with a dng

[drtonyb]

@Alwaysheathbar wrote

'when I was signing up it was expressed to me that Lightroom classic was getting phased out "sometime soon"'

I don't know who expressed that to you, but I don't think there is any truth in it at all.

[defaultuz6s618w5u07]

If that were the case, Adobe would be burying a product that many professionals still enjoy using. The slimmed-down version, Lightroom (Cloud), is completely unacceptable for demanding workflows.

[ppdix]

I downgraded to the previous version of Lr and I'm back in business 

[kostafotograf]

Denoise on M1 MacBook Air is incredibly slow now.
My workflow involves flagging images, denoising and editing.

I cannot work with images after batch-denoising now. They need 20 seconds to load and manage the data, and when they load -- features like copy-pasting settings from a previous photo are broken, as Lightroom re-does the whole denoising process (?!) (wasn't it already analysed in the batch?!)

When you copy over ONLY the settings for color and light -- the image needs ANOTHER 20 seconds to recompute, on the top of the additional 20 seconds needed to load it.

It's as if every single operation besides a slider causes recomputation of the image.

This is ABSURD. I cannot go through 10 photos. I would've edited 110 by now.

Switching back to a previous version, and hoping Capture One develops a better alghorithm. This is absurd messing with professional workflows that people pay big bucks for. 

[johnrellis]

@kostafotograf: "I cannot work with images after batch-denoising now. They need 20 seconds to load and manage the data, and when they load -- features like copy-pasting settings from a previous photo are broken, as Lightroom re-does the whole denoising process (?!) (wasn't it already analysed in the batch?!)"

Have you enabled Catalog Settings > Metadata > Automatically Write Changes Into XMP? There is a severe performance bug with that setting and Denoise:

https://community.adobe.com/t5/lightroom-classic-bugs/p-automatically-write-changes-to-xmp-can-t-be-...

After disabling that setting, performance is usually good.

[kostafotograf]

I migrated from Classic, I work locally in the new version.

[ExUSA]

@johnrellis I have tested with the XMP option on and off (I want it on) and have seen no difference in processing times in Lightroom or using ACR. I have somewhat minimal hardware (M1 Mac mini with 16GB of RAM and a 2019 Intel MacBook Pro) so that may be the bottleneck.

[johnrellis]

@ExUSA: "I have tested with the XMP option on and off (I want it on) and have seen no difference in processing times in Lightroom or using ACR."

An issue that I and others have observed is that, and that Adobe has acknowledged as a bug, after applying Denoise to a large batch of photos, switching photos in Develop takes a very long time and the sliders can be very sluggish until the metadata is fully saved to disk.  These symptoms probably don't affect the time it takes to compute Denoise (either individually or in batch).

[C.Cella]

There's a way to work if you need to do Enhance in batch AND do something else.

1. Select the images you need to Enhance and move them to a Collection *
2. Open them in LrD Local or ACR and Enhance them there.

In LrC you can work on other images ( imo better not touch the images currently being Enhanced in ACR or LrD)
When ACR has finished Enhancing do "Export Settings to XMP" or do "Done"
When LrD has finished Enhancing quit the app, LrD will save to XMP automatically.

In LrC read from metadata.
So by doing Enhance in other apps one can work in LrC on other images.
.
Keeping two apps running is possible but not recommended IMO as they might slow down each other given these intensive tasks...it seems still better than doing nothing till LrC unblocks the UI.

EDIT

* I have added a little detail I forgot to mention

I suggest to move the images to a Collection because LrC detects images edited externally only if viewing them.

Collection helps.

[James31274521omju]

The change of Denoise in the Camera Raw engine (and thus its use in LRC) from DNG file creation to 'always on' slider was a nice idea, but so poorly implemented that it can only be a bug. 

It has been implemented so inefficiently that it runs with a heavier load than some modern next gen PC games. 

Example - When applying denoise, it takes about 6 seconds (as before) to complete at 50% value. However, this is where things go wrong: The load does not stop. It keeps going and drawing more and more load until LRC starts to lag. Even when I don’t do anything else, it now keeps the processor at ca. 50% load, RAM at 65% and my GPU spiking between 0 and 10% load for acceleration. As soon as I zoom in to see, LRC lags and skips (its not fluid) and when I touch any other slider there is a delay of 3-10 seconds for an update (to exposure etc), all the while LRC keeps loading the PC and spiking the GPU for acceleration.

It has made the update of ‘always on’ and ‘live’ sliders totally redundant. While this delay and excessive loading may not be a problem for some who are used to not having the ‘live’ update effect, it is for those of us who are and rely on it for showing clients real time.

This is a bug. The feature does not work as intended. Just because it ‘works’ to some capacity does not mean it is functional, hence a bug.

Additionally, there is a noticeable difference in how the new Denoise renders after use – it is far too aggressive, and takes a lot of texture out. The previous version was just cleaner.

Is there any update in the works to fix this issue?

[James31274521omju]

My original post was moved from Bug to idea - Please do not do that. The feature is bugged. Please investigate a hot fix.

The change of Denoise in the Camera Raw engine (and thus its use in LRC) from DNG file creation to 'always on' slider was a nice idea, but so poorly implemented that it can only be a bug. 

It has been implemented so inefficiently that it runs with a heavier load than some modern next gen PC games. 

Example - When applying denoise, it takes about 6 seconds (as before) to complete at 50% value. However, this is where things go wrong: The load does not stop. It keeps going and drawing more and more load until LRC starts to lag. Even when I don’t do anything else, it now keeps the processor at ca. 50% load, RAM at 65% and my GPU spiking between 0 and 10% load for acceleration. As soon as I zoom in to see, LRC lags and skips (its not fluid) and when I touch any other slider there is a delay of 3-10 seconds for an update (to exposure etc), all the while LRC keeps loading the PC and spiking the GPU for acceleration.

It has made the update of ‘always on’ and ‘live’ sliders totally redundant. While this delay and excessive loading may not be a problem for some who are used to not having the ‘live’ update effect, it is for those of us who are and rely on it for showing clients real time.

This is a bug. The feature does not work as intended. Just because it ‘works’ to some capacity does not mean it is functional, hence a bug.

Additionally, there is a noticeable difference in how the new Denoise renders after use – it is far too aggressive, and takes a lot of texture out. The previous version was just cleaner.

Is there any update in the works to fix this issue?

[ExUSA]

Adobe is aware, there has been a lot of feedback. I have zero inside knowledge but you can 1. check out the public beta release channel where new features are often tested and 2. wait to see what is released at Adobe MAX conference in October. They typically have new versions of pretty much everything and I wouldn't be surprised if a big overhaul and refinement push is revealed then.

[Radoan A]

Hello,

before this latest update, I loved the reflection remove feature on jpeg but I hate the way now have for denoise. 
before I was able to do it in background and work on other parts but now I have to wait for complete the process. It's killing my times. 
I am a real estate photographer and I do denoise from all drone shots and every day almost 100 photos as batch. It's taking so much time. 
is there any way, I can still use the latest feature but in background? So that I can edit other photos? 
thanks 

using Mac OS latest and adobe all latest apps. 

[johnrellis]

@Radoan A: "is there any way, I can still use the latest feature but in background? So that I can edit other photos?"

It's easy to apply Denoise to a batch of photos with your desired amount setting, but you can't do anything else in LR while it's processing the batch. (There's a more involved workflow using Adobe Bridge that would let you do apply Denoise while continuing to use LR -- see a previous post in this thread.)

Make sure you've upvoted this feature request by clicking the upvote button at the top left.

[Colorful_goddess0D4E]

I did update to 14.4 but trying to denoise one cr3 file took 3 minutes...the next day it was 10 mins.

My workflow is now crawling...I rolled back to 14.3 and that was ok at first but the next day it was just as slow.

The agent told me they know they have faults and that they would take 1 month before being resolved...so I want my monthly subscrition paid back until my workflow increases...anything less is robbery...Adobe are common  thieves and conmen.

[Omar Sosa Ok]

desde la última actualización, Versión 8.4, se volvió infuncional, pegar ajustes con mejoras de IA.
porque hay que terminar de Actualizarlas una por una.
Cuando antes era aplicar Mejoras a todas las fotos seleccionadas.

[Colorful_goddess0D4E]

English please .

[DHW Photography]

Or use the translate button 🙄

[Colorful_goddess0D4E]

Andrew Bates waiting for a reply from you.

[gareths61360876]

The update to the denoise feature in Lightroom Classic is unacceptable for my workflow. While previous versions allowed editing to continue on other images while an image was being denoised, the new version freezes the app until the one image has completed the denoise process. Time consuming when I have 1500 images to work on for a job. 14.4 requires all resources to process the denoise image & all other editing to stop. That simply isn't practical!

[C.Cella]

The problem is not isolated to Enhance.

All batch Ai block the UI.

What I suggested is to block the single photos when Ai computations is running, show a loading bar on the thumbnail...unlock the image when Ai computation is done for the image.

This would ensure that as soon as a photo becomes "available for editing" we can work.

A Progress Scope it the status activity would allow cancel all remaining AI processes in one go, no need to cancel per photo via the thumbnail loading bar.

So workflow would be :

1. Users applies Ai Settings to selection (Enhance or Masking or Profile or Distraction Remove or etc...) 

2. When the first photo is done user can view it ot edit it or tag it or rate it or do metadata

3. When the second photo is done user also can view it or edit it or tag it or rate it or do metadata

etc...

@gareths61360876 has said he needs to edit 1500 images with Enhance.

Assuming an average of 20 seconds per photo of Denoise that means he needs 8 hours and 20 minutes to be able to finally view or edit or tag or rate any of them.
Terrible.

Instead with what I propose after 20 seconds he can work on the first one.

After 40 seconds he can work on the second one.

etc...

Much better no!

Even if he only had to edit 30 images it would still be better than now.

.

[adventure_photo]

Checked out Version 14.5 and although I like some of the new features and Denoise works a bit better in that once the default has been processed, you can move the slider without having to update all images all over again. However, why are you being so stubborn Adobe? Why can't you implement background processing? Or if you can't figure out a solid way of doing that, just give us the option and give us the old way of processing via Enhance and creating DNG's? You seriously can't think this new way is better surely? It's fine when doing an image here and there but many of us need to Denoise while working on other images. I sure hope you can come up with a better solution. Going to have to go back to 14.3 and forego the new features as processing Denoise in the background is more important to me.

[drtonyb]

Not being a Pro photographer myself, I would like to understand from those who are why all photos from a shoot, which could be thousands, need to be Denoised. Surely only a fraction of the photos shot will be used, so most will not need denoising.

If I were such a photographer using the 'spray and hope' method, I would not waste any of my time on those images that didn't make the grade. I do sometimes shoot astro at high ISO, but I do not denoise all my shots; only those few that are worth processing further.

Any enlightenment would be welcome.