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

Re: JavaScriptNode bufferSize

From: olivier Thereaux <olivier.thereaux@bbc.co.uk>
Date: Tue, 8 May 2012 10:57:06 +0100
Cc: <public-audio@w3.org>
Message-Id: <481E87E6-68EA-45A2-A528-3FDC6AC18B29@bbc.co.uk>
To: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Hi Jussi,

Can you make sure we have the issue documented in our tracker?

Our agenda for this week's call (tomorrow) is not set yet, but it seems like this issues, as well as the one Matt raised last week, could be a good basis for discussion on JavaScriptNode buffer size and resulting delay.


On 7 May 2012, at 13:06, Jussi Kalliokoski wrote:

> Hello group!
> We discussed with Chris (off-list) the recent change from numberOfOutputs to numberOfChannels in the createJavaScriptNode(), because I noticed my sink.js was broken in the latest Chrome Canary.
> I suggested that the first parameter (bufferSize) be optional as well, reverting to default when passed undefined. In an advanced implementation, this default could be adjusted to a value that the implementation deems a good tradeoff between safety (avoiding underruns) and latency on that system and setup. I believe Chris thinks this is a good idea, so he suggested I bring this to discussion in the group so we can change the spec if we agree on it.
> Thoughts?
> Cheers,
> Jussi

Received on Tuesday, 8 May 2012 09:57:29 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:49:59 UTC