On Sun, Sep 3, 2017, at 10:27, Brune Wayce wrote: > 2017-09-03 18:05 GMT+02:00 Remco Viëtor <[email protected]>: > > > Time needed for real time edition depends on which modules you have > > enabled. > > Most of the basic ones are simple enough, so you won't see much difference > > between CPU and GPU. > > > > But some can be rather slow/calculation intensive (e.g. profiled denoising, > > iirc). And there the GPU can make a (big) difference even while editing. > > > > And even small speed-ups in real-time editing can make a big difference in > > how > > the program 'feels', you can't do much while the image is being > > recalculated. > > Speedups at critical points might not have a big impact on export time > > (and in > > any case, /for me/ a few minutes more or less isn't that important), it can > > make the workflow much faster and avoid frustration. > > > > Remco. > > > That's exactly my situation: the export time is not so important for me, > the important thing is to improve the "live" feeling when I edit a picture. > Now, also with few modules enabled (crop/rotate, exposure, local contrast, > equalizer, denoise profiled), during the zoom in/out the panel freeze with > "working.." showing for 2 or 3 sec.
As far as the "feel", it can really help (even with OpenCL) to keep denoising off for most your editing, and only enable it last. Once I found the setting I liked for my camera in "profiled denoise", I created a style for just that module, and have it applied in the export module. Now I only mess with denoising in darkroom mode for special cases. :) -- jys ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
