On 18/05/2016 17:57, Roman Lebedev wrote:
> On Wed, May 18, 2016 at 6:20 PM, Dan Torop <d...@pnym.net> wrote:
>> From here a bisect suggests
>> https://github.com/darktable-org/darktable/commit/a083e4c0f9ffc0423613f3a75e5e3457aa11430c
>> as the troublemaking commit.
> Not surprising. Thanks for bisecting it though.
> (but does it still happen with the next commit
> https://github.com/darktable-org/darktable/commit/5590478c7bede4061ab06b013d8d227135d08005
> i guess it does)
>
>> Fiddling with color balance seems a good way to cause this. I've also seen
>> it when fiddling with white balance.
>> The preview in the navigation panel shows correct color, while the full
>> image view shows the weird colors.
> Yep, because preview is demosaiced way before any pipe runs on it.
>
>> I can see this when the view is "fit to screen" or 100%.
>> In the later case, the image looks suspiciously like a CFA problem.See
>> https://i.imgur.com/NG4G1y6.jpg.
> It definitely is.
> Either i forgot to change something to use piece->pipe->xtrans
> instead of xtrans field in dt_image_t,
> or missed some codepath that leads to it being set to wrong values.
>
>> This is with OpenCL disabled and an X-Trans image. Will keep looking into
>> this.
> No opencl here, and so far i have not seen this on bayer images.
>
I don't know if this of any importance… I'm using OpenCL… and have the
problem of course, as I reported it :)
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
