- From: Chris Rogers <crogers@google.com>
- Date: Wed, 17 Apr 2013 22:41:29 -0700
- To: "Robert O'Callahan" <robert@ocallahan.org>
- Cc: "public-audio@w3.org" <public-audio@w3.org>
- Message-ID: <CA+EzO0=a7u6wW4sARN+b31vUoZ1gyKptLSsEHu4RJ7GHZRmQkQ@mail.gmail.com>
On Wed, Apr 17, 2013 at 8:02 PM, Robert O'Callahan <robert@ocallahan.org>wrote: > We've discussed before how, if the specified buffer size matters in terms > of avoiding underruns etc, it's likely that most Web authors will not be > able to choose a buffer size that's appropriate for the Web Audio > implementation and underlying hardware. > > So, I think we should make the bufferSize parameter optional. When it's > not given, the UA will choose a suitable buffer size, which will be > constant for the lifetime of that ScriptprocessorNode. We would encourage > authors to not specify a fixed buffer size. > > We'll do this in Firefox if there are no objections. > That seems possible, except then the number of input and output channels will take their default values of 2. If the developer wants to choose different channel values but still have the UA choose the buffer size what would we specify for the buffer size, maybe 0? I think it's best that if the UA chooses the buffer size, then the value should still be a power of 2 and be the same every time the event handler is called. It's easier for developers that way. > > Rob > -- > q“qIqfq 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 Thursday, 18 April 2013 05:41:57 UTC