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

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=20698#7) by Ehsan Akhgari [:ehsan] on W3C Bugzilla. Tue, 02 Apr 2013 20:05:02 GMT

(In reply to [comment #7](#issuecomment-24244102))
> 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.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/12#issuecomment-24244106