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. On Thu, Aug 15, 2013 at 11:06 AM, Chris Wilson <cwilso@google.com> wrote: > Although I recognize the value of that proposal for that proposal, I'm not > convinced logical audio channels is a good solution for the scenario of "I > have two different 8-channel audio devices that I want to provide access > to" - e.g. the digital audio workstation case. Perhaps that's only > applicable in the case of Web Audio - and there, I'd expect (in addition to > this API) that there would be an AudioContext constructor of some form that > takes some kind of identifier (maybe a sinkId, I haven't thought that > through). I'd like the solutions to these problem spaces to at least be > designed cooperatively. > > > On Wed, Aug 14, 2013 at 9:41 PM, Robert O'Callahan <robert@ocallahan.org>wrote: > >> This seems closely related to various proposals (and implementations) for >> "audio output channels". See the thread starting at >> http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Mar/0174.html >> . >> >> Basically, those proposals approach the problem by defining a standard >> set of logical audio output channels (which we could think of as logical >> output devices) and leaving the mapping from those channels to actual >> output devices to the UA. >> >> Rob >> -- >> 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 20:58:47 UTC