- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Mon, 01 Aug 2022 07:57:00 +0000
- To: public-webrtc-logs@w3.org
targetBitrate = 0 may work depending on the implementation - hoping there's no implementation that defaults this to 0 during ramp up time even though it is sending, I don't know what Chromium does. limited has the benefit of being explicit and feature detectable, but we could make targetBitrate definition more explicit about this. qualityLimitationReason does not say whether or not you are sending, only whether or not a limitation is occurring (e.g. could simply reduce resolution or frame rate without affecting sending). And while it may be possible do report something smart per-stream there, the implementation today reports the same QLR value for all outbound-rtps. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/650#issuecomment-1200848874 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 1 August 2022 07:57:02 UTC