Re: [mediacapture-main] New audio acquisition constraints (#671)

The subject matter of optimization of SST input to remote services raises the question why SST is not shipped in the FOSS browser by default (https://webwewant.fyi/wants/55/) for users to "optimize" or otherwise improve their own implementation given and based on the state of the art in commercial domains? That is, if speech is specified for `getUserMedia()` supply the source code to be able to actually check the work. Else, no matter how "optimized" the input is, if the "remote service" is censoring or otherwise incapable of parsing input, there is no way to determine if "echo cancellation, automatic gain control, etc." have and effect whatsoever on the privately held concerns the output of `MediaStreamTrack` of kind SST or category speech is being sent to - unless the remote web service https://bugs.chromium.org/p/chromium/issues/detail?id=816095 discloses in full the algorithms in use to process input. 

That is, how do you know, and how can you, and more importantly, individuals other than the web service, check the efficacy of applying a constraint, would they not be entirely beholden on the web service being up and running to verify results of an algorithm?

-- 
GitHub Notification of comment by guest271314
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/671#issuecomment-605373404 using your GitHub account

Received on Saturday, 28 March 2020 01:14:47 UTC