Open tguilbert-google opened 1 year ago
This request for a standards position is following the Blink feature launch process; it is perhaps heavy-handed for a change of this size (adding a single entry in a dictionary, approved by the Media WG).
Are there any comments as to whether this type of change should go through the standards position request?
A clarification that came up in the Mozilla standards position issue:
This change was not discussed in the Media WG, and was accidently merged in the spec too quickly: see this comment.
Sorry about that :(
WebKittens
@youennf
Title of the spec
WebCodecs AudioEncoder bitrateMode
URL to the spec
https://w3c.github.io/webcodecs/#dom-audioencoderconfig-bitratemode
URL to the spec's repository
https://github.com/w3c/webcodecs
Issue Tracker URL
No response
Explainer URL
No response
TAG Design Review URL
No response
Mozilla standards-positions issue URL
No response
WebKit Bugzilla URL
No response
Radar URL
No response
Description
[EDIT]
The Media WG has agreedThe change to add abitrateMode
toAudioEncoderConfig
was merged into the spec as part of https://github.com/w3c/webcodecs/pull/657. This accidentally was not discussed by the Media WG or the spec editors before being merged. See comment below.This flag will allow web authors to configure WebCodecs AudioEncoders to use a variable bitrate or a constant bitrate. Specific encoder implementations might have slightly different terminology (e.g.
CBR
vsVBR
for Opus), but all of them should map to the general concept of"constant"
versus"variable"
bitrate.Work on the Chromium side is being tracked here.