henbos

I think this has either been resolved already or no longer applicable, and we can always add new metrics if we want ended, but I don't think that is needed...

I think we can defer to the APIs rather than getStats for this

Implementations may be doing several things to improve quality, like echo cancellation, synthesizing samples to conceal packet loss, and noise suppression. Strategies are, however, implementation-specific. This can make standardizing metrics...

Action Item: Talk to an audio engineer to see if this is something that we could measure :)

@ivocreusen Do we have any estimates of background noise that could be exposed as stats? E.g. totalBackgroundAudioEnergy that would be <= [totalAudioEnergy](https://w3c.github.io/webrtc-stats/#dom-rtcinboundrtpstreamstats-totalaudioenergy)? This is another issue I would like to...

I would propose the metric to be well defined in _what_ it is a measurement of (audio energy), without specifying _how_ the measurement is obtained. And then declare inaccurate estimates...

Talked to an audio engineer, his take roughly: - Not sure about the use case of this in a web conferencing app. Questioning how interesting it is to implement. -...

I'm not sure what to do with this one so I'm removing the TPAC label

@vr000m If you still want this (or #383) to be discussed at TPAC feel free to prepare a slide for it.

Are there any standards to reference with regards to how to detect echo?