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

[Bug 20698] Need way to determine "performance.now()" time of current audio output

From: <bugzilla@jessica.w3.org>
Date: Tue, 02 Apr 2013 16:10:16 +0000
To: public-audio@w3.org
Message-ID: <bug-20698-5429-XEQyHvo48M@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20698

--- Comment #3 from Joe Berkovitz / NF <joe@noteflight.com> ---
This bug is intended to cover both the MIDI-synchronization cases that you
proposed and also the original case I raised, which involved the placement of a
visual cursor that is synchronized with audio that's being heard at the same
time.

In the original visual case, the main thread needs to be able to determine the
original "audio scheduling" time (in the context time frame used by start(),
setValueAtTime(), etc.) for the audio signal presently emerging from the
speaker. AudioContext.currentTime does not supply this time, as I explained in
my original bug description.

I am not interested in the average latency or processing block size and agree
that would be a different bug.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 2 April 2013 16:10:21 UTC

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