- From: Ray Bellis <ray@bellis.me.uk>
- Date: Tue, 11 Dec 2012 08:05:19 +0000
- To: public-audio@w3.org
On 11/12/2012 01:27, Chris Rogers wrote: > I can see how an AudioParam could keep a record for .computedValue for > the last N "rendering quantums", so it could look back in time to the > .computedValue corresponding to the snapshot of .currentTime you're > suggesting. But we can't go back an arbitrary amount of time, since we > don't have infinite storage. This value is computed based on timeline > values and also audio-rate signals (from other AudioNodes) connected to > it. So we don't necessarily have all the information we need to compute > this value on-the-fly arbitrarily backwards in time. Just wondering - how does this (pre?) calculation of an AudioParam's values affect the various suggestions for how those values might be exposed to a ScriptProcessorNode ? (https://www.w3.org/Bugs/Public/show_bug.cgi?id=17388) Ray
Received on Tuesday, 11 December 2012 08:30:46 UTC