ACR Denoise AI - speed issues.

Mini update from the OP.

I updated my GPU driver, with interesting results. I had upgraded the entire Win11 OS to version 23H2 just 2 weeks ago, and I noted I got a new GPU driver in that process (dated 8/14/24). So I thought I was OK. But I checked, and Nvidia said the current driver was now dated 5/14/25, just 2 weeks ago.

The driver update was a minor PITA. Turns out Nvidia has killed the "GeForce Experience" and replaced it with a new routine simply called "Nvidia App". So I had to download/install that first. The driver update then went well, and even deleted/uninstalled all traces of the old "GeForce Experience". However, it tries to force some gaming junk to be included, and you have to "opt-out" a few times.

With the new GPU driver, I repeated some tests. I loaded 25 "naked" raw files into ACR, then used the filmstrip to AI Denoise them one at a time. The GPU memory went to 5.4 GB and stayed there. Denoise speed remained normal at 8 seconds per image. Then I did it again, this time selecting all files and running Denoise in batch. Same result, normal 8 second speed, no memory bloat.

So, that sounds good, but time will tell. In my real world workflow I Denoise the raw images one at a time, bring one into Photoshop, and hammer away. I do lots of other "AI" stuff in Photoshop. Some removes, auto selections, Gen Fill, etc. Then I go back to ACR, grab the next image, and repeat. So, I don't know yet if all those round trips to Photoshop are causing problems that eventually degrade Denoise.
 
Mini update from the OP.

I updated my GPU driver, with interesting results. I had upgraded the entire Win11 OS to version 23H2 just 2 weeks ago, and I noted I got a new GPU driver in that process (dated 8/14/24). So I thought I was OK. But I checked, and Nvidia said the current driver was now dated 5/14/25, just 2 weeks ago.

The driver update was a minor PITA. Turns out Nvidia has killed the "GeForce Experience" and replaced it with a new routine simply called "Nvidia App". So I had to download/install that first. The driver update then went well, and even deleted/uninstalled all traces of the old "GeForce Experience". However, it tries to force some gaming junk to be included, and you have to "opt-out" a few times.

With the new GPU driver, I repeated some tests. I loaded 25 "naked" raw files into ACR, then used the filmstrip to AI Denoise them one at a time. The GPU memory went to 5.4 GB and stayed there. Denoise speed remained normal at 8 seconds per image. Then I did it again, this time selecting all files and running Denoise in batch. Same result, normal 8 second speed, no memory bloat.

So, that sounds good, but time will tell. In my real world workflow I Denoise the raw images one at a time, bring one into Photoshop, and hammer away. I do lots of other "AI" stuff in Photoshop. Some removes, auto selections, Gen Fill, etc. Then I go back to ACR, grab the next image, and repeat. So, I don't know yet if all those round trips to Photoshop are causing problems that eventually degrade Denoise.
Sounds good. Nvidia updates their drivers about once per month. Now when you have the app you can use it, or download the updates at this site. https://www.nvidia.com/en-us/drivers/ On the site you download the file to your computer and then run it (an .exe file).

It is worth having a recent driver because the updates by Nvidia have frequent significant updates.
 
and doesn't require creation of an intermediate DNG file.
When using ACR (v17) through Bridge, there's no longer a DNG file created. You have to enable the Technology Preview --> New AI Features and Setting Panel checkbox to get this behavior.
ACR does not create. DNG either and this will be coming to LrC.
Well, that's nice, but I use LRC for selecting which RAWs to send to PhotoLab, so ACR would be an additional step in my workflow. Plus, AI Denoise is slow. So, thanks for the info, but no thanks to Adobe.
This was not directed at you because I know you don’t like it. I’m an hobby shooter with all the time in the world. It stays under one roof and the perfect workflow for me. Thus no thanks to DXO.
Fair enough. I've kind of forgotten what it's like to be a hobbyist.
 
and doesn't require creation of an intermediate DNG file.
When using ACR (v17) through Bridge, there's no longer a DNG file created. You have to enable the Technology Preview --> New AI Features and Setting Panel checkbox to get this behavior.
ACR does not create. DNG either and this will be coming to LrC.
Well, that's nice, but I use LRC for selecting which RAWs to send to PhotoLab, so ACR would be an additional step in my workflow. Plus, AI Denoise is slow. So, thanks for the info, but no thanks to Adobe.
This was not directed at you because I know you don’t like it. I’m an hobby shooter with all the time in the world. It stays under one roof and the perfect workflow for me. Thus no thanks to DXO.
Fair enough. I've kind of forgotten what it's like to be a hobbyist.
I’ve never forgotten the 20 or so weddings I shot. Events are easier but I gained a while new respect for working pros. I know one day Adobe will enable the NE again I just picked up a Mac Mini 4 in anticipation. My 2019 IMac Intel won’t get the NE benefits
 
Another minor update: After the driver update using Nvidia.app I discovered significant bloat on my system drive (6.2 GB). Google said, "Yes, Nvidia.app bloats. Run this 3rd party utility on the installer file BEFORE you run it."

Too late, too bad. So I just copied everything that looked like bloat to a secondary drive and deleted it off C:. Everything looks OK. Most of it was in the "ProgramData" folder.
 

Keyboard shortcuts

Back
Top