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


--- Comment #8 from Ehsan Akhgari [:ehsan] <ehsan@mozilla.com> ---
(In reply to comment #7)
> Based on my knowledge of various audio platforms I don't know if it is
> likely that implementations can always succeed in getting the latency down
> to the point where it doesn't matter.
> I agree that in principle if it was always quite small, it wouldn't matter
> much, but I am concerned that this is not a realistic goal to sign up for.

Fair enough, but I think we should have examples on cases where this latency is
unavoidably above the human perception range and the implementation can do
nothing about it.  I believe that if implementation avoid using imprecise OS
clock facilities, there should not be a case where this can happen.

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

Received on Tuesday, 2 April 2013 20:05:08 UTC