- From: Olivier Thereaux <notifications@github.com>
- Date: Wed, 11 Sep 2013 07:28:33 -0700
- To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
- Message-ID: <WebAudio/web-audio-api/issues/134@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17388](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17388) Tue, 05 Jun 2012 12:09:11 GMT > Reported by Michael[tm] Smith > Assigned to 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 --- Reply to this email directly or view it on GitHub: https://github.com/WebAudio/web-audio-api/issues/134
Received on Wednesday, 11 September 2013 14:40:23 UTC