- From: guest271314 via GitHub <sysbot+gh@w3.org>
- Date: Mon, 14 Sep 2020 14:38:05 +0000
- To: public-webrtc-logs@w3.org
> `audiooutput` is not intended for capturing. That language needs to be in the specification to avoid confusion. There are more than one individual that has interpreted that term literally when the only specified definition is > **audiooutput** | Represents an audio output device; for example a pair of headphones. without the accompanying explanation. > `audiooutput` is intended to identify devices that can output (as in play) audio. That is what have not ever understood about what `setSinkId()` is intended to do and does. Again, all of that language needs to be in the specification if the label is useful to some. At https://stackoverflow.com/a/45003549 and https://github.com/guest271314/SpeechSynthesisRecorder/issues/14 the term only sows confusion when users actually want to capture heaphones and speakers. Kindly tell those users that `"audiooutput"` does not mean capture of headphones or speakers at all. No one else has said that in any specification. > In this spec, they're useful if you want getUserMedia to prefer a microphone (type `audioinput`) associated with a certain output device by specifying the group ID of the `audiooutput` device using the `groupId` constrainable property. I still am having difficulty understanding exactly what `setSinkId()` does. What is meant by "associated with a certain output device"? The user does not need `"audiooutput"` at all to set `MediaStream` as `srcObject` of `HTMLMediaElement` or as `mediaStream` at `MediaStreamAudioSourceNode`. In this specification `"audiooutput" is useless. As far as I can tell Chromium is the only browser that uses that label. Which refers to the same device as `"audioinout"`. There is no difference at Chromium - unless you can demonstrate that difference in code. > I see no need to remove them from this spec. I do. To avoid confusion. There is not capture of audio output occurring. That requirement is still being requested and developed. If that needs to be kept around for whatever purpose individuals use it for, then all of the language used outside of the specification in these issues needs to be in the actual specification - and Audio Output Devices API - so that no user ever again has the interpretation that either of these specifications intends to actualy capture the audio output to headphones or speakers. And rename the bit `"audioreroute"` or `"microphone=to-headphones-or-speakers` or something like that, as the prupose actually has nothing to do with actual capture of heaphones or speakers, rather, routing captured microphone input to headphones. -- GitHub Notification of comment by guest271314 Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/720#issuecomment-692101323 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 September 2020 14:38:07 UTC