I've been out all day, so won't get to post new results until tomorrow night.
Originally Posted by TomHuffman Gamut Off
Red: 0.2116Gamut On
No, red's lightness is barely changed at all (about 1.5%) and blue's lightness is significantly darker (61%) without the gamut correction.
Tom, I do appreciate your insight and expertise, and your spreadsheet. I hope you continue to comment here.
While red's absolute Y barely changed, the luma target generated by your spreadsheet depends on the primaries xy location, which is why the luma error is reduced. Without gamut changing xy, the luma error would remain.
I'm not sure just what exactly the RS1 color control affects. But I have to disagree when you say the lightness errors can be eliminated without the gamut controls. RS1 color=0 has blue down -20%. RS1 color=-10 brings red down as well. There is no way to get correct luma for R,G,B at 100IRE on a stock RS1, and maintain D65 grayscale.
The numbers in my post were not targeting REC709 exactly. I was experiementing with a compromise between REC709 and SMPTE-C. When I target exact REC709, I can easily get R,G,B,C < 2.0dE, but M,Y are still around 10. Stock RS1 (color=0) has M dE=8, so only the Y error is visible.
Ron, etc., I think the difference in our secondaries (cyan is always perfect for me) is not caused by the new bulb, but by different test patterns. I only use external patterns (AVS HD709) and you guys use the Lumagen internal patterns. I don't trust the internal patterns, as there has been a bug before where the color controls caused the patterns to change. Even Lumagen recommends using external patterns. I've recently noticed a change between measuring real-time while still in the gamut menu after changing a value, vs. measuring after clicking on OK and exiting. It's almost like some update happens in a spreadsheet.