Talk:XvYCC

---

So, I can't find much detailed non-marketspeak information on XvYCC anywhere. It'd be really nice to have a CIE 1931 chromaticity diagram like that in the article for [Adobe RGB] for comparison with other wide-gamut colorspaces. Anyone know where to find something like that? Matthew Miller (talk) 16:43, 7 December 2007 (UTC)

A problem

Is XvYCC limited to just HDMI cabling? Right now I think the article is ok, but if it is possible to send colors like what you get out of XvYCC over component, I think that needs mentioning. The article leaves the impression that to get the best color, you have to have HDMI 1.3 —Preceding unsigned comment added by 153.91.137.171 (talk) 17:15, 20 March 2008 (UTC)

This in fact seems to be the case; you need HDMI. The castration of the value ranges in previous colour spaces was done in response to spikes in analog transmission routes. Only a digital transmission allows a troublefree transmission of the full 8 bit range. Thyl Engelhardt 213.70.217.172 (talk) 08:06, 14 April 2008 (UTC)

CE

What the hell is a CE system? This is mentioned in the article but not explained. Morons at it again I see. --84.250.188.136 (talk) 02:03, 15 August 2008 (UTC)

I think CE means Consumer Electronics. Like CES and Windows CE. --70.167.58.6 (talk) 22:24, 16 March 2009 (UTC)

Error?

In:

... xvYCC uses the full range of values (0 to 255 in an 8-bit space) to represent colors. ...

I think it should read:

... xvYCC uses extended range of values (1 to 254 in an 8-bit space) to represent colors. ...

As it is extension to BT.709 the values 0 and 255 are reserved for timing reference.

96.53.138.105 (talk) 06:47, 26 December 2008 (UTC)

They are reserved on the wire (HDMI), but they are not in files. 10 bit, 12 and 16 bits reserve even more values. 109.252.94.59 (talk) 11:31, 21 December 2020 (UTC)

Any products that actually use it?

I see some TV makers tout their models have the capability for XVYCC and DeepColor, but nothing actually can use it. All Blu-Ray, HD and video game sources are 8-bit per channel images. --70.167.58.6 (talk) 22:26, 16 March 2009 (UTC)

PS3, triluminos TV from Sony, Canon vidcam ... Mastered in 4K Blu-Rays support xvYCC. http://www.trustedreviews.com/opinions/what-is-mastered-in-4k-and-does-it-make-a-difference

Video recording in x.v.

"I see some TV makers tout their models have the capability for XVYCC and DeepColor, but nothing actually can use it."

Sony's Z7U camcorder can record in x.v.color. ```` —Preceding unsigned comment added by 75.22.180.215 (talk) 01:54, 1 April 2009 (UTC)

Misunderstanding between Full range and x.v.YCC

http://www.hdmi.org/download/HDMI_Specification_1.1.pdf In the specification of HDMI v1.1(P.70 and 71), it is already defined that what "Full range RGB" is. And actually, Full range RGB is transfered from DVI 8-bit format. http://www.ddwg.org/lib/dvi_10.pdf

xvYCC is just a HDMI extension since v1.3. http://www.hdmi.org/pdf/HDMI_Insert_FINAL_8-30-06.pdf It's clear that "xvYCC" expands the range of color (larger area in the "triangle board(http://en.wikipedia.org/wiki/Color_space)"), but it's NOT talking about from the original limited RGB to full RGB. Limited RGB/Full RGB use the same color space(this "color space" refers to the area of the "triangle board"), but different numbers and levels of repersentation bits(quantization range).

so that, Full range RGB should not be equal to "x.v. YCC".

Ghosthk (talk) 12:35, 1 May 2009 (UTC)

Better than ProPhoto RGB?

Is xvYCC colour space better than ProPhoto RGB colour space? Urvabara (talk) 16:36, 29 October 2009 (UTC)

NO, in total size, but ProPhotoRGB has problems with imaginary primaries. Maybe a comparison with Pointer`s gammut (Surface colors) and ACES in a list of colorspaces helps?

xvYCC and YCC

″The xvYCC color space permits YCC values that, while within the encoding range of YCC, have chroma values outside the range 16–240″

How can a value be within the encoding range of YCC and at the same time be outside the 16–240 range for chroma? Shouldn't the ″while within the encoding range of YCC″ be deleted?

DamjanB52 (talk) 03:44, 18 January 2013 (UTC)

the floating point range -0.5 to 7.5 is partially coded in the normal rec709 space and the ilegal values 1-254 except 16-240 encode the extension. — Preceding unsigned comment added by 177.96.129.102 (talk) 18:23, 8 January 2017 (UTC)

There can be even a stronger statement, YUV values YCC=135,155,12 are translated (using BT.709 matrix) into RGB=-43,184,184, that is in xvYCC and outside BT.709. 109.252.94.59 (talk) 05:15, 16 January 2021 (UTC)

External links modified

Hello fellow Wikipedians,

I have just modified one external link on XvYCC. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

• Added archive http://web.archive.org/web/20090829145618/http://www.sony.net:80/SonyInfo/technology/technology/theme/xvycc_01.html to http://www.sony.net/SonyInfo/technology/technology/theme/xvycc_01.html

|needhelp=<bot changed to a dead page, 404; maybe Sony doesnt want people to know that xvYCC covers more colors than DCI-P3, and the current requirements of UHD have 90% of P3. So the HDMI1.3 surpaces the new HDMI2.0 in some aspects. Then of course 4k resolution is bigger but the quality of experience that a wide color gamut with high dinamic range 10bit+ could be used by any 1080 TV if xvYCC and deeepcolor were enabled.>

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

N An editor has determined that the edit contains an error somewhere. Please follow the instructions below and mark the |checked= to true

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 12:59, 21 July 2016 (UTC)