Happy new year! Turns out we were using EDID primaries wrong the whole time (gulp!)
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Friendly ping.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
LGTM, added some comments for consideration but they are non-blocking.
} else {Another possibility, add a case for BT709 and leave the default as is.
SetColorspaceProperty(kColorSpaceDefaultEnumName);In the flagged case, should we set the colorspace property to one of "BT709_YCC", "XVYCC_709" ?
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Commit-Queue | +2 |
Thanks!
} else {Another possibility, add a case for BT709 and leave the default as is.
Yeah, that's another good way to frame it. I put it under the default cause cause the feature flag is "default means 709".
SetColorspaceProperty(kColorSpaceDefaultEnumName);In the flagged case, should we set the colorspace property to one of "BT709_YCC", "XVYCC_709" ?
That's the long-term solution I'd want (just always say BT709_YCC). But we'd have to make sure that it doesn't un-WCG the WCG displays.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
drm: Add flag to assume Default colorspace is Rec709
It is currently assumed that when the Colorspace property is set to
Default, the color primaries of the signal are set to the color
primaries read from the EDID. This happens to be correct for several
wide color gamut displays, but is not reliable. Many devices interpret
Default as Rec709.
Add a flag to allow interpreting Default as Rec709, and add a TODO to
more robustly signal the color space.
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |