3409cfa378
The work was already done to support it, but it wasn't being negotiated in SDP. This means we'll now see 8 H264 payload types instead of 4; one for each combination of BP/CBP profiles, packetization modes 0/1, and RTX/non-RTX. This could be problematic in the future, since we're starting to run out of dynamic payload types (using 25 of 32). Bug: chromium:600254 Change-Id: Ief2340db77c796f12980445b547b87e939170fae Reviewed-on: https://webrtc-review.googlesource.com/77264 Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> Reviewed-by: Erik Språng <sprang@webrtc.org> Reviewed-by: Magnus Jedvert <magjed@webrtc.org> Cr-Commit-Position: refs/heads/master@{#23372}
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