(resending from correct email)

On 2023年07月07日 00時32分12秒 (+09:00), Mike Taylor wrote:



On 7/5/23 8:57 PM, 'Eugene Zemtsov' via blink-dev wrote:


Intent to Implement and Ship: Per-frame quantizer in VideoEncoder



Contact emails

ezemt...@google.com



Explainer

None



Specification

https://www.w3.org/TR/webcodecs/#video-encoder-bitrate-mode



Summary

Adds "quantizer" VideoEncoderBitrateMode for VideoEncoder. This allows to 
specify a quantizer parameter for each frame for AV1, VP9, and AVC video 
codecs. The quantizer parameter is set via codec specific extensions for 
VideoEncoderEncodeOptions.

Assuming I know very little about video codecs, what use cases does this enable 
for developers?




Blink component

Blink>Media>WebCodecs



TAG review

None. 

Previously WebCodecs API had TAG review as a whole:

https://github.com/w3ctag/design-reviews/issues/612


This is a new addition since that review, but it's a trivial addition (IMHO) so 
a new review request isn't needed.


I agree, I don't see anything particularly contentious in the proposal that 
would warrant a full review.






TAG review status

Not applicable



Risks



Interoperability and Compatibility




Gecko: Neutral 
(https://github.com/mozilla/standards-positions/issues/837#issuecomment-1614666364)
 Paul Adenot (Mozilla) expressed that minor changes to WebCodecs spec don't 
need to go through the full "Request for Mozilla Position" process assuming 
they were approved by the Media Working Group.




WebKit: Positive (https://www.w3.org/2023/03/07-mediawg-minutes.html#t02) The 
issue was discussed on 07 March 2023 by w3c Media working group. Jer Noble 
(Apple) was actively participating and provided input for spec details.

Can we request a formal position from WebKit, at least to let them know we're 
intending to ship?




Web developers: Positive (https://github.com/w3c/webcodecs/issues/56) People 
ask for this on GitHub




Other signals:



WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it 
has potentially high risk for Android WebView-based applications?





Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, 
Chrome OS, Android, and Android WebView)?

Yes



Is this feature fully tested by web-platform-tests?

Yes



Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1424154



Estimated milestones

Shipping on desktop

        

117




Shipping on Android

        

117








Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5783986600673280









--

Thanks,
Eugene Zemtsov.
--
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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK8JDrF0PKfpVbaYWX-hR0wJ%2Bb9H4YtwFBUc6Y6JGSmFT7pVgQ%40mail.gmail.com.


--
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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/0a1d0f96-c5f0-fdf8-44b0-b49c3f180839%40chromium.org.

-- 
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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1688734395667.2754843864.3308362256%40chromium.org.

Reply via email to