| commit | d89fa97356bc1a276fd1319f3b57232f2e8cdc01 | [log] [tgz] |
|---|---|---|
| author | minyue@webrtc.org <minyue@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> | Fri Jul 18 12:28:28 2014 |
| committer | minyue@webrtc.org <minyue@webrtc.org@4adac7df-926f-26a2-2b94-8c16560cd09d> | Fri Jul 18 12:28:28 2014 |
| tree | 175828d54d726861a29f80ec9c0fdfde3e93efe4 | |
| parent | c6176548bfae24bcd7ff110d13a7e5139ef6bdb9 [diff] |
This is related to an earlier CL of enabling Opus 48 kHz. https://webrtc-codereview.appspot.com/16619005/ It was reverted due to a build bot error, which this CL is to fix. The problem was that when audio conference mixer receives audio frames all at 48 kHz and mixed them, it uses Audio Processing Module (APM) to do a post-processing. However the APM cannot handle 48 kHz input. The current solution is not to allow the mixer to output 48 kHz. TEST=locally solved https://webrtc-codereview.appspot.com/16619005/ BUG= R=andrew@webrtc.org Review URL: https://webrtc-codereview.appspot.com/20779004 git-svn-id: http://webrtc.googlecode.com/svn/trunk/webrtc@6730 4adac7df-926f-26a2-2b94-8c16560cd09d