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

Re: [mediacapture-main] Update getusermedia.html (#651)

From: guest271314 via GitHub <sysbot+gh@w3.org>
Date: Mon, 16 Dec 2019 23:45:54 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-566301849-1576539952-sysbot+gh@w3.org>
> I think step 1 is providing a compelling use case.
> 
> Frankly, capturing browser audio output at that late a stage only to bring it back into the browser, smells like a workaround for something that should be doable directly using components like `MediaStreamTrack` and maybe web audio.
> 
> For instance—did I see you mention web speech earlier?—I recently made some design recommendations in [mozilla/standards-positions#170 (comment)](https://github.com/mozilla/standards-positions/issues/170#issuecomment-509873541) to make `SpeechRecognition` play better with tracks. If your need here stems from an API shortcoming like that, then I'd try to fix that API instead first.
> 
> I'd hope we could do better for any use case short of media device stack testing (which is what we use the Monitor device for in Firefox). If you do find compelling use cases, _and_ can get vendor interest in solving those use cases, then I guess an extension spec would be the way to go. However, IMHO specs don't always drive buy-in, buy-in drives specs.

Can compile a list of issues and bugs relevant to Web Speech API and Web Audio API working in conjunction. Those requests have been ongoing for several years now. In brief,

- https://stackoverflow.com/questions/18902789/can-web-speech-api-used-in-conjunction-with-web-audio-api

- https://lists.w3.org/Archives/Public/public-speech-api/2017Jun/0000.html

- https://github.com/WICG/speech-api/issues/10

- https://github.com/WebAudio/web-audio-api/issues/1764

- https://stackoverflow.com/a/48504311 

- https://github.com/WICG/speech-api/issues/56

- https://github.com/WICG/speech-api/issues/69

- https://github.com/guest271314/SpeechSynthesisSSMLParser

It depends on how thorough and lengthy you want the list to be to satisfy the as-yet undefined term "compelling". Notice the local direct text to `MediaStreamTrack` conversion implication of the last list item. 

`MediaStreamTrack` can certainly be useful in the domain of TTS/SST. 

-- 
GitHub Notification of comment by guest271314
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/pull/651#issuecomment-566301849 using your GitHub account
Received on Monday, 16 December 2019 23:45:55 UTC

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