Intent to Implement and Ship: VideoEncoderConfig.contentHint

[Eugene Zemtsov]

Contact emails

ezem...@google.com

Specification

https://www.w3.org/TR/webcodecs/#dom-videoencoderconfig-contenthint

Explainer

https://gist.github.com/Djuffin/c3742404b7c53ada227849c8b2b76b4c

Summary

Adding a contentHint field to VideoEncoderConfig Content hint takes values that are already used for MediaStreamTrack: "motion", "text", "detail". This gives web developers a way to communicate to VideoEncoder the expected type video frames they intend to encode.

Blink component

Blink>Media>WebCodecs

TAG review

N/A

Interoperability and Compatibility

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/919)

WebKit: Positive (https://github.com/WebKit/standards-positions/issues/274)

Web developers: Positive RTC software vendors (including Google Meet) are interested in using it for screen sharing vs live cam scenarios.

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

https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/web_tests/external/wpt/webcodecs/video-encoder-content-hint.https.any.js

Finch feature name

WebCodecsContentHint

Requires code in //chrome?

False

Tracking bug

https://crbug.com/1493588

Estimated milestones

Shipping on desktop

121

Shipping on Android

121

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5103493249761280

--

Thanks,

Eugene Zemtsov.

[Mike Taylor]

Hi Eugene,

Could you please request reviews for all the other review gates in your chromestatus entry?

thanks,
Mike

--
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/CAK8JDrGKnc0Jc_doyR9ZsGVfcnk8aNfNS_t%2BTNQ-KLL%3DW%3DiZdA%40mail.gmail.com.

[Eugene Zemtsov]

Done for Privacy, Security, Enterprise, Debuggability and Testing.

--

Thanks,

Eugene Zemtsov.

[Daniel Bratell]

They seem to be in state "preparing" which is the stage before they are actually requested. The system is a bit new so maybe there is some confusing UI or bug, but they are not yet requested. jrobbins, do you know what might have gone awry?

/Daniel

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAK8JDrHnO-en4d_%2BKcwRBCRWYeVEi8hzcnGUsSkb%3D3dNgh0%2Bdw%40mail.gmail.com.

[Rick Byers]

All the other gates are now approved. I see there's a larger TAG review open which includes this feature, but it sounds like this generic (not codec-specific) feature is the direction TAG is encouraging. I don't think we need to block this little feature on the larger discussion of AV1-specific options.

LGTM1

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6ffa1b86-4f0e-4e07-afb3-f3ad20cb2ebe%40gmail.com.

[Yoav Weiss]

LGTM2

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAFUtAY9K9_YmJRFn%3DQBKb0GsETsSFex0DPprMRRpWUWgcvAtbA%40mail.gmail.com.

[Mike Taylor]

LGTM3