- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Feb 2017 14:12:21 +0000
- To: public-webrtc-logs@w3.org
The actualEncBitrate should be computable from RTCRTPStreamStats.bytesSent. The googTargetEncBitrate should either be the same as RTCIceCandidatePairStats.availableOutgoingBitrate or the same as sum(RTCOutboundRTPStreamStats.targetBitrate) for all (video?) tracks, depending on how it's defined. In either case, it should be computable from existing values, so I don't see a reason to add them. (Once we have all the stats mentioned above wired up, we could write a test to run old and new stats against each other, checking that the stats (or the stats we can compute from them) are ~equal. If they aren't, we have the definitions wrong.) -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/155#issuecomment-278010728 using your GitHub account
Received on Tuesday, 7 February 2017 14:12:27 UTC