RE: ConvolverNode.buffer with extra channels?

+1

I think it should throw a NOT_SUPPORTED_ERR exception.

 

From: Raymond Toy [mailto:rtoy@google.com] 
Sent: Saturday, March 15, 2014 5:51 AM
To: public-audio@w3.org
Subject: Re: ConvolverNode.buffer with extra channels?

 

 

 

On Fri, Mar 14, 2014 at 1:12 PM, Raymond Toy <rtoy@google.com> wrote:

http://webaudio.github.io/webA-audio-api/#attributes-14 says the buffer should be a mono, stereo, or 4-channel AudioBuffer.

 

 

Here's the correct link:  http://webaudio.github.io/web-audio-api/#attributes-14

 

On a different note, that link brings me somewhere in the paragraph about the buffer attribute, not the heading 2.15.1. Don't know if that's an issue with the spec itself or the browser. (This happens in both Chrome and Firefox.)

 

What should happen if the AudioBuffer doesn't satisfy that? Seems to me we should throw a NOT_SUPPORTED_ERR exception.

 

Ray