Thank you Tobias, I was not aware of that. But anyway it sounds a bit
strange to me. Why should any module depend on preview window which carries
a lot less image information than the main image? I can imagine that it may
be some remain from past when opencl was not implemented and cpu code was
not so optimized as it is now. In such situation calculating the histogram
from preview may be huge speed benefit. But I am not sure if such strategy
is still valid even nowadays.
Suni
2013/12/21 Tobias Ellinghaus <h...@gmx.de>
> Am Samstag, 21. Dezember 2013, 12:34:35 schrieb suni:
> > Hi all,
>
> Hi,
>
> [...]
>
> since I know nothing about how OpenCL works in darktable I will not
> comment on
> that part, however, I know that
>
> > The other possible solution would be to enable of switching the
> > preview image off and thus to avoid preview pixelpipe processing at all.
> I
> > do not know how much other users use the preview image, but I've found
> > myself to not need it at all.
>
> is a bad idea and I am quite sure that you DO use the preview a lot, just
> not
> directly: the histogram and the color picker use the result of the preview
> pipe, too.
>
> [...]
>
> > Suni
>
> Tobias
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
darktable-devel mailing list
darktable-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/darktable-devel
