Yes @unchdxoly that’s right, thank you for this clarification.
Of course, @aligw you can post here, this forum is made to try to resolve problems.
Sorry for this misunderstanding.
1 Like
I am sticking with version 5, I spent time this morning comparing both and cannot see any differences using my Nikon raw files.
Any results yet from DxO regarding your question/issue, Ali ?
Your question seems to be related to a similar post here.
It’s a Windows issue and DxO will not lobby Microsoft over it.
I have sent sample files to ACDSee and to Serif/Canva (Affinity), so hopefully both houses will incorporate support for this format soon.
ON1 already supports the format, I believe.
1 Like
Do people really just view these things in windows?
OK so file explorer wont preview them. Not a big issue. You dont use a compressed DNG as a final output anyway.
Lightroom, Photoshop, Photolab and other software will read it.
Its a very normal format under the DNG standard. Support will come as and when others bother updating. That isnt DxOs fault.
1 Like
ON1 supports it.
Lightroom/Photoshop (Adobe ecosystem) support it
Photolab obviously supports it.
Not an issue for many people. OS previews really arent that important for these intermediate step files.
I didn’t say it was DxO’s fault per se, but they should be providing sample files to Microsoft, but are not going to.
I have sent sample files to ACDSee and to Serif/ Canva (Affinity), and I believe that ON1 already supports the format.
As you say, actually viewing the files in Windows is not necessary, but would be preferable. It’s our editing software houses that need to provide support.
Its an Adobe standard, documentation is public. Sample files arent needed.
September 2023 this was added to the DNG standard by Adobe so software houses have had well over 2 years to add support.
Pressure from users is ALWAYS a good idea - I know from personal experience that it does work and that you cannot assume that software houses are even aware of these things. At least, they may choose to ignore them until users start to ask for them, so I shall continue in my own way.
1 Like
It may not be critical that Windows itself supports the format. But… on Macs (where it happens to be supported), the immediacy of QuickLook means a lot of users do view all sorts of files from the Finder. It’s the ONE feature I wish Microsoft would borrow from Apple, as I use it on my Macs all the time. I think the only reason Windows users don’t routinely view images ‘natively’ is that it’s a chore and inconsistent.
Note that DNG 1.7 support was added to public Libraw releases only in January 2026, see https://www.libraw.org/news/libraw-0-22-0-release
Darktable, RawTherapee, and many other do not support it (yet), and they mostly use DNG 1.4.
2 Likes
Regarding the new compressed .dng format. Dng is an editing format, like camera raw formats, the file contains far more data than can be ‘seen’ on the monitor. The point is to allow flexibility in editing without the displayed image ‘breaking up’ into visible bands of colour or tone. Many comments on the new compressed dng format in pureraw 6 state that there is no visible difference between the compressed and uncompressed dng options. This is to be expected, as it is not possible to ‘view all the data at once’. However, in my experiments comparing both formats, the editing flexibility does appear to be slightly narrower in the new compressed dng files, presumably due to the lossy compression. As is commonly stated “you never get nothing for nothing”.
1 Like
New update v6.0.1
Improvements
• DNG export options in the Finder/Explorer context menu are now clearer and more flexible, with explicit Uncompressed labeling and new High Fidelity Compression options available.
Bug Fixes
• Fixed an issue where some processing settings (DNG compression and dust removal) were ignored when launching processing from the system context menu.
• Fixed an issue where dust removal was not applied to images processed directly from Lightroom Classic.
• Fixed a crash when saving or renaming presets after launching PureRAW from Lightroom Classic.
1 Like
Fixed for me on Windows / LRC
Progress bar worked fine yesterday. its back to not working today
Has anyone here been able to see that dust removal actually does something?
Testing at default value (20) does not seem to do anything to the photos of a dusty negative. In- or decreasing the sensitivity can occasionally remove something, but it’s not necessarily be a dust spot.
I suppose that ADR was not intended to remove traces of dust on the subject of the photo. Maybe it can handle sensor dust?
Any positive examples welcome!
I provided some “results” here:
As far as I can understand, without seeing anything that directly says so, the dust removal is purely for sensor dust/spots. Not for anything you might find on a film negative, etc.
After a few quick tests on raw scans of negative film and slides, I can confirm that it does partially correct dust. You need to increase the default sensitivity depending on the amount of dust.
Obviously, it’s not equivalent to the results obtained with a Nikon scanner and ICE-type dust removal, but it’s quite effective for a function not designed for that purpose. However, it only works for dust, not for filaments or scratches.
This is all the more surprising since it works on negatives, where the spots are white.
1 Like
Somewhere in the news about PR6, DxO writes:
AI sensor dust removal:
Automated perfection
With DxO PureRAW 6, keeping your images spotless has never been easier.
Its new AI Sensor Dust Removal System automatically detects and
removes sensor dust with...
Okay, sensor dust then.
Extending the functionality to dusty negative scans will probably come later in loose relation to FilmPack’s tone curve inversion. 2-3 years from now?