Copy link to clipboard
Copied
First time I wanted to try Denoise, it wouldn't work as is was trying to save with the same filename.
Seems to be the case as I got a dialog box with "Save As" and then offered to save as .TXT
Restarted LR and was able to Denoise one picture.
Ended up with a similar error when trying another picture (after the second LR restart).
This time, with an additional error message about the GPU.
Anyone with insight into this issue?
Note that it did work well for one time (and pretty quickly too).
Lightroom Classic version: 12.5 [ 202308091523-68a7abd6 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Home Premium Edition
Version: 10.0.22621
Application architecture: x64
System architecture: x64
Logical processor count: 16
Processor speed: 3.6GHz
SqLite Version: 3.36.0
CPU Utilisation: 0.0%
Built-in memory: 32652.7 MB
Dedicated GPU memory used by Lightroom: 2973.0MB / 5968.0MB (49%)
Real memory available to Lightroom: 32652.7 MB
Real memory used by Lightroom: 4863.7 MB (14.8%)
Virtual memory used by Lightroom: 7601.0 MB
GDI objects count: 880
USER objects count: 2474
Process handles count: 4216
Memory cache size: 215.6MB
Internal Camera Raw version: 15.5 [ 1595 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 1452MB / 16326MB (8%)
Camera Raw real memory: 1515MB / 32652MB (4%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Standard Preview Size: 1440 pixels
Displays: 1) 2560x1440
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No
Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 2060 (31.0.15.3699)
Init State: GPU for Image Processing supported by default
User Preference: GPU for Image Processing Enabled
Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic
Library Path: C:\Users\User\Pictures\Lightroom\Lightroom Catalog-v12.lrcat
Settings Folder: C:\Users\User\AppData\Roaming\Adobe\Lightroom
Installed Plugins:
1) ColorChecker Passport
2) Flickr
3) Loupedeck2
4) Nikon Tether Plugin
5) ON1 Effects 2023
6) ON1 HDR 2023
7) ON1 NoNoise AI 2023
8) ON1 Photo RAW 2023
Windows11 SysInfo:
System Information report written at: 10/07/23 16:20:16
System Name: SYLVAIN-I9-TOWE
[System Summary (C:\Users\User\Documents\SystemInfoW11.nfo)]
Item Value
OS Name Microsoft Windows 11 Home
Version 10.0.22621 Build 22621
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name SYLVAIN-I9-TOWE
System Manufacturer System manufacturer
System Model System Product Name
System Type x64-based PC
System SKU ASUS_MB_CNL
Processor Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz, 3600 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 3006, 2021-10-12
SMBIOS Version 3.2
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product PRIME Z390-P
BaseBoard Version Rev X.0x
Platform Role Desktop
Secure Boot State Off
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume5
Locale Canada
Hardware Abstraction Layer Version = "10.0.22621.1413"
Username SYLVAIN-I9-TOWE\User
Time Zone Eastern Summer Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.9 GB
Available Physical Memory 13.2 GB
Total Virtual Memory 36.5 GB
Available Virtual Memory 9.38 GB
Page File Space 4.66 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualisation-based security Not enabled
Windows Defender Application Control policy Enforced
Windows Defender Application Control user mode policy Off
Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualisation Enabled in Firmware No
Hyper-V - Data Execution Protection Yes
Copy link to clipboard
Copied
Moved from Bugs to Discussions, see https://community.adobe.com/t5/lightroom-classic-bugs/p-do-i-post-in-discussions-or-bugs/idi-p/13691... for an explanation why.
Copy link to clipboard
Copied
First time I wanted to try Denoise, it wouldn't work as is was trying to save with the same filename.
Seems to be the case as I got a dialog box with "Save As" and then offered to save as .TXT
By @SdeGat
This can indeed a bit confusing, but the 'Save as' button in this dialog saves the contents of the dialog window as a text file. It has nothing to do with the file mentioned in that error message.
Copy link to clipboard
Copied
I rebooted my computer, went to the very same picture and Denoise worked fine in just 25 seconds or so.
Copy link to clipboard
Copied
Graphics Processor Info:
DirectX: NVIDIA GeForce RTX 2060 (31.0.15.3699)
So GPU driver v536.99. (released 8 August 2023) At NVIDIA v537.42 (released 21 September 2023) is available. Both Game Ready and Studio. Advise using Studio. GPU drivers can be an issue. Your computer probably has an NVIDIA App called GeForce Experience, use that to check for and update GPU driver, Select Custom for install type as to force a clean install.
Copy link to clipboard
Copied
@GoldingD I did get get the notification for the new GPU drivers but it was only for games (according to the NVidia message). I'm no gamer at all. 🙂
Having said that, I usually update regularly.
Copy link to clipboard
Copied
Copy link to clipboard
Copied
A few points
1. NVIDIA publishes two sets of drivers for most of the NVIDIA GeForce GPU's (very old ones not so much) The Game Ready (that they often release updates for first) and The Studio driver (sometimes released later than the Game Ready one)
The Studio driver is better tested, and is for creative use. If you are using creative apps (LrC) it is better.
A quote from NVIDIA:
"NVIDIA Studio Drivers provide artists, creators, and 3D developers the best performance and reliability when working with creative applications. To achieve the highest level of reliability, Studio Drivers undergo extensive testing against multi-app creator workflows and multiple revisions of the top creative applications from Adobe to Autodesk and beyond."
Typically NVIDIA improves the Game Ready driver, typically to support gamers issues, then they return to the Studio driver and look at it.
Typically the default in the GeForce app is the Game Ready driver, You should consider changing that.
2. NVIDIA does not appear to mention much about improvements in the drivers other than gaming. They are not alone in this. Oh they might mention bug and security fixes, but nothing like "fixed issue involving Adobe anything"
A statement at NVIDIA for the update mentioned is as follows:
"The September NVIDIA Studio Driver provides optimal support for the latest new creative applications and updates. This includes DaVinci Resolve version 18.6 which features NVIDIA TensorRT acceleration as well as the latest Chaos Vantage update which introduces support for DLSS Ray Reconstruction."
Yep, vague. And immediately no specific mention of LrC. May or may not be any improvement for LrC. But that is typical. Often you cannot know if the driver update will help LrC or not without giving it a try.
3. An update of a GPU driver typically improves issues or performance. BUT, occasionally the update might break things, as in they fouled up. AMD and NVIDIA have both occasionally failed.
Copy link to clipboard
Copied
Thanks again for following-up @GoldingD
I am pretty sure I had changed the GEForce Experience to "Studio Driver" a long time ago but maybe it was lost in an update and did not notice it.
Anyway, changed it back to Studio Driver and updated again.
Copy link to clipboard
Copied
By the way, when you updated, did you select Custom for install type? As mentioned that forces a clean install. Should have mentioned a clean install scrubs out any old/odd crud that might be an issue.
Copy link to clipboard
Copied
Yes I did the first time I updated to 537.42; chose custom and then clicked on "clean install". 🙂
Copy link to clipboard
Copied
I was able to use Denoise on 2 pictures and then got the same error as above. 😞
Copy link to clipboard
Copied
I could not even Denoise a single picture today. 😞
I got the same errors as originally mentioned above when trying for the very first time (today).
Copy link to clipboard
Copied
I suspect going into /preferences/performance/ and turning off the use of the GPU, will not actually turn off using the GPU for advanced AI functions like Denoise AI. But have you tried anyhow?
Copy link to clipboard
Copied
Also, a stray thought occurred.
Are you using any third party GPU accelerators? Overclocking?
Copy link to clipboard
Copied
My GPU is NVidia and has not given me any issues with anything since I bought it installed in my current computer (3 or 4 years ago). I don't use any overclocking.
I did not try turning off GPU acceleration but LR does turn it off after the GPU error occurs (see above). 🤷🏻
Copy link to clipboard
Copied
After the error occurs, you would need to restart LrC in order to change the use graphics processor option.
Now if that fails, then see Solution 3 in the following link. In fact read that entire link. You may need to delete a text file and let LrC recreate it upon startup
Other members, Do I have this correct?
https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html
Copy link to clipboard
Copied
Still got the same error message today after sucessfully "denoising" two pictures.
I was hoping this issue was addressed/solved in the latest Lightroom update. I guess not. 😞
Copy link to clipboard
Copied
Could this be fixed in release 13.2 that was just made avalaible?
Copy link to clipboard
Copied
Is this a laptop with dual graphics? The two GPUs may conflict (known and fairly common problem).
Disable the integrated GPU as per the instructions here (scroll down to secton 4): https://helpx.adobe.com/lightroom-classic/kb/troubleshoot-gpu.html
Also, the GeForce Experience app has been known to cause problems in Photoshop. I'd recommend not installing it (I haven't). It's not needed.
Copy link to clipboard
Copied
It's a big tower system but there is an integrated video "card" on the CPU; disabling that "video card" is an interesting option. 🤔 I checked it out through Device Manager and there is no graphics card listed other than my main NVidia card. Maybe I've already disabled the CPU graphics card in the past...
I didn't know about the GeForce Experience app, I'll get rid of it.
Thanks @D Fosse.
Copy link to clipboard
Copied
That integrated Video Control (Processor), apparently a , Intel® UHD Graphics. may be deactivated in the BIOS. As such Windows would not see it. Not an issue. If Windows devices is showing only the NVIDIA Dedicated GPU, that is fine.
I have no knowledge of the NVIDIA GeForce Experience fouling PS up, Mine works fine. (but a NVIDIA GeForce RTX 3070)
Copy link to clipboard
Copied
As long as the Intel UHD isn't connected to a display, it doesn't do any harm. It's another situation in a laptop where the integrated display is hard-wired internally. Then the switching is done by the operating system and GPU driver.
So just don't connect any displays to the motherboard sockets, use the GPU connectors only, and you should be fine as far as that goes.
So basically this should work. I'd do a new driver install again, studio driver - and this time, check "custom install" and then "clean install". This will remove all traces of the old driver. Uncheck all the extra components in the driver package, leave only the basic driver checked.
(There is usually a HD audio driver there as well. I'm not sure if that is needed for anything, so I've always left that checked).
Copy link to clipboard
Copied
First of all, thanks @D Fosse and @GoldingD for your efforts and continued assistance. 🙂
I have reinstalled the latest driver as a "clean install" as recommended. There was actually a new studio driver available from Feb 22nd.
I also watched the settings video and followed along to have the exact setup that is proposed in that video.
Next step is to try it out!
Copy link to clipboard
Copied
Here's an update on this issue @D Fosse and @GoldingD,
The denoise function is holding up and I was able to denoise a few pictures without issues. Hopefully, this is settled for good. 🙂
However, LrC is crashing on me pretty regularly now when invoking the Crop tool (R). 😞 The automatic advice when the error happens tells me to turn off the graphics processor option. (it is now configured as shown in the YouTube clip mentioned above/below)
https://helpx.adobe.com/lightroom-classic/kb/crash-gpu-directx-enabled.html