Closed jussi-kalliokoski closed 11 years ago
Original comment by Olivier Thereaux on W3C Bugzilla. Thu, 07 Jun 2012 15:06:57 GMT
Proposed changeset: https://dvcs.w3.org/hg/audio/rev/b78b7c5e906e
Original comment by Olivier Thereaux on W3C Bugzilla. Thu, 07 Jun 2012 15:08:00 GMT
Discussion thread since proposed changeset: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/thread.html#msg497
Original comment by Chris Wilson on W3C Bugzilla. Mon, 15 Oct 2012 18:27:30 GMT
General acceptance of HRT.
Original comment by Olivier Thereaux on W3C Bugzilla. Wed, 24 Oct 2012 09:13:31 GMT
(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.
Original comment by Olivier Thereaux on W3C Bugzilla. Thu, 15 Nov 2012 09:58:54 GMT
(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.
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