There's a recent change introduced that changes highlight reconstruction to +3 EV essentially disabling almost all of it.
sob., 18 lip 2020 o 09:04 Peter Harde <peter.harde.pri...@gmail.com> napisał(a): > Hi Dan, > > Am 17.07.20 um 04:34 schrieb Dan Torop: > > 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. > > Yes, you almost perfectly describe the workflow I'm actually using. I > created some presets for different types of images, all of them > initially switching off highlight reconstruction. > > But this is not what you get using the default settings of the module. > There "threshold" is initialized with -1 and this means that almost any > image (at least for my images) is processed with highlight > reconstruction enabled. I suspect that is what Alexander Rabtchevich > refers to in his mail from last wednesday. > > My hardware is powerful enough, I can live with the actual state. But as > Alexander stated, processing times of 15 seconds and more become a problem. > > Best regards, Peter Harde > > ___________________________________________________________________________ > darktable developer mailing list > to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > -- Pozdrawiam, Hubert Kowalski ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
