17357 2012-06-05 11:47:05 +0000 (ConvolverNodeChannels): ConvolverNode channel mapping 2014-10-28 17:16:47 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified PC All CLOSED WONTFIX P2 normal TBD 1 philipj dave.null crogers mage public-audio dave.null oldest_to_newest 68668 0 philipj 2012-06-05 11:47:05 +0000 Audio-ISSUE-70 (ConvolverNodeChannels): ConvolverNode channel mapping [Web Audio API] http://www.w3.org/2011/audio/track/issues/70 Raised by: Philip Jägenstedt On product: Web Audio API The buffer attribute is defined as "A mono or multi-channel audio buffer containing the impulse response used by the convolver." However, it is not defined at all how the channels in the impulse response should be used, even in the case where it matches the number of channels in the input. Possibly, a mono impulse response should be applied to all channels, but beyond that it's hard to guess. 69035 1 crogers 2012-06-14 00:53:57 +0000 This information should now be present: https://dvcs.w3.org/hg/audio/rev/4df179094971 69195 2 mage 2012-06-18 10:12:45 +0000 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). 113877 3 olivier.thereaux 2014-10-28 17:13:54 +0000 Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues 114022 4 olivier.thereaux 2014-10-28 17:16:47 +0000 Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.