On Fri, Aug 16, 2013 at 11:22 AM, Chris Wilson <cwilso@google.com> wrote: > In particular, the digital audio workstation type case - or any music app > that wants access to multiple hardware interfaces, like a DJ app that has a > cue output as well as a mains output - typically has to leave this up to > the user, since it's hard to semantically define the "roles" of different > devices (sometimes there's no semantic difference - I just have two > four-track interfaces, and I want to have eight tracks of output, etc.) > One way to address this kind of use-case might be to allow applications to define their own logical output devices. Another thing that might help is to add APIs to grab the current output configuration into an opaque data object which can be persistently stored locally (e.g. via IndexedDB), and which can be used to restore the current configuration, but which can't be sent anywhere. Given that, your hypothetical DJ app would be able to define logical "cue" and "mains" outputs, the UA would hook those up to output devices and allow the user to control that mapping, and the app could save and restore those settings and associate them with particular application-specific contexts. Would that help? 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 Friday, 16 August 2013 02:25:17 UTC