Project

General

Profile

Bug #12527

Luma preset of Denoise (profiled) module gets applied in wavelets mode instead non-local means

Added by Vasyl Tretiakov about 1 year ago. Updated about 1 year ago.

Status:
Closed: invalid
Priority:
Low
Assignee:
-
Category:
Darkroom
Target version:
Start date:
01/06/2019
Due date:
% Done:

0%

Estimated time:
Affected Version:
git stable branch
System:
other GNU/Linux
bitness:
64-bit
hardware architecture:
amd64/x86

Description

According to documentation on Denoise (profiled) module's MODE parameter, luma noise is best tackled with non-local means mode and blending with lightness option.

However, the luma preset shipped with darkatble 2.6.0 gets applied in wavelets mode (just like the chroma preset) and with lightness blending option.

I believe, this could be a mistake here.

History

#1 Updated by rawfiner - about 1 year ago

Hi
This is not a mistake.
Non local means currently does not behave very well as noise increases. Wavelets' behavior remains more consistent when noise increases, that's why it was chosen.

#2 Updated by Vasyl Tretiakov about 1 year ago

Thanks for the explanation. Please feel free to close/cancel.

#3 Updated by dar ix about 1 year ago

maybe make it a documentation bug then, so both match?

#4 Updated by Vasyl Tretiakov about 1 year ago

Indeed, as my confusion came from reading documentation on the module while in the blog post on 2.6 release modes were not mentioned explicitly.

#5 Updated by rawfiner - about 1 year ago

The online documentation is unfortunately not the 2.6 one yet, it is still the 2.4 documentation.
The 2.6 documentation makes it clearer that wavelets can be used for luminance noise too ;-)

#6 Updated by Aurélien PIERRE about 1 year ago

  • Status changed from New to Closed: invalid

Also available in: Atom PDF

Go to top