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
rtpTimestamp is already defined in VideoFrameCallbackMetadata so it seems logical to have it also be a property of encoded chunks in both Encoded Transform and WebCodecs.
To update on what's been happening: #173 added the long long timestamp type into the Metadata, so we at least now have that field matching the webcodecs field in both type and definition.
I created #203 to move the RTP timestamp to metadata and rename it to explicitly be rtcTimestamp - so the first bulletpoint in fippo's original comment.
see also #116
https://w3c.github.io/webrtc-encoded-transform/#RTCEncodedVideoFrame-interface
and
https://w3c.github.io/webrtc-encoded-transform/#RTCEncodedAudioFrame-interface
both define a timestamp as
which by definition is the RTP timestamp (and this was changed to align with implementations).
This is different from what we have in Webcodecs
This is hard to fix so we should do this as follows:
The text was updated successfully, but these errors were encountered: