Copy link to clipboard
Copied
Version of the app:
LrC 14.5.1
Platform and OS version:
Windows 11 24H2 x64
Basic steps to reproduce the problem:
When using the AI denoise sometimes it does not apply or does not consider the already done desonise.
It got to the point where I was not able to tell if denoise was actually applied without manual one-by-one inspection of each picture. From what I understood it seems to happen if I apply ai denoise on some pictures, then if i synchronize the settings with the ai denoise aswell including both already denoised and non denoised pictures. It already starts wrong since if the selected pictures has a different denoise strenght applied it does recompute the ai denose from scratch instead of just synching the value but it looks like sometimes it does recompute it but also does not apply it even if it looks checked on the develop panel.
Moving the slider manually or setting the value sometimes fixed it but most of time it didn't and sometimes the slider did not move and when typing in the box it instantly deselected itself. Note that it was not grayed out. Syncing the settings again did not fix the problem. Cleaning both video and camera raw's cache did not fix the problem. Restarting did not fix the problem and updating the ai edit status was also completely useless. The noise was still clearly in the image, both luminance and color noise, and did also show exactly in the same way in the exported jpg files. The only way I could "fix" this was to completely delete the preview folder of the catalog and regenerate the denoise from scratch
Expected result and actual result:
To just generate the denose if it is not already present and just synchronize the strenght and to actually apply the denoise and allow me to change the strenght. Also the AI status update button to be effective.
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
Unfortunately, Adobe developers won't pay much attention unless this can be replicated by others (especially them). Your screen recording suggests that there were other edits applied to the problem photos, which might help trigger the problem.
I observed two screwy things in your screenshot and screen recording, to which you alluded:
1. The position of the slider doesn't correspond
...Copy link to clipboard
Copied
Edit: I forgot to mention that to fix it I did not just delete the previews folder but also removed the ai denose on all the pictures and reapplied it so I am not sure which was the fix
Copy link to clipboard
Copied
UPDATE:
I updated my Nvidia drivers to the latest version and regenerated both the previews and the ai denoise but this time it did not work. I still have noise and I have no solution to fix this, I am stuck
Copy link to clipboard
Copied
UPDATE:
I updated my Nvidia drivers to the latest version
By @simone_zini97
Did you install the Studio version of the NVidia drivers? If you are using the Game-ready driver, that could be the cause of your problem.
Copy link to clipboard
Copied
Yes, I always had the studio drivers
Copy link to clipboard
Copied
Hi @simone_zini97, welcome to the community!
Sorry you're running into trouble with AI Denoise. Could you let us know what photo format you're working with? If possible, a quick screen recording of the issue would be super helpful. Also, if you haven’t tried it yet, resetting your Lightroom Classic preferences can sometimes clear up odd glitches, especially if a corrupted internal file is causing the problem.
Thanks a lot, and looking forward to helping you get this sorted!
Alek
Copy link to clipboard
Copied
Hi @Aleke , I'm working with .ARW from my Sony A7III cameras. Now I rolled back to LrC 14.3.1 to finish the job but I can try to install both of them to see if it works. I did the recording I am attaching before rolling back. AI denoise does work but only if I do what I recorded manually on each single picture
Copy link to clipboard
Copied
I tried resetting the preferences and I still have the same problem @Aleke
Copy link to clipboard
Copied
Hi @simone_zini97!
As dj_paige mentioned, would you be able to share some RAW files so we can test things on our end? That would really help us take a closer look.
Thanks so much!
Alek
Copy link to clipboard
Copied
I had to shoot new pictures because I can't share the ones I'm working on, but it shouldn't matter. It seems more likely to happen when working with at least 10 pictures and some of them with already applied denoise and some not
@Aleke @dj_paige
https://www.swisstransfer.com/d/22fb4594-0f34-4355-b8b6-f19f0f405995
Copy link to clipboard
Copied
I donwloaded one photo (_72S1387.ARW) which was almost entirely black, and LrC I was able to denoise it properly.
Copy link to clipboard
Copied
The content of the picture doesn't matter, it's at high iso so there is enough noise for it to be clear if it is working or not. As I said, it is not a problem to denoise a single image, the problem is when I have to do it with tens or hundreds of images
Copy link to clipboard
Copied
Any news? @Aleke
Copy link to clipboard
Copied
Please post on of these photos (the original raw) to DropBox or similar service, and then provide us with the link. We will see if works on our computer.
Copy link to clipboard
Copied
I downloaded all 12 of your photos, and then in one batch operation I denoised them all without any problem at all.
You can tell which files have been denoised by searching in the Filter Bar under Metadata. Performing this search, all 12 of your photos are selected.
Please clearly state what GPU you are using, and the driver NUMBER (we need the NUMBER and not words like "latest" or "up-to-date").
Copy link to clipboard
Copied
As you can see denoise it is clearly checked and if I filter by metadata it shows this picture as denoised. It was also clearly the same situation I have shown in the video I uploaded previously where I also had a different denoise strenght. Note that even at strenght 1 in a 100 color noise does not show up when it works correctly so it is a clear indicator it is just not working.
I am using an NVIDIA GeForce RTX 3080 driver version 581.29 studio driver which came out the same day I made the post
Copy link to clipboard
Copied
What camera was used to take these pictures?
Could your problem be this situation?
I don't know anything about a previously uploaded video.
Copy link to clipboard
Copied
No it is not the same. Please watch the video I attached in one of the messages above. Pictures were taken with a Sony A7iii
Copy link to clipboard
Copied
With your 12 sample pics, I too observed that syncing Denoise from the first to the succeeding 11 worked correctly. I then changed the Denoise slider of the first pic and synced that to the rest, and that worked correctly too. To actually see the noise, I applied a Tone Curve. Take a look at the attached screen recording to see if you consider those results correct (I edited out most of the two minutes of Denoise being synced initially to the the other 11 pics.)
Copy link to clipboard
Copied
[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]
Unfortunately, Adobe developers won't pay much attention unless this can be replicated by others (especially them). Your screen recording suggests that there were other edits applied to the problem photos, which might help trigger the problem.
I observed two screwy things in your screenshot and screen recording, to which you alluded:
1. The position of the slider doesn't correspond with the numeric value:
Often when the user interface is acting up, resetting LR's preferences fixes it:
https://www.lightroomqueen.com/articles-page/how-do-i-reset-lightrooms-preferences/
LR sometimes soils its preferences file, and resetting it can fix all sorts of wonky behavior. That article explains how to restore the old preferences if resetting doesn't help.
2. The AI Edit Status button is yellow, but when you click on it, it doesn't show any other settings that might affect Denoise:
Then nothing happens when you click on Update.
There are many reports here of AI settings needing constant updating and updates not taking effect. The catalog's .lrcat-data file stores the results of AI settings, and if it gets corrupted for some reason, or if there is a permissions issue, that could cause these symptoms. When the file gets corrupted, the only remedy is to delete it and let LR rebuild it, as described here:
While most of the AI commands will be correctly recomputed, there will be new variations computed for Generative AI Remove, which you'll have to review and adjust individually, if necessary.
Alternatively, you could create a new catalog (which will create a new .lrcat-data file) and see if the issue occurs again.
3. Have you used the Imagen AI service at some point? It had a nasty bug that permanently corrupted the .lrcat-data file.
Copy link to clipboard
Copied
I have never used imagen, I think the issue is exactly what you said in the second point: a corrupt .lrcat-data file. I think so because as I moved to an other catalog I was unable to reproduce my own issue
Find more inspiration, events, and resources on the new Adobe Community
Explore Now