W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

Re: [web-audio-api] (numberOfChannels): AudioDestinationNode.numberOfChannels (#112)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:37 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/112/24244269@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17396#1) by Olivier Thereaux on W3C Bugzilla. Thu, 07 Jun 2012 14:20:33 GMT

>From the Editor: Change Set: https://dvcs.w3.org/hg/audio/rev/90e55985e260

Feedback given in http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0430.html
As Marcus pointed out in <http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0355.html>, maxNumberOfChannels doesn't seem to really work and an array of values would make more sense.

We don't think that setting numberOfChannels to a configuration that isn't supported should throw an exception, since that's likely to result in unhandled exceptions when authors have only tested with one speaker configuration. For example, it's to be expected that authors will set numberOfChannels to 2 without checking maxNumberOfChannels, which will fail on smartphones with a single speaker. Instead, we think that the requested number of channels should be used and mixing should be applied if the hardware doesn't support it.

Note also the typo in "If this value is 0, then this indicates that <code>maxNumberOfChannels</code>" which should be numberOfChannels.

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:30:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC