You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAZh%2BM2VAD3pmhuknj69J6hWaTn%2BHWQZ_7EYqUGnPpbSVy%3DdYA%40mail.gmail.com.
https://w3c.github.io/mediacapture-record/#mediarecorder-api Not needed The `MediaRecorder` spec was recently updated to allow either constant bitrate (CBR) or variable bitrate (VBR) encoding to be specified with `MediaRecorderOptions`, previously VBR was assumed when using anything other than uncompressed PCM. This change adds support for the updated specification and for enabling the hard CBR mode of the Opus encoder when CBR mode is configured for the `MediaRecorder`. https://github.com/w3c/mediacapture-record/pull/185This is now in the editors draft https://w3c.github.io/mediacapture-record/#mediarecorder-api
Gecko: No signal WebKit: No signal Web developers: No signals
No No There is currently no coverage this specification update; however, I have opened an issue to add it: https://github.com/web-platform-tests/wpt/issues/24666 https://bugs.chromium.org/p/chromium/issues/detail?id=980559 https://chromestatus.com/feature/5730124735447040This intent message was generated by Chrome Platform Status.
Thanks for the response, I've never filled one of these in before and I wasn't really sure what to put for a fair few of the fields so I just made a best guess to start with. I now know what a TAG review is after some googling, but I'm not clear on whether or not this change needs one. Is there some criteria which indicate when one is required, or is the process to request one and they'll tell you if you don't require one?
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAZh%2BM0_TLKRQSiST6bjaYssxkf4SZ-enDcANnk38a_z%2BoMe9Q%40mail.gmail.com.
I can confirm that this has been discussed in the WEBRTC WG, and that there was no real opposition to adding the feature there (and the shape was revised based on discussion).I don't know if it is valuable enough to make for wide usage, but it is a small API surface change with a good backwards compatibility story.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACj%3DBEgCpAcrzxtxR4fbO77-mCTp7VO%2BjdUE965zr%3Dom74AgNw%40mail.gmail.com.