-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression from 2.13 when interpolating CMYK colours #345
Comments
It only affects CMYK with 8-bit integer depth, 16-bit and float appear to be unaffected. |
Hello, Specifically:
I used from/to built-in sRGB: tificc -t0 -i AP_Munken_Print_White_260v4.1.icm ramps_cmyk.tif out-14-rgb.tif Both gives same result as 2.13.1 Probably I am missing something important. |
Checked other intents too, and BPC as well. All works fine to me. |
Input.
Perceptual.
Only black point compensation and the fast float plugin enabled.
sRGB-elle-V2-srgbtrc (output, 8-bit integer depth). I'll try to bisect now and see if I can trap the regression. |
The plain CMM without plugin works fine in this configuration. I have to build a tificc with the plugin, maybe the issue is in the plugin. Tomorrow will try to do that. |
Git bisected between lcms2.13.1 and current HEAD (with a couple edits to build the fast float plugin under Meson-- btw, thanks for having it!) Seems that one of the optimizations went awry:
|
This makes sense. |
This is a nasty bug on the plugin. Only affects 8 bits and CMYK. I will temporally disable CMYK on it 8 bits since the speed improvement is very small. |
See 328c226 |
Fixed in 2.15 |
@mm2 judging by the commit log, it seems there was no better solution found yet, right? |
Hi @mm2,
We've gotten this bug reported against Krita 5.1.3, where we upgraded Little CMS to 2.14.
Between 2.13.1 and 2.14, something broke in the interpolation of CMYK colors, at least in 8-bit depth:
I'm not sure where in the commit log it happened, but disabling the fast float plugin has no effect. The offending profile is: https://bugs.kde.org/attachment.cgi?id=154115
The text was updated successfully, but these errors were encountered: