-
Notifications
You must be signed in to change notification settings - Fork 26
Register new codec AV1-related Dolby Vision - 'dav1' #101
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
Comments
Regarding 3.4, isn't there a link to point to? |
Yes. The link currently exists as "Dolby Vision". |
PR has been merged, closing |
@mikedo which DV spec actually deals with it? I looked in the “Dolby Vision Streams Within the ISO Base Media File Format Version 2.2” but I can not find anything about |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1. Name of the organization making the request: Dolby
Please send contact information for that organization, should questions arise at application time or in future, in email to mp4reg at group.apple.com.
2. statement of an intent to apply the code-points in practice: Currently in use.
3. For each code-point requested:
3.1 The type of value requested: Codecs
identify the table on the site in which your value should appear
3.2 The desired value (typically a four-character code): 'dav1'
This should not conflict with any existing or pending code-point visible at the publication site
3.3 Short description of the code-point's meaning: "AV1-related Dolby Vision consistent with ‘av01’"
example descriptions are on the site
3.4 Link to the documentation/specification: existing "Dolby Vision"
link to the place where more information about the code-point can be found (ideally, identification of a published defining specification or other document). If you link to contact information for requesting documentation, please be as specific as possible.
3.5 Any other values needed to complete the request: none
notably, any other data needed for the row of the table into which the code-point will be placed.
The text was updated successfully, but these errors were encountered: