commit | a7678667fc726979ca27d2429689d5735cca425d | [log] [tgz] |
---|---|---|
author | Taylor Brandstetter <deadbeef@webrtc.org> | Mon Oct 30 22:52:53 2017 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Oct 30 22:52:59 2017 |
tree | 87845035f4aff9bf3b59648a5cfc7635e2d47f0e | |
parent | 33f69db1c8a51a212995a26e3b77d90cccc685c7 [diff] |
Revert "Add helper functions for migrating to new video codec factories" This reverts commit 1c9623c70db42550d152c127e01434004087f743. Reason for revert: Breaks brace initialization: cricket::VideoDecoderParams params = { "deadbeef" }; I suggest adding an initializer list constructor. Original change's description: > Add helper functions for migrating to new video codec factories > > This CL adds helper functions in media/engine/convert_legacy_video_factory.h to > convert from the old WebRtcVideoEncoder and WebRtcVideoDecoder to the new > webrtc::VideoEncoder and webrtc::VideoDecoder. > > The purpose is to make it as easy as possible for clients to migrate to the new > API and allow us to stop depending on the internal SW codecs as soon as possible. > > There still exists an ugly decoder adapter class in the video engine. The reason > is that we need to continue to pass in the |receive_stream_id| decoder params to > some legacy clients. > > Bug: webrtc:7925 > Change-Id: I43ff03e036411a85d4940fe517a34489f171d698 > Reviewed-on: https://webrtc-review.googlesource.com/15181 > Commit-Queue: Magnus Jedvert <magjed@webrtc.org> > Reviewed-by: Anders Carlsson <andersc@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#20475} TBR=magjed@webrtc.org,andersc@webrtc.org Change-Id: I0d1084dc86979fbca748d9ba287d1db3dbe52b44 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:7925 Reviewed-on: https://webrtc-review.googlesource.com/17160 Reviewed-by: Taylor Brandstetter <deadbeef@webrtc.org> Commit-Queue: Taylor Brandstetter <deadbeef@webrtc.org> Cr-Commit-Position: refs/heads/master@{#20486}
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.