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

Re: [mediacapture-main] Clarify getUserMedia({audio:{deviceId:{exact:<audiooutput_device>}}}) in this specification mandates capability to capture of audio output device - not exclusively microphone input device (#650)

From: guest271314 via GitHub <sysbot+gh@w3.org>
Date: Mon, 09 Dec 2019 15:35:11 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-563294989-1575905710-sysbot+gh@w3.org>
`getDisplayMedia()` does not capture audio at all at Chromium. 

`setSinkId()` captures only microphone, not audio output even where the audio output device `deviceId` is selected.

Do not care if `getDisplayMedia()` or `getUserMedia()` needs to be used to capture audio output. If neither method is intended to capture `"audioouput"` whatsoever that needs to be made clear in the specifications. If `getDisplayMedia()` in fact is capable of capturing audio output, e.g., to "headphones", as Media Capture and Streams specification currently implies by language 

> `audiooutput` | Represents an audio output device; for example a pair of headphones.

though that language is actually intended to apply to `getDisplayMedia()`, a canonical example of capturing audio output only - not audio input from a microphone - needs to be included in the specification.

The use case is very simple: capture audio output of `speechSythesis.speak()` which outputs audio directly from the system (https://github.com/guest271314/SpeechSynthesisRecorder; https://github.com/WICG/speech-api/issues/69).

Or, make it unequivocally clear that neither this parent specification nor any derivative specification is intended to capture audio output, so that alternative, non-standardized approaches, can be implemented.

GitHub Notification of comment by guest271314
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/650#issuecomment-563294989 using your GitHub account
Received on Monday, 9 December 2019 15:35:12 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:49 UTC