- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Dec 2024 20:13:31 +0000
- To: public-webrtc-logs@w3.org
To clarify, degradationPreference (is not nullable and) has no default. Four inputs as possible: 1. `"maintain-framerate"`, 2. `"maintain-resolution"`, 3. `"balanced"`, 4. (the dictionary member is missing) The default is 4 (not 3). Track content hints take effect only in 4 (`degradationPreference` overrides them). The default default (4 and no content hints) _behavior_ is implementation defined. > I believe it probably says somewhere the user agents can adapt the streams in resolution or framerate, ... I don't think it does, but it doesn't say user agents _can't_. So I agree they can do that. > ... which in effect is the same will be the same as using "balanced". This should probably be confirmed. Disagree. 3 and 4 are different. The spec says [balanced](https://w3c.github.io/mst-content-hint/#dom-rtcdegradationpreference-balanced) means: _"Degrade a balance of framerate and resolution."_ This sounds like 50/50 to me: i.e. in the face of congestion, compromise equally on frame rate and resolution. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mst-content-hint/issues/37#issuecomment-2557657682 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 December 2024 20:13:31 UTC