WebCodecs: Support for AV1 Screen Content Coding

[aboba]

WebKittens

@marcoscaceres

Title of the spec

AV1 WebCodecs Registration

URL to the spec

https://www.w3.org/TR/webcodecs-av1-codec-registration/#av1-encoder-config

URL to the spec's repository

https://github.com/w3c/webcodecs/blob/main/av1_codec_registration.src.html

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

Support for configuration of AV1 Screen Content Coding Tools in WebCodecs has been added to the AV1 Registration page, along with per-frame QP support. The Chromium tracking bug is here: https://bugs.chromium.org/p/chromium/issues/detail?id=1464862

As shown in the graph included with the tracking bug, configuration of AV1 screen content coding tools appears to be effective.

[fippo]

The functionality ended up being part of contentHint (#274) so this has been overtaken by events.

[marcoscaceres]

Might defer to @youennf or @jyavenard...

[youennf]

@aboba, can you clarify whether the ask is for https://w3c.github.io/webcodecs/av1_codec_registration.html#dom-videoencoderencodeoptionsforav1-quantizer or for https://w3c.github.io/webcodecs/av1_codec_registration.html#dom-av1encoderconfig-forcescreencontenttools? If the latter, can we safely close this issue or should we wait for https://github.com/w3c/webcodecs/pull/752 resolution?

[marcoscaceres]

@aboba, any update? We are inclined to close this unless we hear back from you.

[aboba]

@marcoscaceres We merged PR 752. Instead of explicit codec-specific encoder configuration, we are now using Content Hints, which can be applied to any supported codec.

[aboba]

@youennf This ask was for support of Screen Content Coding. quantizer is now supported across multiple codecs, but that's a separate question.