This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#ConvolverNode Currently, the number of output channels of the ConvolverNode is controlled by the number of output channels of the AudioContext (although it's not very clear in the spec). I think it would be a better idea to be able to control the number of output channels of the ConvolverNode upon construction rather than relying on the AudioDestinationNode. It would give you more freedom to do custom processing, and makes the actual usage of the impulse response channels much more user controllable. The last point is important, since the number of output channels controls which matrixing operation will be used.
Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.