- From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Oct 2021 16:27:00 +0000
- To: public-webrtc-logs@w3.org
WebRTC-SVC isn't a new specification. It was originally developed in the ORTC CG, so it predates much of the WebRTC 1.0 specification, including "Unified Plan" and many of the sections of WebRTC Extensions. scalability mode info was added to MC for use by WebCodecs, not WebRTC. So far, I haven't seen much MC usage by WebRTC developers. MC wasn't designed to be convenient for use in WebRTC and the additional information it provides isn't actionable in most cases. referenceScaling isn't really an SVC issue. It also affects the ability to change resolution without a keyframe in a stream with no layers. For a WebRTC application not using SVC, it isn't actionable because the API doesn't have a way to tell the encoder to only make resolution changes at keyframe boundaries. "prefer-resolution" is just a hint. Since reference scaling is required for a VP8/VP9/AV1 decoder to be compliant, IMHO the lack of support is more of a "bug" than a "capability". Similarly, "power efficiency" is more actionable in WebCodecs than WebRTC. WebRTC doesn't have the equivalent of WebCodecs HardwareAcceleration enum. -- GitHub Notification of comment by aboba Please view or discuss this issue at https://github.com/w3c/webrtc-svc/issues/49#issuecomment-947832616 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 20 October 2021 16:27:01 UTC