W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] Setting sample rates for individual JavaScriptProcessingNodes (#232)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:12 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/232@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17424](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17424) Tue, 05 Jun 2012 15:54:02 GMT
> Reported by olivier Thereaux
> Assigned to 

Closed per http://www.w3.org/2011/audio/track/issues/4

Raised by Jussi as: “Ideally, the end developer should be able to create custom processing nodes with specific sample rates within a single AudioContext. This is very useful, since high quality resampling in JavaScript is relatively expensive, and a required feature for anything that deals with external media sources, for example JS codecs.The sample rate should also be possible to be changed on the fly to allow for features like changing the playback rate of a codec (required if you'd want to use JS codecs to extend <audio> for example).”

Resolved on 2 Apr 2012 teleconference: 
http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0010.html

Resolution: add a constructor parameter for audio context to specify sample rate - make sure to specify that default is best unless needed.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/232
Received on Wednesday, 11 September 2013 14:29:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC