Pascal de Bruijn wrote: > XYZ = 1.231303 1.000000 0.023474, x,y = 0.546086 0.443503 > D50 L*a*b* = 100.000000 42.461990 138.939711 This is a rather saturated color (139) > But when I put the XYZ values through xicclu, I get a huge mount of > clipping, which resultings in a hue shift to the yellow: > > $ xicclu -f b -s 255 srgb.icc > 1.231303 1.000000 0.023474 > 1.231303 1.000000 0.023474 [XYZ] -> MatrixBwd -> 255.000000 219.479747 > 0.000000 [RGB] (clip) > > So the big question is, did I use the wrong mode for measuring the > terminal? Or am I just misusing xicclu? It's out of gamut of sRGB. This is not much of a surprise really, since the any highly saturated phosphor color is likely to be similar in saturation to the RGB primaries, and if it is centred on a different wavelength it will be expected to fall outside the RGB triangle since the spectrum locus is a curve in xy space. I guess the only surprise is that they chose a highly saturated phosphor - I would have thought they could have mixed a range of phosphors in to de-saturate it. Graeme Gill.