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

@michelleg7073996 if you do Enhance first and then Masking you should not need to do "Update Ai Settings".

Masking is the last of the Ai Edits in order.

So if LrC is asking for an update then you have a bug.

@JamesRHogg , LrC and ACR are two applications created by Adobe and they both provide the option to process RAW image files from digital cameras. They both utilize the same processing engine , LrC has the ACR engine built in to the Application.

When you are working with Bridge / ACR the processing data is stored in a XMP sidecar file for original raw files from digital cameras or in the file header for tiff, DNG and JPEG images. As far as ACR is concerned the info is in the file. ACR cannot read info from the LrC Catalog.

When you are working with LrC the info from the Images and the changes you make is stored in the Catalog. LrC will read info from the file XMP or file header at import or if you use the manual option to read metadata from the file. There is an option to write metadata to XMP from LrC, however read from the file is only available manually.

While working in LrC it is only reading and writing to the Catalog file and support data files for the Catalog.

With the advent to the AI options including Denoise there is a large amount of data that has to be stored with the file or with the LrC Catalog, the LrC AI data is stored in a data file alongside the Catalog file.

Using both applications the data storage is doubled.

That's what I do. For example, I take 300 photos. then narrow the selection to about 50-60. Then 25 then maybe 10-15 which I will edit. As soon as I have my picks, I immediately delete the files so I won't forget and so they won't take up disk space...

I usually do an auto-everything for light and color and so on to make a smaller selection. Once I have the 10-15, then I denoise and fine tune the light and color. Then I always finish editing the images in Photoshop in 16-bits. I only use LR for organization and RAW editing. 

@drtonyb 

I am guessing my problem is i do very little editing with my photos.  I crop, I masks subject to sharpen/texture a touch, I usually do a very faint radial mask to highlight my wildlife subject, and then I tweak any exposure or white balance if necessary.  then I denoise.  When I denoise first, and then do any masking last, each masking step requires that AI update button again. When I mask first, I only have to hit that update button one time as first hitting denoise (at 50%), then fixing the %, then hitting the Update button.  EVERY.TIME.

@michelleg7073996 

"Doing denoise first (if that is indeed the suggestion from Adobe)"

See here:

https://community.adobe.com/t5/lightroom-classic-discussions/p-recommended-order-of-edits-lr-amp-cr/m-p/14046636 

"First, i have to denoise (at 50% with no choice of my own). Then, I have to change the % to what I really want. Then, if I do any masking/editing, etc to the image after, I have to do that AI Update button again after each change."

Having to do the AI Update after each change is incorrect if the order of edits is followed.

@JamesRHogg see my post here: https://community.adobe.com/t5/lightroom-classic-ideas/p-bring-back-the-ability-of-enhance-to-run-in-the-background-lrc/idc-p/15430763#M24754

Anyone can do batch Ai externally.

LrC and ACR or LrD will be fighting for resources, uselss acr. files or bloated XMP will be created,.etc...

It can be done but is a terrible workaround.

.Just to give youn an idea of how bad it can get.

1. Batch Denoise in ACR

2. acr. files will be created.

3. whe you read metadata in LrC a duplicate of that file will be created in the lrcat-data

If by any chance you save into XMP the data will be in 4 different places.

.acr, XMP (25% bigger) , lrcat-data, lrcat (copy of xmp)

I have written a code to get rid of .acr

So at least I can somehow cope with this horrible workflow.

.

@JamesRHogg , I believe you are referring to Adobe Camera Raw application i.e. ACR not ARC?

Are you suggesting applying Denoise in ACR prior to import to LrC?

I think there may be a solution

I find that I can use LrC while ARC is actively working on batch processing.

We could use ARC for time consuming AI processes and simultaneously work on LrC on other files.

If you do any AI you can select the stop button and non AI features will be displayed. The edit status button will go yellow

When you have a batch of pics needing AI status update load the batch into ARC and start batch processing with edit status update.  I did this by doing the first pic and pasting the edits to the rest of the batch but I bet there’s a cleverer way. Get back to working on LrC deferring slow AI till the next ARC batch.

After ARC batch use “synchronise folder” to bring pictures up in LrC if they haven’t already appeared

I think it should be possible to write an export protocol so that pictures can be easily sent from LrC to ARC  but I dragged RAW files from grid and dropped them on the Photoshop icon on my MacBook M4.

If Adobe feel this could be a workable solution, I imagine they would be able to make the whole process much slicker without too much difficulty.

I hope this works for everyone’s sake

Good Luck

James Hogg

Am I the only one here that would be perfectly ok with the option to "block the user from doing other Edit operations on the same photo, until the Enhance step is done."  ?

I believe nobody here wants to apply Ai in a batch and before the process is even fished, before even seeing the result, do more edits on those same images.

I believe we only want to be free. 
We want to be able to do our batch AI (doesn't have to be Denoise,  could be just less computationally expensive Ai Masking or Adaptive Profile) and until the images are ready still be able to something else NOT in conflict with the Ai process running on those images.

.

I think there may be a solution I noticed