- From: Tony Herre via GitHub <sysbot+gh@w3.org>
- Date: Thu, 07 Sep 2023 07:19:08 +0000
- To: public-webrtc-logs@w3.org
I thought the same re #169 , but re-reading it before filing the PR it seems to be suggesting that we should try to map the existing `timestamp` field to the WebCodecs encoded frame timestamp by changing to `long long` etc. AIUI, the path we settled on in #173 was a little different - adding the new `long long Metadata.timestamp` field holding the presentation time, so matching the WebCodecs field, and rename the old `unsigned long timestamp` to make it explicit that it's holding the RTP timestamp. I'll add a comment over there too. -- GitHub Notification of comment by tonyherre Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/203#issuecomment-1709607877 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 7 September 2023 07:19:10 UTC