Correct support for avc3, hev1?
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
- Apparently avc3 and hev1 are specific forms for writing the AVC and HEVC bitstreams.
- AVC1 and AVC3 don't differ much beyond the codec string, but HEV1 has a
array_completenessvalue which should be set to 1 if parameter sets are expected to change. - WebCodecs VideoEncoder requires explicit config changes, so no matter what we always emit AVC1/HVC1 compliant streams.
The WebCodecs codec registry currently reports support for both of these forms. Should we remove that? Should we require implementations to set array_completeness=1 for HEV1 content even if we don't allow in-band parameter set changes?
@Djuffin @sandersdan
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 reviewing the WebCodecs codec registry and the VideoEncoder requirements mentioned in the issue, focusing on AVC3 and HEV1 support. No files or tests are named; done requires a decided specification change covering registry support and the HEV1 array_completeness requirement.
Written by the indexing model from the issue text.
Assessment
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100