I always assumed that basecurve fucks up the whole linear workflow. So I
always have it off.
But still, what then? I mean each module that relies on a certain color
space must take into consideration everything in the pipe before (and
possible undo it, which is not always really possible) to push stuff back
into linear, if necessary.
Or am I missing something here?
.mm
On May 23, 2019 00:17:00 Heiko Bauke <heiko.ba...@mail.de> wrote:
Hi,
quick question: what do RBG color values actually represent in darktable
just after basecurve module? For simplicity, let us assume "input color
profile" is standard color matrix with Rect2020-RGB as working profile
(In case that this is of any relevance.).
Backgroud of my question: The hazeremoval module (implicitly) assumes
that numerical RGB values are proportional to physical intensityies,
i.e., RGB values are from a linear color space. I was not aware of the
distinction between linear RGB and gamma-corrected RGB values, when I
implemented the hazeremoval module. Possibly, a gamma correction should
be taken into account in the hazeremoval module to reduce color artifacts.
Heiko
--
-- Number Crunch Blog @ https://www.numbercrunch.de
-- Cluster Computing @ https://www.clustercomputing.de
-- Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
___________________________________________________________________________
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
