- From: Olivier Thereaux <notifications@github.com>
- Date: Wed, 11 Sep 2013 07:29:50 -0700
- To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Received on Wednesday, 11 September 2013 14:30:30 UTC
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17357#1) by Marcus Geelnard (Opera) on W3C Bugzilla. Mon, 18 Jun 2012 10:12:45 GMT The specification does not say anything about what must happen for other channel configurations than the ones listed. Also, the wording "common cases for stereo playback where N and M are 1 or 2 and K is 1, 2, or 4" is confusing. First of all the expression "common cases for stereo" indicates that there may be other (less common) cases, but in fact the API does not support them. Secondly, taking all permutations of "N and M are 1 or 2 and K is 1, 2, or 4" gives 12 possible combinations (not just the 5 that are required): N M K 1 1 1 1 1 2 1 1 4 1 2 1 1 2 2 1 2 4 2 1 1 2 1 2 2 1 4 2 2 1 2 2 2 2 2 4 Also, what about cases when AudioDestinationNode has numberOfChannels other than 1 or 2? Furthermore, it seems odd to let the number of output channels of the AudioNode depend on the number of output channels in the playback system (I take it that means ctx.destination.numberOfChannels). --- Reply to this email directly or view it on GitHub: https://github.com/WebAudio/web-audio-api/issues/133#issuecomment-24244395
Received on Wednesday, 11 September 2013 14:30:30 UTC