W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2017

A19 - Was: Re: Review of May 15 WebRTC 1.0 draft -

From: Cullen Jennings (fluffy) <fluffy@cisco.com>
Date: Wed, 14 Jun 2017 18:38:46 +0000
To: Taylor Brandstetter <deadbeef@google.com>
CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <09B41D6D-B17B-44AF-9532-5858724747D4@cisco.com>

> On Jun 7, 2017, at 2:14 AM, Taylor Brandstetter <deadbeef@google.com> wrote:
>   A19             The web API must provide means for the web
>                    application to indicate the type of audio signal
>                    (speech, audio) for audio stream(s) / stream
>                    component(s).
> Is this satisfied by the ability to disable voice activity detection? This sounds a lot like MediaStreamTrack content hints. Maybe we could consider adding that feature to WebRTC 1.0.

Yah, I think this was meant to get at exactly what  https://wicg.github.io/mst-content-hint/#audio-content-hints does. 

That allows the codec to have a much better idea about how to encode the media. I'd be in favor of adding that to the appropriate specs.
Received on Wednesday, 14 June 2017 18:39:20 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:51 UTC