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:39 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/112/24244282@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17396#4) by Marcus Geelnard (Opera) on W3C Bugzilla. Wed, 24 Oct 2012 14:32:12 GMT

(In reply to [comment #4](#issuecomment-24244277))
> 1. using maxNumberOfChannel or using an array of layout. I think current
> spec using maxNumberOfChannel is reasonable.

As long as the specification is clearer about what should happen when setting numberOfChannels to an unsupported number of channels. For instance: if the supported channel counts are 2 and 6, then maxNumberOfChannels should return 6, but what must happen if you set numberOfChannels to 1, 3, 4 or 5?

And I still believe that there must be a better way to signal "read only" than to have '0' as a magic constant. In fact, "read only" only means that there is a single allowed configuration (e.g. 2 for a stereo only context).

> 2. Exception handling. (automatic down/up mixing or throw exception?). I
> prefer to automatic mixing.

Dito.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/112#issuecomment-24244282
Received on Wednesday, 11 September 2013 14:30:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC