Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timing Metadata #167

Open
aboba opened this issue Dec 2, 2022 · 2 comments
Open

Timing Metadata #167

aboba opened this issue Dec 2, 2022 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@aboba
Copy link
Contributor

aboba commented Dec 2, 2022

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

@fippo
Copy link
Collaborator

fippo commented Dec 2, 2022

Proposal: add timing metadata to RTCEncoded*Metadata

@alvestrand
Copy link
Contributor

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?"

@alvestrand alvestrand added the enhancement New feature or request label Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants