Re: [w3ctag/design-reviews] WebCodecs support for AV1 screen content coding tools (Issue #912)

> forceScreenContentTools is AV1 specific and does not interact with resolution or framerate.

Doesn't HEVC have this too? Wondering if it should really be constrained just to AV1 scope (as the name suggests), or consider the possibility of HEVC (or other future codecs) to be able to use this. I suppose while ugly, the other codecs could inherit from `AV1EncoderConfig`.

>  contentHint: 'detail'

What's the expectation when contentHint preference conflicts with what the codec-specific config asks for? For example:

```
encoder.configure({
  codec: 'av01.0.04M.08',
  width: 1920, height: 1080, bitrate: 2_000_000, framerate: 5, 
  contentHint: 'detail'
  av1: { forceScreenContentTools: false}, // for example.
}); 
```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/912#issuecomment-1809867732
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/912/1809867732@github.com>