Re: Call for Consensus: retire current ScriptProcessorNode design & AudioWorker proposal from Srikumar K. S. on 2014-08-13 (public-audio@w3.org from July to September 2014)

From: Srikumar K. S. <srikumarks@gmail.com>
Date: Wed, 13 Aug 2014 08:29:07 +0530
To: robert@ocallahan.org
Cc: adelespinasse@gmail.com, Chris Wilson <cwilso@google.com>, Joseph Berkovitz <joe@noteflight.com>, Raymond Toy <rtoy@google.com>, Olivier Thereaux <olivier.thereaux@bbc.co.uk>, Audio WG <public-audio@w3.org>
Message-Id: <E14F2194-4ADE-4A4E-96D4-A87CD48D2B35@gmail.com>

> On 13 Aug 2014, at 8:09 am, Robert O'Callahan <robert@ocallahan.org> wrote:
> 
> Another option that we've talked about before is having an API for OfflineAudioContext that lets you tell it to produce N samples (asynchronously) and then pause, firing a notification callback when it's paused. I think that's a pretty good solution for many use-cases, including dynamic graph reconfiguration.

Agreed.  That would solve the problem of having to create all nodes involved throughout an offline render at one shot.

Attachments

application/pkcs7-signature attachment: smime.p7s

Received on Wednesday, 13 August 2014 02:59:42 UTC