commit | 3e98368ec5f8161fff9c02148675256a81a235fd | [log] [tgz] |
---|---|---|
author | Johannes Kron <kron@webrtc.org> | Sun Mar 29 20:17:00 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Sun Mar 29 21:03:27 2020 |
tree | daeae1bb99ed550efa76b803d3c63001fa5f9be9 | |
parent | 8e1824a0d12f6a9806fed9e99b1138cb3ea19eb6 [diff] |
Reland "Distinguish between send and receive codecs" This reverts commit 8e8b36a94a7a7a1fd0f8093979a406afa56e18c1. Reason for revert: The CL has been improved with the following changes, - Fixed negotiation of send/receive only clients. - Handles the implicit assumption that any H264 decoder also can decode H264 constraint baseline. Original change's description: > Distinguish between send and receive codecs > > Even though send and receive codecs may be 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: Id119560becadfe0aaf861c892a6485f1c2eb378d > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/165763 > Commit-Queue: Johannes Kron <kron@webrtc.org> > Reviewed-by: Steve Anton <steveanton@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#30284} Change-Id: I834ed48ee78d04922c73e2836165e476925e1cc5 Bug: chromium:1029737 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/168605 Commit-Queue: Johannes Kron <kron@webrtc.org> Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Reviewed-by: Karl Wiberg <kwiberg@webrtc.org> Reviewed-by: Johannes Kron <kron@webrtc.org> Reviewed-by: Henrik Boström <hbos@webrtc.org> Reviewed-by: Sergey Silkin <ssilkin@webrtc.org> Reviewed-by: Steve Anton <steveanton@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30932}
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.