- From: Stefan Holmer via GitHub <sysbot+gh@w3.org>
- Date: Thu, 09 Feb 2017 08:53:30 +0000
- To: public-webrtc-logs@w3.org
Harald, you are right, that would be an option. I'm not sure what is easiest to interpret and explain. Robin, I think you've got it right, but there are other ways to define them too, and I think this is simpler: 1. currentEstimatedCaptureTime - What our estimate of the capturer's clock of this video element is right now (i.e., if a frame was captured now, this is what the timestamp would be). 2. currentlyPlayedCaptureTimestamp - The timestamp which would be played out now if there was something to play out. e2eVideoDelay = video.currentEstimatedCaptureTime - video.currentlyPlayedCaptureTimestamp AVSync = audio.currentlyPlayedCaptureTimestamp - video.currentlyPlayedCaptureTimestamp -- GitHub Notification of comment by stefanholmer Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/158#issuecomment-278582397 using your GitHub account
Received on Thursday, 9 February 2017 08:53:36 UTC