This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
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.
No objection to resolution since June, Closing.