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

[web-audio-api] (DOMHighResTimeStamp everywhere): Use DOMHighResTimeStamp for all times? (#227)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:29:10 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/227@github.com>
> Originally reported on W3C Bugzilla [ISSUE-17414](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17414) Tue, 05 Jun 2012 12:42:25 GMT
> Reported by Michael[tm] Smith
> Assigned to 

Audio-ISSUE-106 (DOMHighResTimeStamp everywhere): Use DOMHighResTimeStamp for all times? [Web Audio API]

http://www.w3.org/2011/audio/track/issues/106

Raised by: Adam Goode
On product: Web Audio API

AudioContext.currentTime uses a float type specified in seconds since the creation of the AudioContext.

Is it necessary for each AudioContext to have a unique clock? If not, then it may make sense to use a DOMHighResTimeStamp which is now used by requestAnimationFrame for its timestamps:

http://updates.html5rocks.com/2012/05/requestAnimationFrame-API-now-with-sub-millisecond-precision

Having one global high-resolution clock for audio and animation seems to make a lot of sense.


The MIDI draft recently switched to using DOMHighResTimeStamp as well.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/227
Received on Wednesday, 11 September 2013 14:29:38 UTC

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