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-105 (MIDI timestamp resolution): timestamps in MIDI should use High Resolution Time [MIDI API] http://www.w3.org/2011/audio/track/issues/105 Raised by: Adam Goode On product: MIDI API The current MIDI API specifies timestamp as a long representing "milliseconds from the UNIX Epoch". For MIDI applications, millisecond resolution is insufficient and can cause noticeable jitter. Using absolute wallclock time is also problematic, as it is subject to system clock skew. The MIDI timestamp should use High Resolution Time (DOMHighResTimeStamp), which solves these problems: http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/HighResolutionTime/Overview.html
Proposed changeset: https://dvcs.w3.org/hg/audio/rev/b78b7c5e906e
Discussion thread since proposed changeset: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/thread.html#msg497
General acceptance of HRT.
(In reply to comment #3) > General acceptance of HRT. From the e-mail thread (linked above) I see Philip expressed preference for seconds, but did not have a strong objection. Giving the group another occasion to object, but I think we have reasonable consensus around HRT at this time.
(In reply to comment #4) > Giving the group another occasion to object, but I think we have reasonable > consensus around HRT at this time. Closing.