henbos
henbos
The RTCTransportStats object's [bytesSent](https://w3c.github.io/webrtc-stats/#dom-rtctransportstats-bytessent) is said to be: > Represents the total number of bytes received on this PeerConnection, i.e., not including headers or padding. There's also packetsSent: > Represents...
On the sender side we have multiple "rids", but on the receiver side we only have a single stream. How to tell which stream it correlates to?
"outbound-rtp" is now said to cover both RTP and RTX stats. This makes sense because RTP and RTX streams map 1:1 so there is no ambiguity there. In the implementation...
These used to exist on the "track" stats and currently remain on the handler stats (a.k.a. "sender" and "receiver"). Decide whether they should remain here or if we want to...
[RTCPeerConnectionStats](https://w3c.github.io/webrtc-stats/#pcstats-dict*) does not contain PC state information. - If we fix #483 we have iceState on a per-transport basis. Would it make sense to compute [iceConnectionState](https://w3c.github.io/webrtc-pc/#dom-peerconnection-ice-connection-state) and expose it on...
Related to https://github.com/w3c/webrtc-stats/pull/492
System, process and tab CPU usage directly affects the performance of WebRTC and WebRTC has ways of adapting depending on available CPU. While not in direct control of WebRTC, there...
The non-standardized Chromium getStats contains the following stat: ``` // An instantaneous measurement of the likelihood that there is echo. // This is a send side stat with range 0...
When downscaling a resolution, there are at least three ways you could do it if the new aspect ratio is not the same as the original one: - Stretch it....
MediaStreamTrack.getSettings().frameRate is either an exact frame rate or a frame rate range. > The exact frame rate (frames per second) or frame rate range. If video source's pre-set can determine...