On Fri, Nov 11, 2016, at 01:40, Roman Lebedev wrote:
> I doubt that is a bug. Especially profiled denoise is quite CPU-hungry. Thanks. I'm well aware that the denoise is computationally expensive (and rarely have it enabled while editing). What I don't understand is why, occasionally, the rendering time is many times more than the sum of the time for either lens correction *or* profiled denoise, when both are enabled. Explain like I'm five? :) -- jys ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
