- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Jan 2020 12:31:45 +0000
- To: public-webrtc-logs@w3.org
Edited the description with a correction: It is not the RTP timestamp that is rewritten by the server to account for the Sender->Server delay - it is the RTP->NTP mapping that adjusts for that difference. So this metric works as intended. However, when using contributing sources, we no longer have meaningful mappings between RTP timestamp and capture timestamp. In this case you either wouldn't have the RTCP information to do the mapping or the mapping you did have could become obsolete when the CSRC changes and you haven't gotten a new mapping. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/537#issuecomment-580231213 using your GitHub account
Received on Thursday, 30 January 2020 12:31:47 UTC