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

[Bug 22723] OfflineAudioContext and ScriptProcessorNodes

From: <bugzilla@jessica.w3.org>
Date: Wed, 24 Jul 2013 06:48:09 +0000
To: public-audio@w3.org
Message-ID: <bug-22723-5429-EMuKab23xs@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22723

--- Comment #25 from Srikumar Subramanian (Kumar) <srikumarks@gmail.com> ---
(In reply to comment #24)
> (In reply to comment #23)
> > 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.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 24 July 2013 06:48:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:10 UTC