- From: Audio Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Wed, 21 Mar 2012 09:45:29 +0000
- To: public-audio@w3.org
Audio-ISSUE-6 (audioparam): AudioParam constructor [Web Audio API]
http://www.w3.org/2011/audio/track/issues/6
Raised by: Jussi Kalliokoski
On product: Web Audio API
Raised by Jussi, going back to a discussion back in spring 2011:
[1] http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0374.html
[2] http://lists.w3.org/Archives/Public/public-audio/2011AprJun/0085.html
[3] http://lists.w3.org/Archives/Public/public-audio/2011AprJun/0086.html
[4] http://lists.w3.org/Archives/Public/public-audio/2011AprJun/0087.html
[5] http://lists.w3.org/Archives/Public/public-audio/2011AprJun/0089.html
[6] http://lists.w3.org/Archives/Public/public-audio/2011AprJun/0101.html
[7] http://lists.w3.org/Archives/Public/public-audio/2011AprJun/0103.html
The discussion focused on the need for an AudioParam constructor in the context of a JavaScriptAudioNode.
Jussi then suggested
partial interface JavaScriptAudioNode {
AudioParam createAudioParam(name, defaultValue, minValue, maxValue,
units);
}
partial interface AudioProcessingEvent {
Float32Array getParamValues(name);
}
With which CRogers agreed, but suggested to pass the AudioParam instead of name to getParamValues().
Thread: http://lists.w3.org/Archives/Public/public-audio/2012JanMar/thread.html#msg412
http://lists.w3.org/Archives/Public/public-audio/2012JanMar/0437.html
Received on Wednesday, 21 March 2012 09:45:34 UTC