Is https://www.w3.org/TR/webcodecs/#dom-audioencoder-encode complete enough?
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
WPT test https://github.com/web-platform-tests/wpt/blob/master/webcodecs/audio-encoder.https.any.js has channelNumberVariationTests and sampleRateVariationTests checking the input data matches the configuration of the encoder, but I see no mention of that in the spec.
Blink checks it, see https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/webcodecs/audio_encoder.cc;l=509
cc @youennf @padenot @dalecurtis @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
Read the WebCodecs AudioEncoder encode section and the WPT file webcodecs/audio-encoder.https.any.js, focusing on channelNumberVariationTests and sampleRateVariationTests. Compare those checks with Blink's audio_encoder.cc behavior, then clarify in the specification whether input channel count and sample rate must match the encoder configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- api, documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 43/100