- From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
- Date: Thu, 15 Jun 2017 09:04:55 +0000
- To: "Cullen Jennings (fluffy)" <fluffy@cisco.com>, Taylor Brandstetter <deadbeef@google.com>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 14/06/17 20:41, Cullen Jennings (fluffy) wrote: > >> 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. On an audio track there are constraints to switch gain control and noise suppression off with the motivation "so that the audio is not altered". Perhaps the encoding machinery can use this info to accomplish something similar which we would get with an audio content hint with the allowed values 'speech' and 'music'? > > 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 Thursday, 15 June 2017 09:05:32 UTC