- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Apr 2023 14:14:55 +0000
- To: public-webrtc-logs@w3.org
Thanks, microseconds makes sense now. However, I remain concerned about the name. Consistency with [VideoFrame](https://w3c.github.io/webcodecs/#dom-videoframe-timestamp) and [EncodedVideoChunk](https://w3c.github.io/webcodecs/#dom-encodedvideochunkinit-timestamp) would mean calling it _"`timestamp` ... The presentation timestamp, given in microseconds. The timestamp is copied from the [EncodedVideoChunk](https://w3c.github.io/webcodecs/#encodedvideochunk) corresponding to this VideoFrame."_ However, in [RTCEncodedVideoFrame](https://w3c.github.io/webrtc-encoded-transform/#rtcencodedvideoframe) `timestamp` is taken (used for RTP). But there's a comment claiming this _"will eventually re-use or extend the equivalent defined in WebCodecs"_ (presumably [EncodedVideoChunk](https://w3c.github.io/webcodecs/#encodedvideochunk))? <img width="839" alt="image" src="https://user-images.githubusercontent.com/3136226/231479567-a0ae6e26-1ba1-4d40-80d0-b8166dec08fe.png"> If that is still our intent, we would appear to be at a crossroads. Is it too late to align this? -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/173#issuecomment-1505356908 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 April 2023 14:14:56 UTC