5f7bfbe6c6
It may happen that if we have simulcast track with, let's say, 2 streams A and B, we can receive frame X on A and then receive it again on B when there is a switch from A to B. TO correctly handle it we need to skip second receive of X. Later we need to add metric which will show how many frames were in between when X was received twice. Bug: webrtc:11557 Change-Id: I8c52a78674b62387f520a587f51e209ed7c0b0bc Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/176853 Commit-Queue: Artem Titov <titovartem@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31488}
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 here 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