W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2015

Fwd: [mediacapture-main] Allow device capabilities to be discoverable via enumerateDevices (#211)

From: Joe Berkovitz <joe@noteflight.com>
Date: Thu, 6 Aug 2015 11:58:18 -0500
Message-ID: <CA+ojG-ZEMjyTdAkSyVVnK9A+uuY2QcMD2tjcMvfCOqNgYm7_7w@mail.gmail.com>
To: Audio Working Group <public-audio@w3.org>
FYI -- output device characterization is not looking so good for inclusion
in the final Media Capture spec, though input devices look likely to be
covered by my earlier proposal, with some modification. This may have to
wait for the Audio Output API to take shape, unless others have better
ideas than I on how to proceed.

Please see the github PR for more details:


---------- Forwarded message ----------
From: jan-ivar <notifications@github.com>
Date: Thu, Aug 6, 2015 at 10:18 AM
Subject: Re: [mediacapture-main] Allow device capabilities to be
discoverable via enumerateDevices (#211)
To: w3c/mediacapture-main <mediacapture-main@noreply.github.com>
Cc: Joe Berkovitz <joe@noteflight.com>

@burnburn <https://github.com/burnburn> thanks for explaining the reason
for the exception.

Having an Audio Output spec add this makes sense to me FWIW. It might be
worth pondering whether such a spec would be likely to extend (with the
partial webidl keyword) either MediaTrackCapabilities or MediaDeviceInfo.
If the latter, we may want to rename info.capabilities to
info.inputCapabilities now to anticipate this (assuming we're still going
ahead). *

*) Because (MediaTrackCapabilities or OutputCapabilities) capabilities wont
work, as two dictionaries are not distinguishable
<https://heycam.github.io/webidl/#dfn-distinguishable> from each other in
webidl today.

Reply to this email directly or view it on GitHub
Received on Thursday, 6 August 2015 16:58:50 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 6 August 2015 16:58:51 UTC