Bug 397465

Summary: Broken Color Space with Blending Modes, and a few effective broken broken blending modes
Product: [Applications] krita Reporter: reptillia39
Component: Color modelsAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: normal CC: halla
Priority: NOR Keywords: triaged
Version First Reported In: git master (please specify the git hash!)   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: See the wacky output

Description reptillia39 2018-08-15 04:50:31 UTC
Windows 10 64x, Krita git b7e7447

CMYK32F, and LAB32F is effectively broken in Krita if one needs blending modes on those modes. There are almost no working blending modes on LAB32F, and CMYK32F. You can replicate this by creating a black and white gradient with CIELAB filter on G'MIC on 2 different layers perpendicular to each other on a CMYK32F, and LAB32F document, and then change blending mode. Most blending modes are inaccessible in those documents.
Comment 1 Halla Rempt 2018-09-01 12:09:51 UTC
I'm not sure what you mean: the blending modes that are grayed out aren't implemented for those color spaces, but they are not broken. They just don't exist (yet). Or do you mean that the ones that are available are broken?
Comment 2 reptillia39 2018-09-01 15:40:50 UTC
Created attachment 114735 [details]
See the wacky output
Comment 3 reptillia39 2018-09-01 15:42:08 UTC
I know that the one that are grey'd out are not implemented. I'm referring to the one that are available. Lab32F, CMYK32F sometimes have completely black output or white output when using blending modes. I know the issue has to do with how Krita calculate numbers using 0-1 instead of 0-128 for LAB32F. LAB32F do have proper A, and B Channel output though unlike LAB16I, and LAB8I. I guess the entire LAB model are broken for some available blending modes. 

As for CMYK32F, you see output like the one on above post. CMYK8I, and CMYK16I works well enough.
Comment 4 Andrew Crouthamel 2018-09-28 03:40:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-29 02:05:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!