commit | 108ecec51ce5d55bcbe455f7a1cb778dd3cb2b22 | [log] [tgz] |
---|---|---|
author | ossu <ossu@webrtc.org> | Fri Jul 08 15:45:18 2016 |
committer | Commit bot <commit-bot@chromium.org> | Fri Jul 08 15:45:26 2016 |
tree | 98919c850f70b9b85a5a3cf8ae55ea575fd4564b | |
parent | be40296ccef50dd79312c6fce533bfa36b7063dc [diff] |
Removed LEGACY_BITEXACT from neteq_impl.cc and updated the ACM unit tests. I'll be rewriting AcmReceiver soon and am trying to reduce the amount of old stuff that needs to be supported. I've manually checked the outputs of the AcmReceiver bitexactness tests with this change. A large part of the tests are still bitexact, with one section only differing slightly in timings. Nothing audible unless playing the old and new versions back simultaneously. The output of NetEqDecoderTest were also changed due to this CL, although only on android. I built and ran the test locally and compared the audio output manually - the changes were the same as for the other tests; i.e. very slight timing changes for a part of the output. I updated the network stats checksum for android without analyzing it further. I expect it goes hand-in-hand with the changes to the output; i.e. the changes in it are fine because the audio output is fine. Likely, the stats will show changes in the usage of CNG, since that is what the code changes. BUG=webrtc:1361 Review-Url: https://codereview.webrtc.org/2117763002 Cr-Commit-Position: refs/heads/master@{#13415}
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.