On Mon, Jun 17, 2013 at 7:49 AM, Torsten Bronger <
[email protected]> wrote:
> Hallöchen!
>
> Ulrich Pegelow writes:
>
> > Am 17.06.2013 01:07, schrieb Torsten Bronger:
> >
> >> If I import an sRGB JPEG into DT, unfold the output profile
> >> module, and press "g", I see a significant gamut warning in the
> >> shadow regions. Why is this? I mean sRGB is sRGB. Is there
> >> some implicit colour shift that causes this?
> >
> > these warnings are generated by lcms2 without any active influence
> > of darktable. Anyhow, I think this is a consequence of the Lab
> > color space where most of the modules act in. Suppose a dark pixel
> > with an Lab value of [1.0, 0.0, -5.0]. That's a fully valid Lab
> > color - a very dark blue close to black. However this can not be
> > represented in an RGB gamut.
>
> But how does such a colour come into existence if you simply import
> an sRGB image?
>
fair question, for srgb input we don't mess with the colors at all apart
from transforming it to Lab and back at the end (as opposed to raw where we
take the liberty to fight the blue-turns-purple problem a little). i would
assume it's a near-out-of-gamut warning? but that's just a wild guess,
would need to check lcms2 source.
-jo
>
> Tschö,
> Torsten.
>
> --
> Torsten Bronger Jabber ID: [email protected]
> or http://bronger-jmp.appspot.com
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Darktable-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
