Comments on: ML in WebRTC: The noise suppression gold rush

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Mon, 16 Nov 2020 20:24:09 +0000

In reply to Seyed Danesh. Yes. My fear is also that the viability of vendors in this space is limited.

By: Seyed Danesh

Seyed Danesh — Mon, 16 Nov 2020 20:05:18 +0000

What a great piece Tsahi, only just read it (a bit late to the party). I think with the fragmentation/modularisation we’re expected to see in WebRTC over the next year, it’s really becoming more and more practical to do this stuff in the browser, but I think some features will always be better in the cloud, and some features will always be better in the browser, for the reasons you said. I think from an engineering point of view we can do a lot of these features today, I think there’s customers/markets that desire them, the biggest question mark is can you make a business model that works. I think the fragmentation of WebRTC if it happens will help a lot to help with plug and play modules on the browser side, but on the cloud side it’s so deep in the technology stack cracking the business model is half the fun. It does look like Krisp will likely be acquired, I’m almost heart broken if that happens since I was hoping they could expand and offer the capability to more and more people, prove it can be done, but likely Discord wouldn’t want that. Maybe one way to make it more viable as a standalone entity is to offer multiple independent capabilities as a technology provider. Not just noise suppression, but many more, maybe then the numbers will look big enough to justify building a longer standing entity servicing this market. As you’ve pointed out there’s a lot of excited ML powered signal processing opportunities up for grabs.

By: Mayur

Mayur — Fri, 06 Nov 2020 06:19:51 +0000

what is javascript code for noise suppression, so that only voice should come in webcam

By: Roman Shpount

Roman Shpount — Wed, 02 Sep 2020 13:05:32 +0000

You should have probably mentioned Microsoft Deep Noise Suppression Challenge https://dns-challenge.azurewebsites.net/Interspeech2020, which was won by Amazon.

They have another one going on right now.

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Tue, 01 Sep 2020 07:18:44 +0000

In reply to Aidar.

First it needs to be implemented by the browser.

Then it needs to be implemented by your microphone/speaker – the intent at least is for this parameter to be passed along with the hardware peripherals and if they support it then enable it on their end.

By: Aidar

Aidar — Tue, 01 Sep 2020 07:15:05 +0000

Hi, nice post!
So, what about noiseSuppression in navigator.mediaDevices.getUserMedia ? Is it improving? Seems it is not working

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Tue, 01 Sep 2020 05:10:00 +0000

In reply to Michael Graves.

Not only nVidia… I was told I also missed Microsoft, and I also forgot about Amazon in this domain.

A better headset is better than any algorithm, which is why it is becoming so hard to purchase good headsets now (they are almost all always out of stock since the pandemic started). The thing is you don’t always have access to a good headset.

By: Michael Graves

Michael Graves — Mon, 31 Aug 2020 22:08:18 +0000

You really should at nVidia’s RTX Voice to your list. It’s every bit as good as those you mention, maybe better. It requires an nVidia RTX GPU. However, there’s a very simple want to lift the hardware constraint to it can work on older GTX cards, too.

Finally, I would be remiss if I did not say that all these things are not equivalent of choosing and using the right hardware. A headset with a boom-mounted, noise cancelling microphone avoids the noise that all these highly technical things attempt to remove after-the-fact.

By: Carlos

Carlos — Mon, 31 Aug 2020 15:50:05 +0000

Thank you for the post! Quite exciting it looks this future!