Hi Tobias,
I will try without lcms. Are there known pros and cons for and against it?
I use custom display profile (because I calibrated the screen) but that
is all. Can it influence the rendering? This profile is only enabled for
the screen - never selected in output or input profile area.
input profile is is not selected - I use "standard matrix"
output profile is set to sRGB.
I use temp enabling during output of output profile sRGB (for screen) vs
Adobe RGB (for print) on output. Adobe RGB does not exhibit issues.
Last attempts were done with temp enabling of input profile on output.
But again - it only turns on gamut clip to sRGB - nothing else - I leave
the setting to "standard matrix" I do not have "extended matrix" - my
camera is canon 70d. This healed most of the issues but few remained.
Regards,
B
On 16-06-28 02:09 AM, Tobias Ellinghaus wrote:
On Monday 27 June 2016 15:48:48 I. Ivanov wrote:
[...]
In addition - if we are to change the gamut clipping in the input module
to sRGB - it should always confine the colors in this space.
That setting only clips the gamut in that very place of the pipe. Subsequent
modules can and will happily push the gamut of the image again. It is thus not
some sort of working space for darktable.
[...]
Could there be something wrong with velvia module or my logic is not
right? Or - since my check box is "always use Little CMS 2" should I
consider that this may be the culprit? I have never observed issues
without Little CMS.
In that case I would suggest to turn the enforced lcms usage off. I can't say
what exactly is going wrong there. Are you using any custom color profiles? As
input, output or display profile?
Thank you,
B
Tobias
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
