commit | e57b266a20334e47f105a0bd777190ec8c6562e8 | [log] [tgz] |
---|---|---|
author | Steve Anton <steveanton@webrtc.org> | Fri Jan 17 02:47:11 2020 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 17 02:47:23 2020 |
tree | cf4ad0027f01e6e39ff038b083c6d5fe3230eab6 | |
parent | e4ddaa94954081f140fa7f0bce178cea360bd797 [diff] |
Revert "Distinguish between send and receive codecs" This reverts commit c0f25cf762a6946666c812f7a3df3f0a7f98b38d. Reason for revert: breaks negotiation with send-only clients (webrtc_video_engine.cc:985): SetRecvParameters called with unsupported video codec: VideoCodec[96:H264] (peer_connection.cc:6043): Failed to set local video description recv parameters. (INVALID_PARAMETER) (peer_connection.cc:2591): Failed to set local offer sdp: Failed to set local video description recv parameters. 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} TBR=steveanton@webrtc.org,kron@webrtc.org Change-Id: Iacb7059436b2313b52577b65f164ee363c4816aa No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: chromium:1029737 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/166420 Reviewed-by: Steve Anton <steveanton@webrtc.org> Commit-Queue: Steve Anton <steveanton@webrtc.org> Cr-Commit-Position: refs/heads/master@{#30292}
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.