commit | cb4d380ba549c806b4951303681e5dbeb9d6bd47 | [log] [tgz] |
---|---|---|
author | Erik Språng <sprang@webrtc.org> | Fri Feb 14 13:18:47 2020 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Feb 14 13:19:07 2020 +0000 |
tree | 22a1268cee6d2b6af9a9c4dcaecb2deb5b931995 | |
parent | bd710dbacd8f590ef1c2e73a7b4c4602284ef296 [diff] |
Revert "Refactors UlpFec and FlexFec to use a common interface." This reverts commit 11af1d7444fd7438766b7bc52cbd64752d72e32e. Reason for revert: Possible crash Original change's description: > Refactors UlpFec and FlexFec to use a common interface. > > The new VideoFecGenerator is now injected into RtpSenderVideo, > and generalizes the usage. > This also prepares for being able to genera FEC in the RTP egress > module. > > Bug: webrtc:11340 > Change-Id: I8aa873129b2fb4131eb3399ee88f6ea2747155a3 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168347 > Reviewed-by: Stefan Holmer <stefan@webrtc.org> > Reviewed-by: Sebastian Jansson <srte@webrtc.org> > Reviewed-by: Rasmus Brandt <brandtr@webrtc.org> > Commit-Queue: Erik Språng <sprang@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#30515} TBR=brandtr@webrtc.org,sprang@webrtc.org,stefan@webrtc.org,srte@webrtc.org Change-Id: Iddf112d801621c8a4370b853cee3fa42bf2c7fba No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:11340 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168603 Reviewed-by: Erik Språng <sprang@webrtc.org> Commit-Queue: Erik Språng <sprang@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30524}
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 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.