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

Re: Can users determine if audio has glitched?

From: Chris Rogers <crogers@google.com>
Date: Mon, 10 Jun 2013 15:46:26 -0700
Message-ID: <CA+EzO0=tR74_amckWhEYK56-fY-=aZ+dA4TMdNgzLJ-b20Sv7g@mail.gmail.com>
To: Russell McClellan <russell@motu.com>
Cc: "public-audio@w3.org WG" <public-audio@w3.org>
On Mon, Jun 10, 2013 at 3:14 PM, Russell McClellan <russell@motu.com> wrote:

> Is there a way under the current API for users to determine if audio has
> glitched (in particular, because their ScriptProcessorNode was too slow)?
>
> This would be very useful, because then programs could increase buffer
> size or decrease audio quality based on whether or not the script processor
> was completing on time.
>
> The only way I can think to do this currently would be to inspect the
> playbackTime attribute on the AudioProcessingEvent and make sure that's
> it's increasing by exactly one buffer each call.  This seems a bit fragile
> to me, as perhaps there's other reasons why the web audio graph might
> decide to skip a buffer of script processing.
>

There is no way currently, but there could be a "missed deadline"
EventListener .onmissed (or something like that)


>
> Thanks,
> -Russell
>
Received on Monday, 10 June 2013 22:46:57 UTC

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