- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Jan 2024 18:06:29 +0000
- To: public-webrtc-logs@w3.org
From the discussion, it seems we want to do two things: 1. Be able to say this stream that we encode is less important than this other one. This would allow UA to fine tune their degradation heuristics. 2. Tell the UA that we prefer high quality, or battery life. And then UA might want to tweak its encoder. For 1, we already have https://w3c.github.io/webrtc-priority/#rtc-priority-type so maybe we do not need anything? For 2, I wonder whether this should not be a global setting at the scope of the peer connection. Maybe a preference with values like "quality" and "powerEfficiency" (plus "") would be good enough. Note also, that, if CPU is what can be controlled, this could also be applied to the receiving side, which could reduce somehow its complexity by changing the rendering (longer audio chunks, dropping frame rate to 30fps...). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/191#issuecomment-1894249533 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 January 2024 18:06:31 UTC