- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Jun 2021 14:40:04 +0000
- To: public-webrtc-logs@w3.org
Given that the purpose of the specification is to provide hints, and it is in the nature of a hint that the UA may choose to disregard it, it seems hard to test that the behavior is non-conformant (as opposed to "just not very effective"). If we had bandwidth limiting, we could write tests that a) send a synthetic video stream and measures its bandwidth, b) reduce its bandwidth below , and c) analyze the result as "more blur", "fewer frames", or "lower resolution". The two last ones are probably easy to test, while "blurrier" is more fuzzy. Would RTCRtpEncodingParameters.maxBitrate have the desired impact? -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/mst-content-hint/issues/33#issuecomment-869742690 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 June 2021 14:40:07 UTC