- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Fri, 13 Aug 2021 13:59:20 +0000
- To: public-webrtc-logs@w3.org
Good question. The fact that there is a time before the first knowledge of the time-at-sender is a PITA for the microsecond-based timestamp; we could just do "offset is zero" in the previous comment, but then we'd never get to reset it according to the SR-carried NTP timestamp (timestamp jumps for no good reason are not a Good Thing). The simplest way is to declare this format "legacy" and change the definition to what the implementation does. Tagging @youennf who's tagged with the task of aligning the encoded-formats. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/116#issuecomment-898477143 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 13 August 2021 13:59:22 UTC