- From: Ben Ritchie via GitHub <sysbot+gh@w3.org>
- Date: Sun, 17 Jan 2021 22:05:57 +0000
- To: public-webrtc-logs@w3.org
> I don't think it makes a lot of sense to do > audioOffsetFromVideo = e2eVideoDelay - e2eAudioDelay; > > as it doesn't provide any value and introduces errors. remoteAudio/Video.currentTime are estimates which can be wrong, and audio/videoTrackStats.currentPlayoutTimestamp should already be based on the same clocks and therefore be directly comparable. It doesn't matter when audio or video started > playing. > > Am I misunderstanding something, or why isn't this enough: > > audioOffsetFromVideo = videoTrackStats.currentPlayoutTimestamp - audioTrackStats.currentPlayoutTimestamp Apologies for barging in on this old thread but I tried to do this (to debug lipsync issues Im seeing in Twilio implementation) and the currentPlayoutTimestamp seems to be static and unchanging in my chrome dump, any ideas what I am doing wrong? -- GitHub Notification of comment by haveaguess Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/158#issuecomment-761888475 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 17 January 2021 22:05:59 UTC