Need EncodedChunk to have video metadata to support WebRTC
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.3k
- Forks
- 194
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
The WebRTC Encoded Transform spec's VideoFrame object (https://w3c.github.io/webrtc-encoded-transform/#rtcencodedvideoframe) has a getMetadata function that returns information about the frame that is produced by the encoder, and needs to be passed on to consumers (and vice versa for decoders).
If we're going to harmonize RTCEncodedVideoFrame with EncodedVideoChunk, we need some way to provide this functionality.
(This bug is created as part of bug triage on webrtc-encoded-transform; all bugs that are about buffer formats should move here, I think.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked WebRTC Encoded Transform specification, especially the VideoFrame getMetadata function, then inspect the EncodedVideoChunk and RTCEncodedVideoFrame concepts described in the issue. Determine how encoder metadata should reach consumers and how decoder metadata should be passed back; done means the two APIs can be harmonized with this metadata support.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100