W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2013

Re: OfflineAudioContext specification gaps

From: Chris Rogers <crogers@google.com>
Date: Fri, 3 May 2013 15:59:33 -0700
Message-ID: <CA+EzO0=3fpGtF7gwhymKz4S99EKMR=6ZiuSJ3k0wUsswtLBu8Q@mail.gmail.com>
To: "Robert O'Callahan" <robert@ocallahan.org>
Cc: Joseph Berkovitz <joe@noteflight.com>, "public-audio@w3.org WG" <public-audio@w3.org>
On Fri, May 3, 2013 at 3:51 PM, Robert O'Callahan <robert@ocallahan.org>wrote:

> It might work well to give startRendering() an optional duration parameter
> in samples. Then the OfflineAudioContext would render exactly that many
> samples (which must be a multiple of the block size, of course) and stop
> (firing some kind of notification event). Then the application could make
> changes to the graph and call startRendering() again to render another
> batch of samples.
>

Yes, I was thinking something like that too.  Do you think it would be
necessary to call startRendering() again each time, or could it be implied
that after returning from the event handler that processing would continue,
repeatedly calling the notification, then finally calling the oncomplete
handler?


>
> Rob
> --
> qqIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q
> qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq
> qsqiqnqnqeqrqsq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq
> qiqfq qyqoquq qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq
> qtqoq qyqoquq,q qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q
> qEqvqeqnq qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
>
Received on Friday, 3 May 2013 23:00:00 UTC

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