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

Re: [web-audio-api] OfflineAudioContext and ScriptProcessorNodes (#69)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:40 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/69/24244290@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=22723#24) by Srikumar Subramanian (Kumar) on W3C Bugzilla. Wed, 24 Jul 2013 06:48:09 GMT

(In reply to [comment #24](#issuecomment-24244283))
> (In reply to [comment #23](#issuecomment-24244281))
> > Yes, you're right there.  One solution is to forbid graph manipulation in
> > that case.
> 
> That would be OK, but it will be quite a lot of work to specify and
> implement checks for every single API that must be blocked.

Synchronous graph manipulation is, I'd say, a *must have* in the offline case. If I want to mix down a 5 minute composition with  8 tracks with 1 voice in each track triggered every second (not too taxing a scenario for the realtime composer case), that would need 2400 nodes to be pre-created ... and this doesn't count effects nodes. Permitting the graph to be changed within a script node would provide a way to instantiate these voices just in time. 

If that isn't possible, it would help to add a separate synchronous event that can be used for this purpose, that would also be useful for tracking progress of an offline context.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/69#issuecomment-24244290
Received on Wednesday, 11 September 2013 14:34:28 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC