Copy link to clipboard
Copied
After using the new Denoise tool on a DNG file, the process ends and I receive an "Enhanse Error" saying "Failed to import the enhanced photo" (side note, when I first noticed the issue, I received no error. Last night the error started while testing again). When I check the folder with the originals, the denoised DNG was correctly created and added to the folder. I first noticed this issue after updating my Mac to 13.4.1.
LrC 12.4
Copy link to clipboard
Copied
A Denoise enhanced DNG has '-Enhanced NR' added to the file name. This file has not, so I wonder what is going on and if this is a denoised DNG at all. What file type is the original file?
Also check that Lightroom Classic still has full disk access. The update may have reset that:
Copy link to clipboard
Copied
Hi Johan,
Thank you for the reply. I did double check the disk access, but everything looks good there. What's strange is the file I show with the error above, where Lr states it "failed to import," is actually the original file edited in Lr and not the "enhanced" version.
When I check the source folder for the images, Lr did create the new Enhansed-NR.DNG file correctly. I have no idea what's going on, but something strange is happening.
thanks for your help!
Copy link to clipboard
Copied
In general, LR is pretty bad about giving the low-level operating-system error messages when things go wrong, making it unnecessarily difficult to troubleshoot issues. This particular error has been reported a couple other times but in situations much different. Some troubleshooting steps:
1. Are you invoking Denoise on a virtual copy? There was a bug with that in LR 12.3 but it's supposed to be fixed in 12.4.
2. In the Folders panel, right-click the folder containing the original image and do Synchronize Folder. Does the denoise DNG that's in the folder on disk get imported?
3. Try putting a sample raw on your Desktop and importing that into LR with the Import > Add option, so that LR doesn't move or copy it somewhere else. When you run Denoise on that image, does it work correctly
4. Run LR with some extra logging enabled, which sometimes gives clues:
a. Start the Terminal app.
b. Copy and paste this command line:
/Applications/Adobe\ Lightroom\ Classic/Adobe\ Lightroom\ Classic.app/Contents/MacOS/Adobe\ Lightroom\ Classic -tracebacks
c. Run Denoise to provoke the error.
d. Exit LR.
e. In the Terminal app, do the menu command Shell > Export Text As and save it to your Desktop.
f. Attach the text file from step e to your reply here.
Copy link to clipboard
Copied
Thank you so much for the help. I worked through your suggestions and then realized the folder where these photos are located is actually in Dropbox. I actually forgot this is where the folder was located (I just grabbed these files to do some tests). When I looked closer at my Lr library folders, I noticed Lr was creating a new folder with the exact name as the original and storing the new enhansed dng files there. I also noticed the Dropbox folder was not fully loaded on my Mac. Several of the files were online only. Not sure if this contributed to issue. I made all the photos local and then removed the folder from Lr and reimported the files. After this, when I use Denoise, it creates the new dng in a stack, as it should.
When I did the desktop test (suggestion #3 above) everything worked perfectly normal. I assume this was related to my Dropbox folder in some way. Reguardless, I appreciate all the advice and glad things are back to normal. If there's any other information I can provide that would be helpful, please let me know.
Copy link to clipboard
Copied
You have to be extremely careful with images stored in dropbox(or any other type of cloud drive service) indeed. If files or folders referenced in Lightroom Classic are in that state where they are online only and not physically stored on your actual disk but that using a tiny reference file, it is not unlikely you will end up with very bad file corruption
Copy link to clipboard
Copied
Thank you for the advice, I will definitely keep that in mind moving forward.
Get ready! An upgraded Adobe Community experience is coming in January.
Learn more