Chunk data definitions are incomplete (VP9, AV1)
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
For VP9, the definition does not allow for superframes (VP9 Annex B) but should. The VP9 spec calls a frame or superframe a "chunk", but this appears to be informal.
For AV1, the OBUs should form a "Temporal Unit", similar to the description in the ISOBMFF binding (possibly we want other requirements from there as well).
In addition, the Opus definition is using "have to" where the other registrations use "expected".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the VP9, AV1, and Opus chunk data definitions in the WebCodecs specification. Compare the VP9 requirements with Annex B, the AV1 OBU requirements with the ISOBMFF Temporal Unit description, and the Opus wording with other registrations. Done means the definitions consistently describe the intended chunk boundaries and use the agreed requirement wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100