W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > December 2022

[mediacapture-transform] Timing Model (#88)

From: Bernard Aboba via GitHub <sysbot+gh@w3.org>
Date: Fri, 02 Dec 2022 17:12:44 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-1473184625-1670001162-sysbot+gh@w3.org>
aboba has just created a new issue for https://github.com/w3c/mediacapture-transform:

== Timing Model ==
How is timing information carried across the pipeline (between VideoFrames and encodedChunks, serialization/deserialization on the wire, between encodedChunks and VideoFrames)?

What timing information is provided in VideoFrames generated in mediacapture-transform, and is this carried across MediaStreamTracks consumed by other APIs (e.g. WebRTC-PC)? 

Timing Model discussed at [November VI](https://www.w3.org/2022/11/15-webrtc-minutes.html#t06)

 [VideoFrameCallbackMetaData](https://wicg.github.io/video-rvfc/#video-frame-metadata-callback) in [rVFC](https://wicg.github.io/video-rvfc/#video-frame-metadata-callback-attributes) specification includes receiveTime, captureTime, rtpTimestamp, mediaTime.

Resolution: “file specific issues on specific specs”

Related: [Issue 601](https://github.com/w3c/webcodecs/issues/601): Expose in VideoFrame

Use case: https://www.w3.org/TR/webrtc-nv-use-cases/#auction

Please view or discuss this issue at https://github.com/w3c/mediacapture-transform/issues/88 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 December 2022 17:12:45 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:59 UTC