Revert "Add core multi-channel pipeline in AEC3"
This reverts commit f3a197e55323aee974a932c52dd19fa88e5d4e38. Reason for revert: Speculative revert, as this may'be broken some build bots Original change's description: > Add core multi-channel pipeline in AEC3 > This CL adds basic the basic pipeline to support multi-channel > processing in AEC3. > > Apart from that, it removes the 8 kHz processing support in several > places of the AEC3 code. > > Bug: webrtc:10913 > Change-Id: If5b75fa325ed0071deea94a7546cb4a7adf22137 > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/150332 > Commit-Queue: Per Åhgren <peah@webrtc.org> > Reviewed-by: Sam Zackrisson <saza@webrtc.org> > Cr-Commit-Position: refs/heads/master@{#29017} TBR=saza@webrtc.org,peah@webrtc.org Change-Id: I877d2993b9ccf024bd1d57bca1513c3e24d0bed3 No-Presubmit: true No-Tree-Checks: true No-Try: true Bug: webrtc:10913 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/150940 Reviewed-by: Ilya Nikolaevskiy <ilnik@webrtc.org> Commit-Queue: Ilya Nikolaevskiy <ilnik@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29022}
This commit is contained in:
committed by
Commit Bot
parent
ddd50ef921
commit
e3e30ae5c5
@ -22,7 +22,7 @@ namespace webrtc {
|
||||
|
||||
// Verifies the check for non-null fft buffer.
|
||||
TEST(RenderBuffer, NullExternalFftBuffer) {
|
||||
MatrixBuffer block_buffer(10, 3, 1, kBlockSize);
|
||||
MatrixBuffer block_buffer(10, 3, kBlockSize);
|
||||
VectorBuffer spectrum_buffer(10, kFftLengthBy2Plus1);
|
||||
EXPECT_DEATH(RenderBuffer(&block_buffer, &spectrum_buffer, nullptr), "");
|
||||
}
|
||||
@ -30,7 +30,7 @@ TEST(RenderBuffer, NullExternalFftBuffer) {
|
||||
// Verifies the check for non-null spectrum buffer.
|
||||
TEST(RenderBuffer, NullExternalSpectrumBuffer) {
|
||||
FftBuffer fft_buffer(10);
|
||||
MatrixBuffer block_buffer(10, 3, 1, kBlockSize);
|
||||
MatrixBuffer block_buffer(10, 3, kBlockSize);
|
||||
EXPECT_DEATH(RenderBuffer(&block_buffer, nullptr, &fft_buffer), "");
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user