- From: guidou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Jun 2021 15:09:16 +0000
- To: public-webrtc-logs@w3.org
> > Handling the signal might result in better performance by the sink. > > Understood, though if web page implements audio glitch-free rendering based on using that signal on a specific browser, it becomes important for UAs to support this mechanism using the same algorithms/timing. > Ditto if we are talking about preserving battery life in case, say rendering can increase/decrease its frame rate. > > As an example, some websites have good quality calls (say ramp-up) if UAs have various tools like TWCC or REMB. > This makes having these tools part of 'correct' user experience, even though this is not a correctness issue per se. I don't disagree with what you say here, but my impression is that the MediaStream-related specs generally do not define specific performance requirements as correctness, so I would see the glitch/battery examples you mention as a quality issue more than a correctness issue. -- GitHub Notification of comment by guidou Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/24#issuecomment-852204015 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 June 2021 15:09:33 UTC