henbos

Do you know if Chromium's implementation was based on something we can reference?

"Likelihood of echo" has a similar problem to that of rates - it's a snapshot. "Over the last 10s" is useful but 10s is arbitrary. With using counters instead of...

I'm afraid the API is designed such that a caller should not need to know about other getStats-callers. Any "since last call to getStats" logic means invoking getStats affects all...

The recent change was noted by @jan-ivar: > To test Chrome, I used an in-content device picker to pick my BRIO: I get channelCount: 1 with {audio: true} in M88,...

Per summary over at https://github.com/w3c/webrtc-extensions/issues/63#issuecomment-786118846, would it make sense to mandate default channel count or is this something that should be up to the browser? @guidou what do you think...

@guidou says the default likely changed here: https://chromium-review.googlesource.com/c/chromium/src/+/2593122

Could we do the same for channelCount without having to revert the culprit CL?

> E.g. going to Audio MIDI Setup and choosing my Logitech BRIO makes it the default microphone on macOS and Firefox, and now {audio: true} gives you channelCount 2 instead...

For what it's worth, the Chromium's change in default channel count was accidental and there is a revert in progress. This will make implementing https://github.com/w3c/webrtc-extensions/issues/63 a smoother transition, whether or...

Why do users have to be able to override defaults?