I'm interested as well in ways for Filmic 4 to be as responsive as possible for interactive use. I believe that it's actually quite fast in its core work (parametrically creating and applying a tone curve to the image), even without OpenCL. But highlight reconstruction can bog things down, and even more so if high-quality reconstruction is > 0.
One way to handle this is to create an auto-applied preset which sets "threshold" in the "reconstruct" tab to 6. This should effectively turn off highlight reconstruction on a newly loaded image. Then make the needed adjustments via the "scene" and "look" tabs. All should be quite responsive. Following that, go to the "reconstruct" tab and double-click the "threshold" slider to get back to the default of -1, and do what is necessary to help the highlights. I believe that the trade-off here is that you lose any black/white settings which may be pre-calculated from the EXIF exposure bias data. And, of course, there's a bit of extra mechanics. -Dan On Thu, Jul 16, 2020, at 1:48 AM, Peter Harde wrote: > Hi, > > my hardware is relatively new and has relatively high performance > (i7-8700, 6 core, 12 threads, Nvidia RTX 2060). But also with this > hardware, filmic 4 slows down the processing markedly. And combining > filmic 4 with tone equalizer increases the problem. It is obvious that > both modules are "heavy" due to the algorithms behind them. All the more > it seems very reasonable to me, to get OpenCL support for filmic 4. > > Best regards > > Peter Harde > > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org > > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
