You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How is timing information carried across the pipeline (between VideoFrames and encodedChunks, serialization/deserialization on the wire, between encodedChunks and VideoFrames)?
the question with timing data is always "in which clock?" And in particular, with cross-network flows, "how can you tell how fast/slow/offset the other end's clock is?"
How is timing information carried across the pipeline (between VideoFrames and encodedChunks, serialization/deserialization on the wire, between encodedChunks and VideoFrames)?
Timing Model discussed at November VI
VideoFrameCallbackMetaData in rVFC specification includes receiveTime, captureTime, rtpTimestamp, mediaTime.
Resolution: “file specific issues on specific specs”
Related: Issue 601: Expose in VideoFrame
Related: w3c/mediacapture-transform#88
Use case: https://www.w3.org/TR/webrtc-nv-use-cases/#auction
The text was updated successfully, but these errors were encountered: