[Bug 20698] Need a way to determine AudioContext time of currently audible signal


Joe Berkovitz / NF <joe@noteflight.com> changed:

           What    |Removed                     |Added
            Summary|Need way to determine       |Need a way to determine
                   |"performance.now()" time of |AudioContext time of
                   |current audio output        |currently audible signal

--- Comment #18 from Joe Berkovitz / NF <joe@noteflight.com> ---
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.

You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 16 April 2013 15:39:11 UTC