OpusBitstreamFormat for AudioEncoderConfig
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Opus follows the pattern of AVC and AAC in having at least two ways to packetize the encoded chunk data. Currently the registration defines how the AudioDecoderConfig.description to signals the packet type, but we should add something like OpusBitstreamFormat { "opus", "ogg" } (check me on the names) for the AudioEncoderConfig to signal a desired encoded output format.
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 comparing the AVC and AAC registration patterns and reading the existing AudioDecoderConfig.description handling alongside AudioEncoderConfig. Confirm the accepted Opus and Ogg naming and define the specification change so encoder output selection is unambiguous; done means the registration and related configuration behavior are updated consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100