Skip to main content
hayphotoman
Known Participant
April 19, 2023
Answered

Can't see enhanced image in develop module in LRC after denoise

  • April 19, 2023
  • 3 replies
  • 3976 views

After "Enhance" in the new LRC AI denoise feature is clicked a new DNG file is created, but is not visible in the develop module but the file is created and saved on my hard drive. When I try to import it I get a message that the file already exists in the catalog but I can't find it in the catalog. Help, what am I doing wrong?

Correct answer alexskunz

So it might be permissions issue for the folder (depending on where you store your photos). You could right-click the original source folder and use "Get Info" to check the folder permissions.

 

Or, in the macOS System Preferences, check if Lightroom Classic has "Full Disk Access".

3 replies

Participant
December 20, 2023

I first tried the solutions suggested above (about permissions) with no result. Then I discovered that the answer can be very trivial. It matters from which level of the library you edit the file. If you apply AI denoise while being directly in the target folder, you will not see the corrected dng files next to the original raw file. You need to switch to the view of all files in the library and then your de-noised dng files will be visible.

Participant
September 24, 2024

I realize this response is 9 months too late, but I just ran into this same issue when editing in Photoshop (to take advantage of AI), and I can provide a little more insight after figuring it out.

I am also on Windows Lightroom Classic, and did not see the new DNG files (actually .TIF in my case) that were created. The files were in the correct directory when I looked via Windows File Explorer, but LRC's file handling doesn't always mirror Windows. LRC had created a new Folder at the top of the list in the Folders Pane. It has the same folder name as the Windows folder, and even lists the same parent directories all the way up to the drive letter. The reason you cannot drag/drop the DNG files from the location LRC places the files to the 'correct' folder that you launched from, is because the DNG are physically already in that location already. To unite the DNG with their long-lost Raw counterparts:

* First drag them from the "Recent" folder to any folder other than the one you want them in

* Second, drag them to where the other photos from that session are located

* Last, if you moved them all, the LRC Halucination folder will now show (0) photos in it. You can delete that folder.

 

Physically you just moved them and then moved them back. From LRC's perspective you are moving them from some made up folder to the folder where they originally were generated out of.

How this looked in LRC for me:

The yellow area above is cut off, but ends with ".../R6/2024-08-31"

alexskunz
Inspiring
April 19, 2023

Do you have a Library filter in place that doesn't show you DNG files?

 

Can you search for the filename/filenumber in the "All Photographs" collection? (Catalog panel, under the Navigator)

 

If you do find it there, where is the file when you right-click and choose "Show in Library"?

hayphotoman
Known Participant
April 19, 2023

No filter in place for DNG files that I know of. I did find the file in "All Photographs" and discovered it created a new folder in the library and put the enhanced image there, I was then able to open it in the develope module and do further edits. Why it doesn't import the file into the current collection/folder is the mystery. Thanks for you response and help.

alexskunz
alexskunzCorrect answer
Inspiring
April 19, 2023

So it might be permissions issue for the folder (depending on where you store your photos). You could right-click the original source folder and use "Get Info" to check the folder permissions.

 

Or, in the macOS System Preferences, check if Lightroom Classic has "Full Disk Access".

Participating Frequently
April 19, 2023

Did you have the "Create Stack" checked in hte Denoise dialog?  If so research how stacks work in Lightroom.  If not hmmm don't know what happened.  

hayphotoman
Known Participant
April 19, 2023

Tried it both ways. Same result.