W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

[Bug 17396] (numberOfChannels): AudioDestinationNode.numberOfChannels

From: <bugzilla@jessica.w3.org>
Date: Wed, 24 Oct 2012 14:32:12 +0000
To: public-audio@w3.org
Message-ID: <bug-17396-5429-goUILctylA@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17396

Marcus Geelnard (Opera) <mage@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mage@opera.com

--- Comment #5 from Marcus Geelnard (Opera) <mage@opera.com> ---
(In reply to comment #4)
> 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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 24 October 2012 14:32:22 UTC

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