W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2012

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

From: Audio Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Fri, 01 Jun 2012 19:37:29 +0000
Message-Id: <E1SaXf7-0003UM-2e@tibor.w3.org>
To: public-audio@w3.org
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.
Received on Friday, 1 June 2012 19:37:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 1 June 2012 19:37:35 GMT