- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 Dec 2016 12:22:58 +0000
- To: public-webrtc-logs@w3.org
Hm. I don't like parentheses.... A FIR is observable at both ends of a track, but it's possible that some FIRs are lost in transit, so the counts may be different. So we have: - FIR at the track sender, which is observable by counting incoming FIR packets, represented in the RTCOutboundRTPStreamStats object with remote=false - FIR at the track receiver, which is observable by counting outgoing FIR packets, represented in the RTCInboundRTPStreamStats object with remote=false I don't think FIR count is reported using RTCP, so this stat won't be present if remote=true (although I'm sure @vr000m will correct me if I'm wrong). The qpSum language actually had a different purpose, since you had to divide the sum by different numbers to get the average qp in the two cases, but yes, language like this ought to be a standard phrase. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/107#issuecomment-267583398 using your GitHub account
Received on Friday, 16 December 2016 12:23:04 UTC