• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.

Develop module New Denoise feature

Status
Not open for further replies.
Mulder

Mulder

New Member
Joined
Oct 3, 2024
Messages
12
Location
Tyumen
Lightroom Experience
Power User
Lightroom Version
Classic
Lightroom Version Number
14.4
Operating System
  1. macOS 14 Sonoma
Denoise is now non-destructive and can be copied as part of Details section settings.

Has anyone notices changes in speed? Is it faster or slower or what? Is it GPU-oriented as before?
 
Sort by date Sort by votes
Interesting, how did you get version 14.4? It hasn't even been officially released yet. I just checked with Adobe. Is this a beta version?
 
Upvote 0 Downvote
UliP. said:
Interesting, how did you get version 14.4? It hasn't even been officially released yet. I just checked with Adobe. Is this a beta version?
Click to expand...
Adobe does a phased release these days, with a small percentage quietly released before the main release.

Mulder said:
Denoise is now non-destructive and can be copied as part of Details section settings.

Has anyone notices changes in speed? Is it faster or slower or what? Is it GPU-oriented as before?
Click to expand...
Hold that thought, we're not at liberty to comment until the main release.
 
Upvote 0 Downvote
Thank you very much for the quick reply! Looking forward to the new version!
 
Upvote 0 Downvote
I'm interested on how Adobe did this. With ACR it creates xmp and acr files . As a test I opened a RAW as a Smart Object and immediately trashed those two files. I then opened the file back in ACR, changed the noise amount it accepted that change. I repeated that several times and got the same result.
 
Upvote 0 Downvote
14.4 has been released in some parts of the world, but I can find nothing on the Adobe websites about it. Since it has already been released why isn't the usual release info on the website?
 
Upvote 0 Downvote
Here? There has not been an official release and this site is not associated with Adobe .
 
Upvote 0 Downvote
Please reread what I wrote. I wrote Adobe websites so I meant that to mean Adobe websites, such as adobe.com, helpx.adobe.com, etc. where they usually post new LrC info.
 
Upvote 0 Downvote
I guess Adobe does a bit of a test run first before the major release and announcement.
 
Upvote 0 Downvote
Zenon said:
I guess Adobe does a bit of a test run first before the major release and announcement.
Click to expand...
That is it, Also, there is a cadre of folks like Victoria and others that participate informally the Alpha /Beta Testing.
 
Upvote 0 Downvote
clee01l said:
That is it, Also, there is a cadre of folks like Victoria and others that participate informally the Alpha /Beta Testing.
Click to expand...
I knew there are beta testers out there. Thanks. I think this one is too good to be true and we have been waiting for a while. Getting excited.
 
Upvote 0 Downvote
Zenon said:
I knew there are beta testers out there. Thanks. I think this one is too good to be true and we have been waiting for a while. Getting excited.
Click to expand...
Considering that it was first seen in ACR, I wonder why it has taken this long.
 
Upvote 0 Downvote
Upvote 0 Downvote
This is absolutely fantastic. No more dng files. This makes managing the files so much easier.

After first tests, I have to say that I am very happy with the quality. Not sure if it is faster, but that is of no concern to me.
 
Upvote 0 Downvote
It's here. I'm about to install it.
 

Attachments

  • Screenshot 2025-06-17 at 12.09.27 AM.png
    Screenshot 2025-06-17 at 12.09.27 AM.png
    250.7 KB · Views: 105
Upvote 0 Downvote
Victoria Bampton said:
Adobe does a phased release these days, with a small percentage quietly released before the main release.
Click to expand...
Seems that Adobe does the limited early release 'quietly' but the recipients seem to be quite communacative.

Victoria Bampton said:
Hold that thought, we're not at liberty to comment until the main release.
Click to expand...
This is correct. Once the "you can talk about it now" date/time comes, many of your traditional sources of information will publish info on the new release.
 
Upvote 0 Downvote
It has arrived "down under". Some initial observations.

- on my M4 MacBook Pro and 20 Mbyte EM1 mk2 images taking about 20 seconds to apply to one image
- once denoised doesn't seem to slow down reloading image
- no extra sidecar files are being produced but if automatic XMP updating is enabled then it looks as though the information is added to .XMP file, one of mine went from 19 Kbytes to 12.7 Mbytes when I turned denoising on
- the file <catalog>.lrcat.data appears to be increasing in size as images are denoised, suggests that information that ACR put in .acr sidecars might be stored in catalog instead. So rather than storage increase from denoising being in visible DNGs it accumulates in the background in the catalogue and, if turned on, .xmp files
- if don't have a .xmp file with denoise information in it then opening in ACR from Bridge doesn't know that file was denoised in LRC.
- if don't have a .xmp file sending from LRC to Photoshop as Smart Object and then opening image up in ACR does know about denoising, so presumably catalogue information is being passed across in someway when creating the Smart Object
- can't select several files in Library and then go to Develop, apply denoise to first image and then have it applied to all the selected images and leave it to do its thing. Now have to denoise one image and then sync the settings

