search

20k / color_proposal_implementation

3 stars 0 forks source link

Add support for Rec. 2020 color space #1

Open ghost opened 4 years ago

ghost commented 4 years ago

Wikipedia link

20k commented 4 years ago

Thanks for adding all of these! The main concern here (once the implementation is a bit more stable) is whether or not there are any standardisation issues from a legal perspective, because none of these are ISO standards. This is something that's been brought up in the past with other proposals, but I'm completely unable to answer this myself.

Either way I'll add them in to test that the library is fully able to do what it promises after I stabilise the implementation!

ghost commented 4 years ago

The main concern here (once the implementation is a bit more stable) is whether or not there are any standardisation issues from a legal perspective, because none of these are ISO standards.

What about sRGB and its usage of Rec. 709 color space? They are in the same boat.

I didn't add 100% proprietary/patented stuff such as Dolby Vision for obvious reasons but the library design should be able to handle those, for example, when patents expire.

20k commented 4 years ago

What about sRGB and its usage of Rec. 709 color space? They are in the same boat.

This is definitely true, even sRGB alone is dependent on ITU-R, IEC, and implicitly CIE for XYZ - I don't think this is a good enough reason to keep any of this out of a proposal, but its definitely something that'll get brought up in a committee meeting (or beforehand).

ghost commented 4 years ago

And in any case, both concepts and templates introduced must support existing practice, especially such mainstream things like HDR video. The color spaces and transfer functions themselves can then be added separately via 3rd party libraries.