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

Re: About AudioPannerNode

From: Marcus Geelnard <mage@opera.com>
Date: Mon, 25 Jun 2012 09:45:44 +0200
To: "Chris Rogers" <crogers@google.com>
Cc: public-audio@w3.org
Message-ID: <op.wgf7ui1em77heq@mage-desktop>
Den 2012-06-21 09:32:49 skrev Marcus Geelnard <mage@opera.com>:

> How about dynamically altering the sample rate of all nodes prior to the  
> panner node instead, and apply re-sampling at the panner node input?  
> That would be more correct w.r.t. filter nodes, for instance. That would  
> also remove the need to implicitly track the source nodes from the  
> panner nodes, and should probably also work for  
> MediaElementAudioSourceNode (if you re-sample it according to the  
> altered sample rate), as well as JavaScriptAudioNode source nodes.
> It would on the other hand be tricky to handle processing-buffer  
> alignment, perhaps requiring the addition of a slight latency to allow  
> up-stream nodes to continue using 128-sample blocks. It would also  
> require all nodes to support dynamic sample rate changes (if that is not  
> already a requirement).

Obviously I hadn't thought this one through... You'd need some kind of  
pitch-altering re-sampling anyway. Not sure if the method could solve any  
problems, but it feels quite complex either way.


Marcus Geelnard
Core Graphics Developer
Opera Software ASA
Received on Monday, 25 June 2012 07:46:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:59 UTC