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

Re: OfflineAudioContext and ScriptProcessorNodes

From: Ehsan Akhgari <ehsan.akhgari@gmail.com>
Date: Wed, 17 Jul 2013 17:04:29 -0400
Message-ID: <CANTur_7qy3adn80_st8qsEAaxvRh93Zn8d9pxZGHfyfNeW+PwQ@mail.gmail.com>
To: Chris Rogers <crogers@google.com>
Cc: Srikumar Karaikudi Subramanian <srikumarks@gmail.com>, WG WG <public-audio@w3.org>
Can you please edit the spec accordingly?  The Gecko implementation doesn't
do this either right now... :/

--
Ehsan
<http://ehsanakhgari.org/>


On Wed, Jul 17, 2013 at 4:07 PM, Chris Rogers <crogers@google.com> wrote:

>
>
>
> On Wed, Jul 17, 2013 at 11:45 AM, Srikumar Karaikudi Subramanian <
> srikumarks@gmail.com> wrote:
>
>> Hi folks,
>>
>> Q: Can script processor nodes be expected to run
>> synchronously during offline rendering?
>>
>> By that I mean will native components wait for
>> a script node to complete its task before proceeding
>> to the next block of sample frames? Though it would
>> be ridiculous if they are not, the spec isn't clear
>> on this.
>>
>> When using the realtime context, the audio thread
>> is not expected to wait for compute intensive
>> script nodes and consequently the script nodes
>> operate with a delay. This delay is unnecessary
>> when rendering using the offline context and it
>> would be ok for the rendering thread to wait for
>> the JS code before continuing.
>>
>> Ensuring this has another benefit - that of providing
>> a mechanism by which we can use a script node as a
>> periodic callback timer to instantiate native nodes
>> just in time when rendering long compositions.
>>
>
> Yes, this is how it should work.  Currently, this is a limitation in the
> WebKit and Blink implementations.
>
> Chris
>
>
>>
>> Best,
>> -Kumar
>>
>>
>>
>>
>
Received on Wednesday, 17 July 2013 21:05:37 UTC

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