Re: [Gimp-developer] Color space conversions seems to change PCS as well

2020-10-24 Thread Elle Stone
On 10/24/20 5:43 AM, marc...@seznam.cz wrote: Now, you are right that there's one inconsistency, gimp color picker's xyY is not the same as to what is being pushed to the operation. I've got the same color picker result as you have. Well, actually everything I said was right :) . Which

Re: [Gimp-developer] Color space conversions seems to change PCS as well

2020-10-24 Thread JonnyRobbie via gimp-developer-list
> So if changing the rendering intent does make even a small difference I tested that again and there's no difference at all between perceptual and relative colorimetric. But I tried converting with saturation and absolute colorimetric and gimp stdouts that those conversions seem to be not

Re: [Gimp-developer] Color space conversions seems to change PCS as well

2020-10-23 Thread Elle Stone
On 10/23/20 6:17 AM, JonnyRobbie via gimp-developer-list wrote: When first opened, the image is in Built-in sRGB and the top row is pure rgb, that is 255,0,0; 0,255,0; 0,0,255. And when running my small gegl operation, I get this stdout in CIExyY color space: Input pixels x=0.653898,

[Gimp-developer] Color space conversions seems to change PCS as well

2020-10-23 Thread JonnyRobbie via gimp-developer-list
First things first. The C code for gegl operation I use here that prints the pixels in CIE xyY color space is below. I apologize that it's an unnecessary composer3 class, but that's what I had handy as a template. I also attached a very small (3x3) test image `33time.xcf`. When first opened,