So it looks as though although denoise is now non-destructive and doesn't require separate DNGs there is still a storage impact because of extra information being held in catalog and .xmp files. In my experiments with the DNG files I found, that for my usage, I could reduce the size of DNGs by converting them to lossy DNGs, stacked with originals. Only added 3 or 4 Mbytes to storage. New method adds more which doesn't seem to be compressible.

These are my initial observations which may have misunderstood or overlooked something, so do your own experiments linked to your workflows.
 
Upvote 0 Downvote
It's also available in Germany this morning.

My first impressions are mixed. Of course, from a file handling point of view it's welcome that you don't have to deal with a second file, apart from the original image.

The downside is, denoising seems to take a little longer (now 8s instead of 4-5 before for a 20 MP RAW), time to export increases as well. Export of the enhanced DNG is instantly available while export of an image using the new method takes a few seconds (3-4s). It's a similar delay to exporting images with e.g. Lens Blur applied.

David Tillett said:
So it looks as though although denoise is now non-destructive and doesn't require separate DNGs there is still a storage impact because of extra information being held in catalog and .xmp files.
Click to expand...
I was expecting this. Denoise information must be somewhere stored, unless you don't apply denoise from scratch on every export.

Overall it seems to be a big win on the memory side (3,5MB XMP vs. 55 MB for the DNG). Not yet sure how I will perceive the slowdown in performance in my workflow.
 
Upvote 0 Downvote
KarstenG said:
It's also available in Germany this morning.

My first impressions are mixed. Of course, from a file handling point of view it's welcome that you don't have to deal with a second file, apart from the original image.

The downside is, denoising seems to take a little longer (now 8s instead of 4-5 before for a 20 MP RAW), time to export increases as well. Export of the enhanced DNG is instantly available while export of an image using the new method takes a few seconds (3-4s). It's a similar delay to exporting images with e.g. Lens Blur applied.


I was expecting this. Denoise information must be somewhere stored, unless you don't apply denoise from scratch on every export.

Overall it seems to be a big win on the memory side (3,5MB XMP vs. 55 MB for the DNG). Not yet sure how I will perceive the slowdown in performance in my workflow.
Click to expand...
As I said I have been converting my denoise DNGs to lossy format. For a test image I have a 9 Mbyte converted DNG and a 14 Mbyte .xmp from performing non-destructive denoise on original RAW. Plus my catalog has gone up 150 Bytes having added non-destructive denoise to several images.

So I am not sure that there is a memory advantage for my workflow.
 
Upvote 0 Downvote
Zenon said:
May have been a little more complex with the catalogue system.
Click to expand...
I'm guessing at this point (but we will soon find out). Adobe has been putting a lot of things like Masking in the "lrcat-data" file. Instead of writing out a derivative DNG it would be realistic to store the denoise parameters in "lrcat-data"
 
Upvote 0 Downvote
KarstenG said:
It's also available in Germany this morning.

My first impressions are mixed. Of course, from a file handling point of view it's welcome that you don't have to deal with a second file, apart from the original image.

The downside is, denoising seems to take a little longer (now 8s instead of 4-5 before for a 20 MP RAW), time to export increases as well. Export of the enhanced DNG is instantly available while export of an image using the new method takes a few seconds (3-4s). It's a similar delay to exporting images with e.g. Lens Blur applied.


I was expecting this. Denoise information must be somewhere stored, unless you don't apply denoise from scratch on every export.

Overall it seems to be a big win on the memory side (3,5MB XMP vs. 55 MB for the DNG). Not yet sure how I will perceive the slowdown in performance in my workflow.
Click to expand...
While there was a way to work around it there is no more while it builds that preview window. When press Denoise it starts right away.
 
Upvote 0 Downvote
Zenon said:
While there was a way to work around it there is no more while it builds that preview window. When press Denoise it starts right away.
Click to expand...
Sorry I meant there is no more "time waiting" while it builds that preview window.
 
Upvote 0 Downvote
Status
Not open for further replies.
Back
Top