- From: Philipp Hancke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 06 May 2022 13:01:39 +0000
- To: public-webrtc-logs@w3.org
> Thus, we want to send configured bandwidth limitation with available send bandwidth The bandwidth estimator will typically do this automatically for you, (this)[https://webrtcglossary.com/bwe/] is a good introduction. To detect whether the encoder is restricted by bandwidth check the [qualityLimitationReason](https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-qualitylimitationreason) stat. [See here](https://webrtccourse.com/course/webrtc-codelab/module/fiddle-of-the-month/lesson/quality-limitation-stats-in-webrtc/) for a lengthy discussion. -- GitHub Notification of comment by fippo Please view or discuss this issue at https://github.com/w3c/webrtc-provisional-stats/issues/22#issuecomment-1119592911 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 6 May 2022 13:01:41 UTC