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

> Doesn't HEVC have this too?

Implementation status seems to be somewhat hard to describe. I just stumbled over a message in the video-dev slack which suggests it may be around on some Intel drivers?

Speaking more generally we could have a more generic name that covers both AV1 and HEVC without developer pain.
On the other hand we have per-frame QP for some codecs without inheritance which suggests that the codec-specific options without inheritance are a thing already?
Tough decision... which is why we ask! :-)

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

Tough one! As Eugene says, codec specific knobs take precedence so this would give you AV1 without screen content coding tools. Not sure what the difference would be TBH. degradationPreference would be my preferred knob but since webcodecs is per-frame I am not sure this applies.

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

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