Am 17.06.2013 07:49, schrieb Torsten Bronger: > 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? >
Admittedly I have no clue. Especially if config option "use lcms2" is activated all color converion should be in the hands of littlecms2 and sRGB->Lab->sRGB should be close to a noop. Ulrich ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
