W3C home > Mailing lists > Public > public-media-capture@w3.org > September 2018

Re: getDisplayMedia() and system audio

From: Henrik Boström <hbos@google.com>
Date: Thu, 6 Sep 2018 11:08:29 +0200
Message-ID: <CAEbRw2w3cKAJXo1W1ysAcrX_wFaxCoyjdqtf61UeFYX7ALh+VA@mail.gmail.com>
To: roman@telurix.com
Cc: Martin Thomson <martin.thomson@gmail.com>, Bernard Aboba <Bernard.Aboba@microsoft.com>, silviapfeiffer1@gmail.com, public-webrtc@w3.org, public-media-capture@w3.org
I listed some use cases and came up with a proposal, please take a look:
getDisplayMedia() with audio: excludeTabAudio constraint proposal
<https://docs.google.com/document/d/1pgN8Pe2zMaD0tytJVsKmnBT-7gM247YlzzWazm7OwSk/edit?usp=sharing>

On Thu, Sep 6, 2018 at 2:54 AM Roman Shpount <roman@telurix.com> wrote:

> On Wed, Sep 5, 2018 at 8:22 PM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
>> On Thu, Sep 6, 2018 at 10:11 AM Bernard Aboba
>>
>> There is probably some role for consent there, but I agree that this
>> should be as narrow as the selection.  To vary from that would require
>> some exceptional consent, in an area that is already a minefield.
>>
>
> There is also an implementation minefield since there is no one-to-one
> correlation between audio sources and windows. Audio is played by the
> process and its relationship to a specific window is not always obvious.
> Even if you limit audio capture to a specific process, it is not trivial to
> capture it. There are no standard APIs for this. Audio capture from a
> process on most of the operating systems requires some sort of hack, like
> dynamic library injection. The most reliable method is to install a special
> driver that creates a virtual output device which maps to a virtual input
> device. Then the application needs to be configured to play into the
> virtual output driver and virtual input driver can be used as WebRTC audio
> source. One example of such setup are Virtual Audio Cables (
> https://en.wikipedia.org/wiki/Virtual_Audio_Cable). This means that for
> people who needs this now, there is a work around already available.
> Implementing something nice with an interface, which is safe to obtain
> consent and be used in a browser, is probably not currently possible.
>
> Regards,
> _____________
> Roman Shpount
>
>
>
Received on Thursday, 6 September 2018 09:09:04 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 6 September 2018 09:09:04 UTC