f88aa97c52
The video encoder should be informed of incoming LossNotification RTCP messages. Since it is unaware of RTP sequence numbers, or anything else RTP-related, the sequence numbers mentioned in the RTCP message must first be mapped to timestamps, since those are meaningful to the encoder. This CL introduces RtpSequenceNumberMap, which maps RTP sequence numbers to timestamps, while providing: 1. Capping the number of entries. 2. Wrap-around handling. RtpSequenceNumberMap also remembers which packets were first and/or last in the frame. Later CLs will wire this up. Bug: webrtc:10501 Change-Id: Ie0662cdb5706a3bcf63aa2934816a9df88439357 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/130497 Commit-Queue: Elad Alon <eladalon@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Cr-Commit-Position: refs/heads/master@{#27448}
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.
Development
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.
More info
- Official web site: http://www.webrtc.org
- Master source code repo: https://webrtc.googlesource.com/src
- Samples and reference apps: https://github.com/webrtc
- Mailing list: http://groups.google.com/group/discuss-webrtc
- Continuous build: http://build.chromium.org/p/client.webrtc
- Coding style guide
- Code of conduct