- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Mon, 08 Oct 2018 22:40:49 +0000
- To: public-webrtc-logs@w3.org
As I see it, the current proposal empowers applications to precisely tune the configuration. I am wondering whether something less powerful but simpler could not cover most use cases. Having less expressiveness has a few advantages, a user agent might better react if something goes wrong like CPU overload. Taking example 6.1 of a temporal-only scalable codec as an example, do we need to support both examples, or could we just decide to only support the first one for instance? I haven't looked at what current scalable codec implementations expose in terms of API. Do they all expose the level of granularity required by the current proposal? SVC has quality scalability. Is that something we should consider to expose? -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-pc/pull/1991#issuecomment-428002022 using your GitHub account
Received on Monday, 8 October 2018 22:40:50 UTC