(DOMHighResTimeStamp everywhere): Use DOMHighResTimeStamp for all times?

[olivierthereaux]

Originally reported on W3C Bugzilla ISSUE-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.

[olivierthereaux]

Original comment by Chris Rogers on W3C Bugzilla. Sat, 09 Jun 2012 00:01:34 GMT

Each AudioContext will have its own clock which normally is based on a specific audio hardware "crystal" and not the system clock. Thus it cannot be in the same time-coordinate system as the system clock.

[olivierthereaux]

Original comment by Olivier Thereaux on W3C Bugzilla. Mon, 10 Sep 2012 10:10:11 GMT

No objection to resolution since June, Closing.