W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

[Bug 17424] New: Setting sample rates for individual JavaScriptProcessingNodes

From: <bugzilla@jessica.w3.org>
Date: Tue, 05 Jun 2012 15:54:02 +0000
To: public-audio@w3.org
Message-ID: <bug-17424-5429@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17424

           Summary: Setting sample rates for individual
                    JavaScriptProcessingNodes
           Product: AudioWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Web Audio API
        AssignedTo: dave.null@w3.org
        ReportedBy: ot@zoy.org
         QAContact: public-audio@w3.org


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.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 5 June 2012 15:56:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 5 June 2012 15:56:10 GMT