Correct/update the activation of the multi-channel processing in APM
This CL removes the experimental status of the multi-channel processing in APM, and accordingly updates the variable naming. It also splits the activation of multi-channel processing to be separate for render and capture. Bug: webrtc:10859 Change-Id: I0e5d04dcb94b6637c33d97146231b8ddddbaea39 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/160707 Commit-Queue: Per Åhgren <peah@webrtc.org> Reviewed-by: Sam Zackrisson <saza@webrtc.org> Cr-Commit-Position: refs/heads/master@{#29926}
This commit is contained in:
@ -256,8 +256,14 @@ class RTC_EXPORT AudioProcessing : public rtc::RefCountInterface {
|
||||
// default rate is currently selected based on the CPU architecture, but
|
||||
// that logic may change.
|
||||
int maximum_internal_processing_rate;
|
||||
// Force multi-channel processing on playout and capture audio. This is an
|
||||
// experimental feature, and is likely to change without warning.
|
||||
// Allow multi-channel processing of render audio.
|
||||
bool multi_channel_render = false;
|
||||
// Allow multi-channel processing of capture audio when AEC3 is active
|
||||
// or a custom AEC is injected..
|
||||
bool multi_channel_capture = false;
|
||||
|
||||
// Deprecated.
|
||||
// TODO(peah): Remove.
|
||||
bool experimental_multi_channel = false;
|
||||
} pipeline;
|
||||
|
||||
|
Reference in New Issue
Block a user