W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2019

Re: [mediacapture-main] Echo Cancellation (#597)

From: Jai Gupta via GitHub <sysbot+gh@w3.org>
Date: Thu, 23 May 2019 10:59:42 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-495171742-1558609181-sysbot+gh@w3.org>
I don't understand why are you talking about performance or guarantees or how to do echo cancellation? It is totally ok if browsers attempt to remove echo but fail to do so due to limitations.

I also understand that Chrome may choose to remain non-compliant to specs until they wish to.

All I am saying is that different browsers are interpreting specs differently. Chrome, in this case, insists that by not attempting to remove all sounds (only working on sound from remote peer) they are not in violation with specs. So, do we need to make specs more explicit or are specs clear enough?

GitHub Notification of comment by jgupta
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/597#issuecomment-495171742 using your GitHub account
Received on Thursday, 23 May 2019 10:59:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:23 UTC