webrtc-stats
webrtc-stats copied to clipboard
w3c
WebRTC Statistics
According to the definition of `estimatedPlayoutTimestamp`, we can use `audioTrackStats.estimatedPlayoutTimestamp - videoTrackStats.estimatedPlayoutTimestamp` to get the AV sync. https://w3c.github.io/webrtc-stats/#dom-rtcinboundrtpstreamstats-estimatedplayouttimestamp I have been using `trackIds` in `RTCMediaStreamStats` to find the associated audio...
@henbos has done a whiteboard drawing of the current stats graph which I find *very* useful: https://photos.app.goo.gl/6P0i4AV1E3szctTl1 Would be great to add this to the spec too as it explains...
https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-framesencoded says > Only exists for video However, https://w3c.github.io/webrtc-stats/#dom-rtcoutboundrtpstreamstats-totalencodetime does not have that restriction (even though it is missing in Chrome for audio) and we typically say that you can...
It's possible that TCP candidates can be coerced into acting as portscanning agents. The numbers need to be specified in such a way that they don't reveal portscanning info.
The type definition for ["outbound-rtp"](https://w3c.github.io/webrtc-stats/#dom-rtcstatstype-outbound-rtp) says: ``` Statistics for an outbound RTP stream that is currently sent with this {{RTCPeerConnection}} object. ``` But [The RTP statistics hierarchy](https://w3c.github.io/webrtc-stats/#the-rtp-statistics-hierarchy) says: ``` RTP...
When filtering by sender or receiver, the stats selection algorithm is as follows: ``` - If selector is an RTCRtpSender, gather stats for and add the following objects to result:...
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...
Currently statistics relating to video tracks do not measure video device errors, such as: o Video Camera: Count of frames dropped due to wrong format received o Video Camera: Count...
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?
Currently in RTCAudioHandlerStats we have audioLevel and totalAudioEnergy, but no estimate of the level of noise and signal. In Edge, we collect the following stats: https://rawgit.com/aboba/edgertc/master/msortc-rs4.html#msaudiorecvsignal*