Intent to Ship: WebCodecs support for enabling AV1 screen content coding tools
Philipp Hancke
Contact emails
pha...@microsoft.com, bernar...@microsoft.com
Explainer
None
Specification
https://www.w3.org/TR/webcodecs-av1-codec-registration/#dom-av1encoderconfig-forcescreencontenttools
Design docs
https://github.com/fippo/webrtc-explainers/blob/gh-pages/av1-screencontent/index.md
Summary
Adds AV1EncoderConfig (a dictionary containing forceScreenContentTools) to the VideoEncoderConfig along these lines:
encoder.configure({ codec: 'av01.0.04M.08', av1: { forceScreenContentTools: true}, width: 1920, height: 1080, bitrate: 2_000_000, framerate: 5, });
This allows an application to encode “screen content”, in particular presentation slides, in a more efficient way supported by the AV1 codec.
This material is typically static, often includes text, a limited set of colors, lots of repetitive content (e.g. straight lines, shapes) for which the encoder can optimize.
See the explainer for a lot of visual examples. This AV1 feature is already supported by WebRTC and enabled for screen sharing MediaStreamTracks so this increases platform consistency.
Blink component
TAG review
None
TAG review status
Not applicable
Risks
Interoperability and Compatibility
None
Gecko: Neutral similar to this situation https://github.com/mozilla/standards-positions/issues/837#issuecomment-1614666364
WebKit: No signal (https://github.com/WebKit/standards-positions/issues/239)
Web developers: No signals Presented in the screen capture community group during TPAC 2023, slides here: https://docs.google.com/presentation/d/10i4HFYZ4CylpFUuoJcigfiI5uS7pK3uaseQpcYhugAY/edit#slide=id.g27ea3fad398_0_0
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?
None
Debuggability
None
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?
No
Unclear to what degree this is testable. Enabling this feature reduces the encoded frame size which makes it tough to test, it might be possible with a canvas source that provides predictable input similar to https://webrtc.github.io/samples/src/content/insertable-streams/video-processing/
Flag name on chrome://flags
None
Finch feature name
None
Non-finch justification
None
Requires code in //chrome?
False
Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1464862
Estimated milestones
Anticipated spec changes
None
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6307770441138176
Links to previous Intent discussions
n/a
This intent message was generated by Chrome Platform Status.
Mike Taylor
On 10/20/23 2:27 PM, 'Philipp Hancke' via blink-dev wrote:
Contact emails
pha...@microsoft.com, bernar...@microsoft.com
Explainer
None
Specification
https://www.w3.org/TR/webcodecs-av1-codec-registration/#dom-av1encoderconfig-forcescreencontenttools
Design docs
https://github.com/fippo/webrtc-explainers/blob/gh-pages/av1-screencontent/index.md
Summary
Adds AV1EncoderConfig (a dictionary containing forceScreenContentTools) to the VideoEncoderConfig along these lines:
encoder.configure({ codec: 'av01.0.04M.08', av1: { forceScreenContentTools: true}, width: 1920, height: 1080, bitrate: 2_000_000, framerate: 5, });
This allows an application to encode “screen content”, in particular presentation slides, in a more efficient way supported by the AV1 codec.
This material is typically static, often includes text, a limited set of colors, lots of repetitive content (e.g. straight lines, shapes) for which the encoder can optimize.
See the explainer for a lot of visual examples. This AV1 feature is already supported by WebRTC and enabled for screen sharing MediaStreamTracks so this increases platform consistency.
Blink component
TAG review
None
TAG review status
Not applicable
Risks
Interoperability and Compatibility
None
Gecko: Neutral similar to this situation https://github.com/mozilla/standards-positions/issues/837#issuecomment-1614666364
--
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/CADxkKiJc34b%3DMrX7HhXQP_gZ3wCFg43qHbLJ7mKQqOPe7WYVwA%40mail.gmail.com.
Philipp Hancke
On 10/20/23 2:27 PM, 'Philipp Hancke' via blink-dev wrote:
For those looking for an explainer, hope down to the design docs section (nice explainer, btw!).Contact emails
pha...@microsoft.com, bernar...@microsoft.com
Explainer
None
An FYI review would be nice (especially given the discussions around per-frame/per-codec options), can you send one?
Specification
https://www.w3.org/TR/webcodecs-av1-codec-registration/#dom-av1encoderconfig-forcescreencontenttools
Design docs
https://github.com/fippo/webrtc-explainers/blob/gh-pages/av1-screencontent/index.md
Summary
Adds AV1EncoderConfig (a dictionary containing forceScreenContentTools) to the VideoEncoderConfig along these lines:
encoder.configure({ codec: 'av01.0.04M.08', av1: { forceScreenContentTools: true}, width: 1920, height: 1080, bitrate: 2_000_000, framerate: 5, });
This allows an application to encode “screen content”, in particular presentation slides, in a more efficient way supported by the AV1 codec.
This material is typically static, often includes text, a limited set of colors, lots of repetitive content (e.g. straight lines, shapes) for which the encoder can optimize.
See the explainer for a lot of visual examples. This AV1 feature is already supported by WebRTC and enabled for screen sharing MediaStreamTracks so this increases platform consistency.
Blink component
TAG review
None
TAG review status
Not applicable
Can we go ahead and request a position? It's not clear to me that Mozilla was present when the feature was discussed at https://lists.w3.org/Archives/Public/public-media-wg/2023Apr/0007.html.
Risks
Interoperability and Compatibility
None
Gecko: Neutral similar to this situation https://github.com/mozilla/standards-positions/issues/837#issuecomment-1614666364
Yoav Weiss
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
Mike Taylor
LGTM2
Chris Harrelson
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/CADxkKiJc34b%3DMrX7HhXQP_gZ3wCFg43qHbLJ7mKQqOPe7WYVwA%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+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6c589524-5dba-4d8e-b94a-f594be3f4d83%40chromium.org.