b2be392c70
The code incorrectly assumed that codecs exist on a per-mid/transceiver basis, but codec payload types are unique on a per-transport basis and in practise most applications use BUNDLE (single transport for the entire PC). This CL makes the codecs per-transport instead of per-transceiver. We still need to iterate transceivers because codecs are exposed on a per-transceiver basis and as shown in https://jsfiddle.net/henbos/7kqxgnr8/ it is possible for FMTP lines to be different on different m= sections despite BUNDLE. Manual testing shows that this CL brings down the number of "codec" stats in Google Meet 50p from 872 objects to 43 objects. Bug: webrtc:14414 Change-Id: Ic854b31bd595799554b99fff22cbd48264ebd141 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/273707 Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> Reviewed-by: Philipp Hancke <phancke@microsoft.com> Commit-Queue: Henrik Boström <hbos@webrtc.org> Cr-Commit-Position: refs/heads/main@{#37989}
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: https://ci.chromium.org/p/webrtc/g/ci/console
- Coding style guide
- Code of conduct
- Reporting bugs
- Documentation