- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Oct 2020 23:52:19 +0000
- To: public-webrtc-logs@w3.org
The rationale for closing this issue is flawed based on the simple fact that "audiooutput" actually does occur at media capture audio output either, thus this issue https://github.com/w3c/mediacapture-output/issues/111. These specifications are using the term "audiooutput" as if audio output to speakers can be captured, which is not the case by default language in either specification. However, users do want actual audio output capture to headphones and speakers, thus if that is ever specified, clearly the "audiooutput" that is implemented now, that is, re-routing microphone input to speakers, must take precedence over the as-applied usage currently, which has nothing to do with actually capturing output to headphones or speakers. Thus, for disambiguity, this issue and the one of the same subatnce in audio output devices, makes it directly clear that the term "audiooutput" needs to be replaced with a term that describes what is actually specified and expected to occur - re-routing of microphone input to speakers - not capture of speakers. Am not sure why this is proving difficult to convey or comprehend at the specification level? -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/720#issuecomment-704612426 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 October 2020 23:52:21 UTC