W3C home > Mailing lists > Public > public-media-capture@w3.org > August 2013

Re: Proposal for output device selection

From: Robert O'Callahan <robert@ocallahan.org>
Date: Fri, 16 Aug 2013 10:51:37 +1200
Message-ID: <CAOp6jLY-gSQgNBk3onQRL1HS=PLOpGsUske4ABLZUT10+TFz1A@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Justin Uberti <juberti@google.com>, Chris Wilson <cwilso@google.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>, Harald Alvestrand <hta@google.com>, Victoria Kirst <vrk@google.com>, Tommy Widenflycht (ᛏᚮᛘᛘᚤ) <tommyw@google.com>, Tommi Gunnarsson <tommi@google.com>
On Fri, Aug 16, 2013 at 10:44 AM, Martin Thomson

> You obviously haven't used Chrome WebRTC with an audio setup like what
> I have here: two sets of headphones (only one with a mic), speakers on
> the laptop, speakers on a large monitor, and an occasional USB
> speakerphone-type device.  Under Windows, you can specify separate
> devices for "normal" use and "communications" use, which helps a
> little, but still causes some strange audio output behaviour.
> Generic controls don't work for all application usages, despite the
> best intentions of the generic implementation.  That's why Skype
> manages its own preferences.  Having some sort of control over this,
> even if it is just to ensure that choices are sticky over time for the
> same application, makes a lot of sense.

It's easy for the UA to make choices stick over time for the same
application. I just said that.

Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w  *
Received on Thursday, 15 August 2013 22:52:04 UTC

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