- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Fri, 27 Oct 2017 00:28:42 +0000
- To: public-webrtc-logs@w3.org
Assuming you're not sending lossless vIdeo, it's always going to adjust quality based on whatever bitrate it has available (constantly changing). In that sense it is always "bandwidth limited". Despite quality being important, in terms of "is there adaptation going on", the QP would be meaningless unless you define thresholds, but this might be opening a can of worms. We thought that if there is need for adaptation, and it's only changing QP but not resolution and/or framerate there would be a bug in the WebRTC implementation. As such, we only need to care about resolution and/or framerate. If you have crappy quality, you probably also have crappy resolution/framerate. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/256#issuecomment-339838513 using your GitHub account
Received on Friday, 27 October 2017 00:28:45 UTC