Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should Linear Rec. 2100 not be gamut bound? #446

Open
facelessuser opened this issue Jan 13, 2025 · 0 comments
Open

Should Linear Rec. 2100 not be gamut bound? #446

facelessuser opened this issue Jan 13, 2025 · 0 comments
Labels
T: enhancement Enhancement.

Comments

@facelessuser
Copy link
Owner

facelessuser commented Jan 13, 2025

Linear Rec. 2100 is an alias for Linear Rec. 2020. Rec. 2020 is the base for HDR spaces Rec. 2100 PQ and HLG. It's not explicitly needed, but it is more made available for people to more easily associate a linear form of the spaces. One could use Linear Rec. 2020 with no issues.

So, the problem is that these HDR spaces have a lot more headroom. The linear form of Rec. 2100 is still bound to an SDR range. This only matters is you bother to check the gamut of the linear space or I guess serialize (the default options will attempt gamut mapping if the SDR range is exceeded).

You can't simply specify an HDR limit as it varies for PQ and HLG. You could really configure the max HDR to anything you want. It can really be defined to anything. So, the thought is maybe we just let the Linear Rec. 2100 space just be unbound so users aren't confused when it gets gamut mapped to an SDR range. We would still keep Linear Rec. 2020 bound.

The alternative is we just leave Linear Rec. 2100 defined as is. If you don't want it to be gamut mapped, just disable gamut mapping when you serialize it and don't check if the linear space is in gamut.

@gir-bot gir-bot added the S: triage Issue needs triage. label Jan 13, 2025
@facelessuser facelessuser added T: enhancement Enhancement. and removed S: triage Issue needs triage. labels Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T: enhancement Enhancement.
Projects
None yet
Development

No branches or pull requests

2 participants