On Wed, Oct 12, 2016 at 11:31 PM, Ulrich Pegelow <ulrich.pege...@tongareva.de> wrote: > Are you using OpenCL? I can confirm that it's no longer working if OpenCL is > running. I could bisect the problem: > > 45326d7725c67505f6500815a87d56650ea7af65 is the first bad commit > commit 45326d7725c67505f6500815a87d56650ea7af65 > Author: Roman Lebedev <lebedev...@gmail.com> > Date: Sun Oct 9 15:45:11 2016 +0300 > > Rawoverexposed iop: process_common_setup() properly compute thresholds. > > Practically, only matters if min(wbcoeffs) != 1.0 > > :040000 040000 9216a7ea22b0af35b141afa7aca9b650ba3422b4 > b16d2611b098c62bae3dff528b262364649e7bb2 M src
Hm, well, that is strange. I guess i somehow failed at opencl codepath for that module. > > Ulrich Roman. > > Am 12.10.2016 um 20:30 schrieb Tim Rolph: >> >> Hi Roman, with raw overexposure indicator enabled usually I get a small >> >> percentage of the image indicated if its over exposed (with CRW images). >> Since >> >> last night (i am checking daily) the whole image turns green when it is >> >> enabled even though it not over exposed! >> >> >> >> P.S it would be nice to be able to visually see an indication that there >> is >> >> overexposure left in an image as sometimes its not obvious >> >> >> >> Regards. >> >> >> >> Tim Rolph. >> > > ___________________________________________________________________________ > 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
