W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > January 2022

[webrtc-extensions] captureTimestamp seems to have an inconsistent clock base (#97)

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Wed, 26 Jan 2022 10:12:51 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-1114845980-1643191970-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/webrtc-extensions:

== captureTimestamp seems to have an inconsistent clock base ==
A straightforward reading of https://w3c.github.io/webrtc-extensions/#dom-rtcrtpcontributingsource-capturetimestamp seems to indicate that this clock is reading out in the NTP timebase (seconds since 1900), while all other times, including "timestamp" in the same dictionary, are represented in the Unix timebase (seconds since 1970).

This seems like a silly inconsistency that makes the value harder to use. Should we fix it?

Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/97 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 26 January 2022 10:12:53 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:55 UTC