commit | f93be584f740854a14a752e5c39947b4ffabd7e5 | [log] [tgz] |
---|---|---|
author | ossu <ossu@webrtc.org> | Wed Jul 13 13:31:30 2016 |
committer | Commit bot <commit-bot@chromium.org> | Wed Jul 13 13:31:37 2016 |
tree | f92e619ceb02f0ac48e0521352fe6e4f217e7ae7 | |
parent | 95eb1ba0db79d8fd134ae61b0a24648598684e8a [diff] |
Revert of WebRtcVoiceEngine: Use AudioDecoderFactory to generate recv codecs. (patchset #10 id:200001 of https://codereview.webrtc.org/2072753002/ ) Reason for revert: For some reason, payload_type_mapper.cc is not being picked up in Chrome builds, leading to undefined references. Reverting while investigating. Original issue's description: > WebRtcVoiceEngine: Use AudioDecoderFactory to generate recv codecs. > > Changed WebRtcVoiceEngine to present receive codecs from the formats > provided by its decoder factory. Added supported formats to > BuiltinAudioDecoderFactory. Added helper functions for creating some > simple decoder factories for mocking. > > Created a PayloadTypeMapper for assigning payload types to formats. I > think we'll eventually want to use this further up, or possibly in > both the audio and video sides. It would be best if the engines didn't > have to talk payload types at all, but it might be more difficult to > get around when payload types depend on each-other, like the RTX > codecs for video. > > This CL also includes some changes to rtc::Optional. I've put them in > a separate CL that should (or should not) land first, making these > changes void. > See: https://codereview.webrtc.org/2072713002/ > > BUG=webrtc:5805 > > Committed: https://crrev.com/95eb1ba0db79d8fd134ae61b0a24648598684e8a > Cr-Commit-Position: refs/heads/master@{#13459} TBR=ivoc@webrtc.org,tina.legrand@webrtc.org,tommi@webrtc.org # Skipping CQ checks because original CL landed less than 1 days ago. NOPRESUBMIT=true NOTREECHECKS=true NOTRY=true BUG=webrtc:5805 Review-Url: https://codereview.webrtc.org/2151453002 Cr-Commit-Position: refs/heads/master@{#13460}
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. This page is maintained by the Google Chrome team.
See http://www.webrtc.org/native-code/development for instructions on how to get started developing with the native code.