W3C home > Mailing lists > Public > public-audio@w3.org > January to March 2015

Re: Is Web Audio a realtime API?

From: Raymond Toy <rtoy@google.com>
Date: Wed, 14 Jan 2015 10:52:32 -0800
Message-ID: <CAE3TgXGC9=j7w9=pNGcL+C+Z-7X-gTeQCY7pj1RqB4YP-dZ9cQ@mail.gmail.com>
To: Chris Lilley <chris@w3.org>
Cc: Oleg Beletski <o.beletski@samsung.com>, "public-audio@w3c.org" <public-audio@w3c.org>
On Wed, Jan 14, 2015 at 9:02 AM, Chris Lilley <chris@w3.org> wrote:

> Hello Oleg,
>
> Wednesday, January 14, 2015, 3:11:56 PM, you wrote:
>
> > Specification lists performance and latency considerations, but
> > does not explicitly state if API is realtime or not.
>
> That depends on your definition of realtime.
>
> On the one hand, it concerns audio which is generated "in realtime"
> rather than previously recorded audio which is merely played back.
>
> On the other hand, it will almost always be executed on a
> non-realtime, multitasking OS rather than a RTOS. And audio samples
> are processed in blocks rather than as individual samples, so
> sample-accurate sync is hard (128 samples at 44.1k is 2.9ms).
>

I believe the api does give you sample-accurate sync, even if the samples
are processed in blocks.


>
>
>
> --
> Best regards,
>  Chris Lilley, Technical Director, W3C Interaction Domain
>
>
>
Received on Wednesday, 14 January 2015 18:52:58 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 14 January 2015 18:52:59 UTC