Open nirbheek opened 1 year ago
Section A.2 of the AV1 spec requires main and high compliant decoders to decode both 8 and 10 bit streams. Therefore, the desired signaling would only be relevant to a constrained (non-compliant) implementation.
Thanks! Good to know that lack of 10-bit support is a non-compliance issue in Chrome.
I think SDP parameters would still be needed for 12-bit?
The SDP parameter
profile
(AV1seq_profile
) is not sufficient to deduce which bit depth is supported by a peer, from page 32 of the spec:So we need another parameter to signify 8-bit, 10-bit, 12-bit, with room reserved for a possible future 16-bit variant.
This will be a problem very soon, because Chrome only ships with dav1d in 8-bit mode, but services that use WHIP will want 10-bit support for ingest. Mobile apps such as Facebook have already deployed a combined 8-bit + 10-bit dav1d for reels and live streams, and WHIP ingest for live streaming is a real use-case.