| commit | f22af3cca7cfe517e4126db4b7083475722c3e6d | [log] [tgz] |
|---|---|---|
| author | Johannes Kron <kron@webrtc.org> | Mon Dec 09 14:48:39 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Mon Dec 09 14:48:55 2019 |
| tree | 2c35f3034cc5bd5333ff309ffd51bd7758d7cd2c | |
| parent | 18314bd8d2cb27fa58e4d304bbc428e3ed1736ba [diff] |
Revert "Distinguish between send and receive video codecs" This reverts commit 18314bd8d2cb27fa58e4d304bbc428e3ed1736ba. Reason for revert: Breaks downstream test. Original change's description: > Distinguish between send and receive video codecs > > Even though send and receive codecs are the same, > they might have different support in HW. > Distinguish between send and receive codecs to be able to keep > track of which codecs have HW support. > > Bug: chromium:1029737 > Change-Id: I16a80da44c5061ca42f2aabda76e6bf0b879bf7b > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/161306 > Reviewed-by: Anders Carlsson <andersc@webrtc.org> > Reviewed-by: Steve Anton <steveanton@webrtc.org> > Commit-Queue: Johannes Kron <kron@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#30041} TBR=steveanton@webrtc.org,andersc@webrtc.org,kron@webrtc.org Change-Id: I7e5807460006db613e9b3b369ec6036b88f164fd No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:1029737 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/161662 Reviewed-by: Johannes Kron <kron@webrtc.org> Commit-Queue: Johannes Kron <kron@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30042}
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.