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

Re: Help needed with a sync-problem

From: Chris Wilson <cwilso@google.com>
Date: Fri, 3 Aug 2012 11:50:08 -0700
Message-ID: <CAJK2wqXjCD9BBZgmYAqr7NdU8XNWp=+E_JBH_rQbK3a1oZ0=pg@mail.gmail.com>
To: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Cc: Peter van der Noord <peterdunord@gmail.com>, Adam Goode <agoode@google.com>, public-audio@w3.org
On Fri, Aug 3, 2012 at 11:20 AM, Jussi Kalliokoski <
jussi.kalliokoski@gmail.com> wrote:

> On Fri, Aug 3, 2012 at 9:14 PM, Chris Wilson <cwilso@google.com> wrote:
>
>> On Fri, Aug 3, 2012 at 10:37 AM, Jussi Kalliokoski <
>> jussi.kalliokoski@gmail.com> wrote:
>>
>>> On Fri, Aug 3, 2012 at 8:21 PM, Chris Wilson <cwilso@google.com> wrote:
>>>
>>>> How would you empower the JS node/DSP API to fix this?
>>>
>>>
>>> By making it possible to do fast processing without using the native
>>> nodes.
>>>
>>
>> Well I get that - _HOW_ was my question, not WHAT.
>>
>
> By improving the DSP API and getting it out there soon. On the Web Audio
> API side, for example these: [1] [2] [3].
>
> [1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=17415
> [2] https://www.w3.org/Bugs/Public/show_bug.cgi?id=17388
> [3] https://www.w3.org/Bugs/Public/show_bug.cgi?id=17533
>

None of those bugs are a way to fix the problem Peter pointed out - that
the buffers in JSNode are going to cause latency.  (I do consider all three
of those to be valid issues - in fact, I think the first time I met Chris
FTF at TPAC 2011 I asked about adding worker thread based JS nodes.
 Although I would point out thread priority is going to be an issue.)
Received on Friday, 3 August 2012 18:50:40 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 3 August 2012 18:50:41 GMT