Hi,

I take the latest postings about denoise issues as an opportunity to ask a few 
questions.

I am a long term DT user. I have spend hours creating my own denoise profiles 
with several instances of profiled denoise in wavelet and local means. But when 
comparing with rawtherapee or lightroom I have the impression that DT is 
lagging behind. Every once in a while I do a RAW development competion with a 
friend. He is using lightroom, I am using DT. When we compare the resulting 
JPGs, Lightroom frequently beats DT in the denoise area. And the same is true 
for rawtherapee. Denoise is the biggest weakness of DT from my point of view.

It might be a personal issue. May be I just do not know how to do it right. But 
that is my next point. The denoise functionality in DT is just too complex from 
a user point of view. It has denoise bilateral, denoise non-local means, 
profiled denoise, raw denoise and equalizer denoise (do I miss something?), And 
any combination of all of them. This is just too much from my point of view. 
Who actually needs this multitude of denoise functions? And who knows exactly 
what to do with them or how to combine them? 

Does DT really need that many denoise functions? I would appreciate just one 
module with a handful of slideers doing the job. Look at Lightroom. By the way, 
is it possible to adapt the denoise code from rawtherapee? 

I would really appreciate if this posting helps to start a serious discussion 
about denoise in DT. 

Thanks 
Matthias

____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org

Reply via email to