P: Lightroom Paste Settings with Denoise creates color artifacts & pink overlays

[matthew_5332]

Hi,

Bug 1)  I've been running into this issue for a couple weeks now.  Whenever I copy edit settings, it'll paste fine onto one image, but if I try to paste onto another image, it does nothing.

Bug 2)  I also tried pasting onto multiple images at once and it turned a bunch of them weird colors until I let them update AI settings.  I think it might have something to do with the denoise features, TBH.

The attached green image is after pasting settings, but before updating AI.  Normal looking image is after updating AI.

-Matt

Edit:  I'd like to note that Bug 1 is intermittent.  I'd say it's like 1 in every 3 times I copy settings.  Sometimes it'll paste an infinite number of times, others I get one paste and I'm done.

[ob_default45746923]

When i go to paste settings to more than one photo at a time they all turn pink and then i have to click on each one, one by one and it makes the process extreamly slow and i am spending more time editing photos than i need to be. please fix this or go back to the older version. this sucks when you do large amounts of photos. kind of BS

[嵩文321831665eye]

After the LR update (since AI active noise reduction has become in the "detail" option, copying presets with AI denoise can lead to weird colors, requiring me to adjust them one by one)

"Some AI settings need to be updated to properly translate at native resolution"

Has anyone encountered this problem? Thanks

Camera used: Nikon Z50

resolution: 5568*3712
LR version: 8.5.1

[desiree_85]

when copying edits from one photo to a group of just 2 or 20+ photos, it distorts the photos. It almost generates a double image, where it takes part of the photo and blows it up, overlaying or fusing with the original photo, like it is multiple layers. It also will turn the photo all green or purple. It then forces you to go through and update each individual photo and it's "AI" settings. Even though there are no actual "AI" settings, and thats the whole purpose of this step is to elimante having to do each indidividual photo. It takes anywhere from 30 seconds to 5 minutes to update each individual photo depending on how everything is running that day... If I copy to just one photo it's great, but any more it forces me to waste more time in updating each photo, so I have to go back to copying edits to just 1 photo at a time.. 

Also, after I copy the edit settings to the photo, if I happen to do spot removal on any part of the photo, it makes me then go back and update all settings including the masks.... which it literally just did when  I pasted the settings. It almost takes 3 times longer now to edit than prior to this recent update. These are some bad bugs and I really am crammed for time as it is. Praying ya'll fix these soon! I wrote in right after I updated over 3 weeks ago so hoping you're already on it 🙂 

[PJV Photography]

Lightroom Version: 8.5

Mac OS: Sequoia Version 15.6.1

I often want to denoise a few hundred images overnight and then actually edit them the next day, a workflow that's always worked pretty well with Lightroom until recently.

Following the 8.4 update (and now continuing even after the 8.5 update I had hoped would patch the issue), every time I try to apply denoise by copying settings and pasting them to more than one image, the process fails for the majority of the images. After the process runs for a while, they wind up with some pink or green error artifact, and a warning dialog saying that I need to update AI settings.

It usually works fine once I click the "Update All" button in the dialog box, but it then takes a minute or so to re-do that image's denoise process. This renders the attempted batch run pointless, since I still have to manually click through each of the failed images to update their AI settings.

I've seen quite a few people mentioning this issue elsewhere. Is there a plan to fix it in the next update, or should those of us who regularly use batch de-noising in our workflow just plan on rolling back to version 8.3.1 for the forseeable future?

[Ervins G.]

I'm experiencing the exact same issue. Have you found a workaround?

[PJV Photography]

This workaround from Rikk seems to avoid the issue.