Skip to content

Introduce a RTCEncodedFrameMetadata dictionary to share more definitions between audio and video metadata #245

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

Closed
youennf opened this issue Apr 18, 2025 · 0 comments · Fixed by #250

Comments

@youennf
Copy link
Collaborator

youennf commented Apr 18, 2025

We could introduce:

dictionary RTCEncodedFrameMetadata {
    unsigned long synchronizationSource;
    octet payloadType;
    sequence<unsigned long> contributingSources;
    unsigned long rtpTimestamp;
    DOMHighResTimeStamp receiveTime;
    DOMHighResTimeStamp captureTime;
    DOMHighResTimeStamp senderCaptureTimeOffset;
    DOMString mimeType;
};
dictionary RTCEncodedAudioFrameMetadata : RTCEncodedFrameMetadata {
    ...
};
dictionary RTCEncodedVideoFrameMetadata : RTCEncodedFrameMetadata {
    ...
};

Similarly, for RTCEncodedAudioFrame and RTCEncodedVideoFrame, we could introduce:

interface mixing RTCEncodedFrame {
    attribute ArrayBuffer data;
};
RTCEncodedAudioFrame includes RTCEncodedFrame;
RTCEncodedVideoFrame includes RTCEncodedFrame;
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 a pull request may close this issue.

1 participant