[discuss-webrtc] PSA: Turning off the echo detector in M84

[Olga Sharonova]

Hi everybody,

2 weeks from now the echo detector implemented in the audio processing module will be turned off in Chromium top-of-tree, in time for the M84 cut. This means that the echo detector stats googResidualEchoLikelihood and googResidualEchoLikelihoodRecentMax will no longer be present in the legacy callback-based getStats() API.

The background is that we’ve seen limited actionable value of these stats and therefore, taking the CPU complexity of the echo detector into account, we think it is better to switch it off.

Regards,

Olga

[shyam chakraborty]

So, is the screw is gradually being tightened from open source to  gradually paid versions?

Just wondering ...

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/7a445700-0f3a-4572-a01e-bfb12010ab23%40googlegroups.com.

[Henrik Lundin]

We've had a few questions come in, so I'd like to make a couple of clarifications:

- This only affects the echo detector metics. It does not in any way change how the echo cancellation (AEC) works.

- The standardized echo metrics echoReturnLoss and echoReturnLossEnhancement are not affected.

Sincerely,

/Henrik