- From: yuanchao0310 via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 May 2022 14:53:45 +0000
- To: public-webrtc@w3.org
yuanchao0310 has just created a new issue for https://github.com/w3c/webrtc-extensions: == senderReceiverTimeOffset should use remoteOutboundRtpStats.roundTripTime == in https://github.com/w3c/webrtc-extensions/blob/main/explainer.md#api-2-sendercapturetimeoffset `senderReceiverTimeOffset = remoteOutboundRtpStats.timestamp - (remoteOutboundRtpStats.remoteTimestamp + remoteInboundRtpStats.roundTripTime / 2); ` if receiver is a recv only endpoint, it cannot get remoteInboundRtpStats.roundTripTime, because [remoteInboundRtpStats.roundTripTime](https://www.w3.org/TR/webrtc-stats/#dom-rtcremoteinboundrtpstreamstats-roundtriptime) use SR and RR to get rtt time, that means the receiver must send RTP to remote peer. so need use [remoteOutboundRtpStats.roundTripTime](https://www.w3.org/TR/webrtc-stats/#dom-rtcremoteoutboundrtpstreamstats-roundtriptime), which can be calculated by XR RTCP at receiver side. after update: > stats = peerconnection.getStats(); remoteOutboundRtpStats = getRequiredStats(stats, "remote-outbound-rtp"); senderReceiverTimeOffset = remoteOutboundRtpStats.timestamp - (remoteOutboundRtpStats.remoteTimestamp + remoteOutboundRtpStats.roundTripTime / 2) Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/109 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 May 2022 14:53:46 UTC