On Wed, Oct 12, 2016 at 11:31 PM, Ulrich Pegelow
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
> Aut
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
Date: Sun Oct 9 15:45:11 2016 +0300
Raw
On Wed, Oct 12, 2016 at 9:30 PM, Tim Rolph wrote:
> Hi Roman, with raw overexposure indicator enabled usually I get a small
> percentage of the image indicated if its over exposed (with CRW images).
Hmm, it does sound like the last commit may have had unintended side-effects.
> Since last night
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 ab
No, it's not.
You need to provide a bit more information :)
On Wed, Oct 12, 2016 at 8:27 PM, Tim Rolph wrote:
> Hi all, the raw overexposure is broken in current git 2.1.0+1875~gab24fa7 and
> in last nights update.
>
> Thanks,
>
> Tim.
Roman.
> ___
Hi all, the raw overexposure is broken in current git 2.1.0+1875~gab24fa7 and
in last nights update.
Thanks,
Tim.
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.o
