- From: Chris Rogers <crogers@google.com>
- Date: Fri, 3 Dec 2010 12:02:06 -0800
- To: Doug Schepers <schepers@w3.org>
- Cc: XG-Audio <public-xg-audio@w3.org>, Noah Mendelsohn <nrm@arcanedomain.com>
- Message-ID: <AANLkTimOGros0r7S-amOrVG8NGB0JWQhkfyR_AKqOoB1@mail.gmail.com>
Hi Doug, Thanks for your work in pushing this forward! Concerning Noah's comment about multi-channel audio input, my API proposal could easily be extended to cover audio input (as well as output). AudioContext has a "destination" attribute representing the audio output and may be multi-channel. Similarly, there could be a "source" attribute on the context representing the live audio input (two or more channels). The main reason I've left this out in my spec is because there are the security / device-access issues which need to be sorted out. It may be that the <device> specification is already addressing these issues, but I haven't had time to keep up with those developments. Cheers, Chris On Fri, Dec 3, 2010 at 11:47 AM, Doug Schepers <schepers@w3.org> wrote: > Hi, folks- > > We advised our Advisory Committee that we are starting work on the Audio WG > charter, as per W3C Process, and there has been definite interest. > > Here are some thoughts sent to me offlist that should be considered as part > of our use cases and requirements, which may dovetail with what Janina Sajka > from the accessibility community said in her recent email. > > -------- Original Message -------- > Subject: Re: Work Started on Audio Working Group Charter (Advance Notice) > Date: Thu, 02 Dec 2010 16:33:26 -0500 > From: Noah Mendelsohn <nrm@arcanedomain.com> > To: Doug Schepers <schepers@w3.org> > > On 12/2/2010 4:13 PM, Doug Schepers wrote: > >> some sort of <device> element for microphones or audio-in jacks >> > > Not sure whether I mentioned this to you or to someone else at TPAC, but > I'd still like to see this generalized to cover more modern audio input > devices, which support > 2 channels. I think a great goal would be to > provide sufficient flexibility that one could do a simple DAW, fed by at > least commodity grade USB/Firewire interfaces. Otherwise, the Web remains > at a huge disadvantage to native. > > I don't normally post personal opinions to ac-forum, as I feel it's mainly > for the AC, but feel free to forward this comment to anyone who might be > interested, whether inside W3C or not. Please do cc: me. Thanks! > > Noah > > >
Received on Friday, 3 December 2010 20:02:39 UTC