Skip to main content
thix2112
Participating Frequently
May 3, 2023

P: Denoise AI and Pentax K3 MKIII DNG files - not working

  • May 3, 2023
  • 106 replies
  • 19037 views

I'm not seeing any noise reduction using Denoise AI on Pentax K3iii DNG files in Lightroom Classic v12.3. Any future solution to this issue?

Thanks

Tom

106 replies

Inspiring
January 2, 2024

Issue:  Ricoh GR3 raw files rated as compatible. After applying denoise to the file not much changes no matter of the scale of applied denoise 0-100.

 

Lightroom Classic version: 13.1

OS and version: macOS 14.12

 

Expected result: Lightroom Classic should do denoise reduction comparable to files from other cameras.

Actual result: Lightroom Classic does not apply denoise properly.

 

 Uploaded  Test files.

Community Expert
December 18, 2023

Would be good if Lightroom threw up an error right now but there is an official statement pinned by Rikk above:

 

"Note:  a change is required by the manufacturer before this issue can be resolved. "

 

So there must be some issue with the pentax files that prevents AI denoise from working on these. I have no clue what that could be but it must make the noise behave completely differently from normal. It does indeed look very differently in character than what I see from my cameras in the files posted here which all show noise limited by the physics of the image capture process which means it must be preprocessed somehow by the pentax cameras. Topaz is surprisingly bad too (although a tiny bit better than Adobe's denoise but far worse than similar files from my cameras) at removing noise from these files. This means something is different about them indeed that doesn't correspond to normal noise in such files.

Participant
December 18, 2023

I fully agree with that but that will not happen. Hopefully we still can use Topaz Denoise on non-RAW file, but that would be nice to have an official statement from Adobe because at the moment Lightroom do not display any error or warning, but just do nothing on the output.

 

clack69
Participating Frequently
December 18, 2023

fotonor: ok, that makes sense - thanks for the explanation!

Participant
December 18, 2023

The "easy" thing to do, was that Pentax made this inbuilt noise suppression on raw files optional. I dont need my camera to remove noise when PC software is better at it.

Participant
December 18, 2023

The older cameras you mention, have raw files with raw data. They have a noise profile which is identical to all other cameras which output raw data. The new situation with K-3 III (and a few other Pentax models) is that they have inbuilt noise suppression. That means the raw data in the dng file is not "raw" anymore, but processed and have a completely different noise than K-50. The result of this is that the AI algorithm has to be trained to be able to recognize the noise from K-3 III and which is unique to K-3 III. 

For Adobe, this means they have to train AI for a specific camera modell instead of using a generic model that works for all cameras without inbuilt noise suppression. That is not an easy task.

clack69
Participating Frequently
December 18, 2023

fotonor: I don't think that insufficient training material is the problem because the denoise function is working perfectly well with older Pentax raw files from K30/K50 and even prehistoric PEFs from my K100D.
There must be a technical reason that DNGs from K3-iii etc. cannot be denoised easily. I tried DxO PureRaw and it shows the same behaviour.
Anyway: ACR 16.1 has been released, no improvement.

Participant
December 18, 2023

It is not an easy problem to solve. The AI algorithm has to be trained and how do you do that. Feed it with the millions of Pentax images floating around on the web?

Keith Reeder
Participating Frequently
December 17, 2023

Sure - it's a really easy problem to solve, and Adobe is just it's taking time to spite you...

Participant
November 27, 2023

Just got a K-3 Mark III and run into this issue 😞 This is a very bad news for me, especially as it seems that Adobe don't care at all, as the issue was reported in April!