876a3dc88a
This CL fixes 2 issues that affect NetEq simulations. - When using event logs with multiple SSRCs, it does not make sense to use more than a single SSRC. If the user does not provide an SSRC filter, we should use the first SSRC we find and no others. - It is possible for event logs to have a gap in the middle, and sometimes we don't store/mark the gap properly. If is possible to detect gaps by looking at the wallclock time delta between getAudio events. These should be 10 ms nominally, so values greater than 1000 should never happen and indicate an error. Bug: webrtc:11855 Change-Id: Idc3b8a7902be4159da48b063ef5c5c82fd484071 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/181940 Reviewed-by: Jakob Ivarsson <jakobi@webrtc.org> Commit-Queue: Ivo Creusen <ivoc@webrtc.org> Cr-Commit-Position: refs/heads/master@{#31960}
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