On Thu, Jul 25, 2013 at 7:37 PM, Robert O'Callahan <robert@ocallahan.org>wrote: > Thanks for this feedback! > > Regarding this issue, see > http://lists.w3.org/Archives/Public/public-audio/2013AprJun/0432.html and > the surrounding thread. Web Audio's design encourages a "fire and forget" > approach of constantly creating new nodes and never explicitly removing > them, which is incompatible with APIs that expose graph structure. If the > TAG insists on having such APIs, then we'll have to redesign Web Audio > significantly (probably making it harder to use), which I don't think > anyone in this group really wants. > I agree. Also, I'd like to note that it's possible to write a Javascript library which intercepts the Web Audio API calls to record the information needed to reconstruct the graph on a different AudioContext to achieve the desired behavior described in this issue. -- Ehsan <http://ehsanakhgari.org/>
Received on Friday, 26 July 2013 12:58:37 UTC