commit | 885ba07b654e5874cbf2f8714563c5dc9263cc97 | [log] [tgz] |
---|---|---|
author | Philipp Hancke <philipp.hancke@googlemail.com> | Tue Aug 24 13:56:03 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 10 13:15:05 2021 |
tree | 372973381f70a9dbed01c44ee81bdc3344516621 | |
parent | 5e7a3aedf1f3699d74ee111b48173a031acafb1f [diff] |
Reland "red: generate and parse the red fmtp format" This is a reland of 9d0730942677a520ce7e184d081b4c5a2469fc48 Original change's description: > red: generate and parse the red fmtp format > > generates a fmtp line like > a=fmtp:<red payloadtype> <opus payloadtype>/<opus payloadtype> > and matches the incoming redundant payload types against the > send codec one. Offers without an FMTP line will not use RED. > Redundancy levels of 1 (plus main packet ) to 32 are accepted but > this is not wired up to the encoder since the O/A semantic of > RFC 2198 is not clear. > > This decreases the chance of a collision with the SATIN codec > which also runs on 48khz (but so far does not specify a channelCount of 2) > > BUG=webrtc:11640 > > Change-Id: I8755e5b1e944d105212f1bbe4f330cf4e0753e67 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/229583 > Reviewed-by: Harald Alvestrand <hta@webrtc.org> > Reviewed-by: Henrik Lundin <henrik.lundin@webrtc.org> > Commit-Queue: Harald Alvestrand <hta@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#34848} Bug: webrtc:11640 Change-Id: I9465e489897a8ded9845592477fe14678af7ab61 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/230545 Commit-Queue: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Harald Alvestrand <hta@webrtc.org> Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Henrik Lundin <henrik.lundin@webrtc.org> Cr-Commit-Position: refs/heads/main@{#34965}
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.
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.