-
Notifications
You must be signed in to change notification settings - Fork 0
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
Static metadata in HDR10 #45
Comments
In CMAF BoG at MPEG145 it was noted that if the file undergoes any conversions this information would be necessary. |
Should a profile be created to address this?
…On Wed, Jan 24, 2024, 15:49 Dimitri Podborski ***@***.***> wrote:
In CMAF BoG at MPEG145 it was noted that if the file undergoes any
conversions this information would be necessary.
—
Reply to this email directly, view it on GitHub
<#45 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAGEYZJ7TLOFI6P3VFMD77DYQGFZBAVCNFSM6AAAAABB5CITN2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZGA2DQOBZGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
I would simply add a recommendation ("should") that the |
On top of what @cconcolato says, we may add defaults in case they information is not present. |
Thomas will provide a "should" recommendation to be included in the CD of Amd. 2 of Ed.3. We can also add a Note emphasizing that industry is in support of that addition. |
In the industry HDR10 implies PQ colorimetry, 10 bits, and presence of static metadata SEIs, namely SMPTE 2086, MaxFALL, and MaxCLL, the latter two often considered optional as they don't work well in live linear.
The only mention of static metadata in the CMAF spec is in footnote c of table B.1 where all of these are optional.
Should we consider a profile where SMPTE 2086 is mandated, along with the recommended MaxFALL / MaxCLL where possible?
The text was updated successfully, but these errors were encountered: