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
To date, no attributes have been approved in the VideoFrame registry, and it is not clear that the administrative burden of a VideoFrame or encodedChunk registry is worth the benefit.
As long as WebCodecs behavior is not changed by addition of encodedChunk (or VideoFrame) metadata, the benefit of a registry comes from the avoidance of conflicts. However, this goal can be accomplished without a registry, through the issuance of unique identifiers.
We now have a proposal to add some timing information to the
RTCEncodedVideoFrameMetadata
: w3c/webrtc-encoded-transform#173Would it make sense to define a metadata registry for
encodedChunk
and add similar info there?The text was updated successfully, but these errors were encountered: