- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 16 Dec 2019 23:22:55 +0000
- To: public-webrtc-logs@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 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. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-main/pull/651#issuecomment-566294379 using your GitHub account
Received on Monday, 16 December 2019 23:22:57 UTC