commit | 84916937b70472715efe5682bc273e91c3a72695 | [log] [tgz] |
---|---|---|
author | Taylor Brandstetter <deadbeef@webrtc.org> | Mon Jun 25 22:50:26 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Jun 25 23:56:39 2018 |
tree | 9bb205be9dc6dda2f8c0adef0144397c5bf1c24c | |
parent | 111fdfd7320416faf92e4b4c6d37d0e7021a837c [diff] |
Update packetsLost and jitter stats any time a packet is received. Before this CL, the packetsLost and jitter stats (as returned by GetStats, at the API level) were only being updated when an RTCP SR or RR is generated. According to the stats spec, "local" stats like this should be updated any time a packet is received. This CL also fixes some minor issues with the calculation of packetsLost (and fractionLost): * Packets weren't being count as lost if lost over a sequence number rollover. * Temporary periods of "negative" loss (caused by duplicate or out of order packets) weren't being accumulated into the cumulative loss counter. Example: Period 1: Received packets 1, 2, 4 Loss over that period: 1 (expected 4 packets, got 3) Reported cumulative loss: 1 Period 2: Received packets 3, 5 Loss over that period: -1 (expected 1 packet, got 2) Reported cumulative loss: 1 (should be 0!) Landing with NOTRY because Android compile bots are broken for an unrelated reason. NOTRY=True Bug: webrtc:8804 Change-Id: I840ba34de8957b1276f6bdaf93718f805629f5c8 Reviewed-on: https://webrtc-review.googlesource.com/50020 Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Reviewed-by: Oskar Sundbom <ossu@webrtc.org> Cr-Commit-Position: refs/heads/master@{#23731}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.