ISSUE-106: (Bugzilla 17414) Use DOMHighResTimeStamp for all times?
DOMHighResTimeStamp everywhere
(Bugzilla 17414) Use DOMHighResTimeStamp for all times?
- State:
- CLOSED
- Product:
- Web Audio API
- Raised by:
- Adam Goode
- Opened on:
- 2012-06-01
- Description:
- 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. - Related Actions Items:
- No related actions
- Related emails:
- [web-audio-api] (DOMHighResTimeStamp everywhere): Use DOMHighResTimeStamp for all times? (#227) (from notifications@github.com on 2013-09-11)
- Re: Audio-ISSUE-105 (MIDI timestamp resolution): timestamps in MIDI should use High Resolution Time [MIDI API] (from agoode@google.com on 2012-06-01)
- Audio-ISSUE-106 (DOMHighResTimeStamp everywhere): Use DOMHighResTimeStamp for all times? [Web Audio API] (from sysbot+tracker@w3.org on 2012-06-01)
Related notes:
The AudioContext clock is driven by the audio hardware which is almost never the same clock as the rest of the system which DOMHighResTimeStamp uses. They run on different "crystals" and will drift away from each other.
This is why it's very important to make this distinction.
[MikeSmith]: http://www.w3.org/2011/audio/track/issues/106
5 Jun 2012, 12:59:22https://www.w3.org/Bugs/Public/show_bug.cgi?id=17414
Olivier Thereaux, 7 Jun 2012, 15:41:44Display change log
