Skip to main content
Inspiring
December 4, 2024
Question

ACR Ver 17.0 Denoise AI - Strange High CPU use after denoise is complete.

  • December 4, 2024
  • 12 replies
  • 2434 views

The following video is a demo of the CPU usage of the latest version of Adobe Denoise AI on Windows 11. There is something strange in that Adobe Camera Raw runs the CPU in the high +90% for a long time after all the Denoise work is done. If you have ACR Version 17 with Technology Preview enabled, please run a similar test and report if you see the same strange CPU usage.

 

Video at: https://www.arkacy.com/Other/Temp-Upload/n-5RJTN/i-v67pfCT/A

 

Related thread on DPReview: https://www.dpreview.com/forums/thread/4784646#forum-post-68019063

 

Related thread on Adobe Camera Raw Forum: https://community.adobe.com/t5/camera-raw-discussions/p-technology-preview-enhance-denoise-super-resolution-raw-details/td-p/14856090

 

12 replies

Inspiring
December 18, 2024

Loaded updates to Photoshop 26.2.0 and ACR version 17.10.2100 today. No joy on this crunching CPU issue following a Denoise. Still happens. Also, found one Win11 user on a different forum who says he ran the test and saw the same on his system. Also, I updated my seldom used Dell XPX-13 laptop I use for travel. It has Windows 10 and shows the same.

Community Manager
December 24, 2024

Hi @redcrown on guard!

Unfortunately, I haven't been able to reproduce this either. Does this happen with every picture you apply Denoise to? Does it also occur with other features like Raw Details or Super Resolution?

Thanks for your patience.

Alek

*(If you mention me with an @, like @Aleke, I’ll get a notification and can respond faster.)*
Inspiring
December 24, 2024

Thanks for trying. My CPU crunch does not happen with just Raw Details. I haven't tried Super Resolution, never needed it.

So, counting you, there are 3 confirmed cases and 3 denials. While that's a very limited sample, it seems to point to some unique Windows modification, or some 3rd party add-on. I do a lot of Windows debloating, mostly following the advice from Chris Titus Tech (https://www.youtube.com/@ChrisTitusTech). Maybe there is something there that Adobe dosen't like.

The work around is simple (Denoise last and then immediately exit ACR). So, not a big deal.

D Fosse
Community Expert
Community Expert
December 6, 2024

I can not reproduce it here.

 

The double spike here is opening from ACR into Photoshop. Left of that double spike is the actual Denoise process. Yes, I have the Technology preview on:

 

And in addition, excessive CPU activity doesn't really make any sense. Denoise runs entirely in the GPU and has never affected the CPU much.

Inspiring
December 6, 2024

D Fosse,

Thanks for that. You are only the 2nd to run my test (the other on a different forum), both showing no CPU problem. I guess that's a good indication I've got a unique gremlin in my system. But I'm at a loss to know how to debug that. I tried by killing all processes and services of 3rd party software I've installed, but I still get my 40 second CPU crunching.

 

Then I tried booting in Safe mode. But when I boot Safe with no internet I can't run Bridge or Photoshop. I get a window saying my subscription can't be verified. I thought Adobe only verified subscriptions periodically, maybe once a month. But I guess not. When I boot Safe with internet I get caught in a Microsoft Edge window that want's me to login and enable Office 365. When I installed Win11 I used the trick to skip the Microsoft account, so I can't login. When I just close that window, Edge freezes and becomes "not responding".

 

Any hints on how to proceed would be appreciated.

D Fosse
Community Expert
Community Expert
December 6, 2024
quote

I thought Adobe only verified subscriptions periodically, maybe once a month.


By @redcrown on guard

 

You thought correctly, it's checked once a month. You can normally work offline for a month (and two more with nag screens).

 

Maybe running it in safe mode is blocking some other service, I don't know. But I've heard of others running in safe mode.