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

Re: [web-audio-api] Need a way to determine AudioContext time of currently audible signal (#12)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:30 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/12/24244161@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=20698#17) by Joe Berkovitz / NF on W3C Bugzilla. Tue, 16 Apr 2013 15:39:09 GMT

I've retitled the bug to try to more effectively communicate the nature of the issue. Yes, it is about average latency: the difference between AudioContext.currentTime and the original as-scheduled playback time for the signal that is currently being emitted from the audio hardware.  Please see the very first comment in the bug for a description of the use case that I am trying to address.

If someone else wants to file a bug about how to correlate AudioContext time with other timebases in the browser I'm fine with that, but that isn't the problem that I'm concerned about.

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:30:03 UTC

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