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

Add WebRTC-specific interactions with capture/receive/RTP timestamps #224

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

handellm
Copy link

@handellm handellm commented Sep 20, 2024

This PR changes the spec to describe how WebRTC interacts with timestamps added by w3c/mediacapture-extensions#156.

Related to changes needed by w3c/webcodecs#813


Preview | Diff

<p>
<!-- TODO: use the xref mechanism when mediacapture-extensions spec status is cleared up.
See https://github.com/w3c/mediacapture-extensions/issues/132 -->
The following terms are defined in <a href="https://w3c.github.io/mediacapture-extensions">mediacapture-extensions</a>
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Due to the unclear state of the mediacapture-extensions spec (not listed in browser-specs) I had to make some temporary reference structure as per below, when referring to concepts defined there.

@handellm handellm marked this pull request as ready for review December 19, 2024 11:10
{{MediaStreamTrack}} are sourced from the [=frame timestamp=].
</p>
<p>
The [=RTP timestamp=] of frames being produced on the {{RTCRtpSender}} is ignored.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The [=RTP timestamp=] of frames being produced on the {{RTCRtpSender}} is ignored.
The [=RTP timestamp=] of frames being produced on the {{RTCRtpSender}} is not visible in this API.

@@ -1540,6 +1553,46 @@ <h2>Event summary</h2>
</tbody>
</table>
</section>
<section class="informative">
<h2>Timestamp behavior</h2>
<h2>RTCRtpSender timestamp effects on packet NTP and RTP timestamps</h2>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<h2>RTCRtpSender timestamp effects on packet NTP and RTP timestamps</h2>
<h2>RTP timestamp effects on packet NTP and RTP timestamps</h2>

there is nothing in the spec that says that incoming RTP is coming from an RTPSender.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants