W3C home > Mailing lists > Public > public-media-capture@w3.org > May 2015

Re: Filtering of enumerateDevices() results

From: Chris Wilson <cwilso@google.com>
Date: Wed, 20 May 2015 08:57:19 -0700
Message-ID: <CAJK2wqVcmnqkzwd1q8q0BAHewVeEYWMTwWj9xhzaHC8KuGGdMg@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: Joe Berkovitz <joe@noteflight.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>, Stefan HÃ¥kansson <stefan.lk.hakansson@ericsson.com>, Audio Working Group <public-audio@w3.org>
On Wed, May 20, 2015 at 1:00 AM, Harald Alvestrand <harald@alvestrand.no>

> Den 19. mai 2015 16:29, skrev Joe Berkovitz:
> > 1. For audio devices, channel count and a binaural (essentially,
> > speaker-vs-headphone) flag are important attributes.
> Query - are these distinct attributes or points on the same continuum?
> ie will a monaural device always have channel count 1? Or is the
> "binaural" flag specifically for the headphone case, with "each ear of
> the listener hears one and only one channel"?

The latter - the flag is really just a way to determine, ideally, if doing
HRTF effects is a good idea.

> > 2. How would the WG feel about including more "filtered" information in
> > the MediaDeviceInfos returned by enumerateDevices(), other than the
> > device label -- information that the application can use to restrict or
> > augment the list of devices displayed to a user (since constraints are
> > not accepted by enumerateDevices())? Ideally channel count, binaural,
> > sample rate and other attributes such as width and height could be
> > exposed here.
> Query - do you think of these things as singular attributes or as a
> range of possible values? IE some devices are capable of being
> configured into multiple sample rates - what info would you want?

Range of possible values would be more flexible, definitely, and quite

Received on Wednesday, 20 May 2015 15:57:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:33 UTC