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:23:07 +1200
Message-ID: <CAOp6jLZWiQXaiAa7gCcgvLOJKL_MG+7u0_Oa6dz1NcFwZOzr3Q@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: 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 8:57 AM, Justin Uberti <juberti@google.com> wrote:

> I agree. While I like the notion of priority in the channels design, where
> call audio will cause other sounds to have their volume reduced, I would
> still like to be able to control the actual output device directly in the
> application, so that it can do things like play audio out of speakers but
> switch if a certain preferred headset is connected.

I'm having trouble thinking of a situation where that sort of thing is
better controlled by the application than by the UA.

I can certainly see the case for the UA remembering application-specific
settings --- and that works fine with the logical channels approach. I
cannot yet see the case for each application having its own UI for this.

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:23:33 UTC

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