@henbos [timestamp](http://w3c.github.io/webrtc-pc/#dom-rtcrtpcontributingsource-timestamp) is poorly named here: It indicates *"the most recent time of* **playout** *of media"*. It's predicted playout time through a media element. It's ***not*** the RTP timestamp. As @fippo [mentions](https://github.com/w3c/webrtc-pc/issues/1983#issuecomment-421010310): this API was designed specifically for audio bars per participant. *getStats* was deemed too slow for this purpose, which is why these synchronous methods exists. Are there compelling use-cases for runtime playout time estimation of video? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1983#issuecomment-425080297 using your GitHub accountReceived on Thursday, 27 September 2018 12:57:07 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:45 UTC