Reuse WebCodec audio/video chunk definitions#101
Conversation
| readonly attribute ArrayBuffer data; | ||
| }; | ||
|
|
||
| // WebCodecs definitions with introduction of EncodedMediaChunk to more easily refer to timestamp and data. |
There was a problem hiding this comment.
shouldn't this be brought directly back to WebCodecs?
There was a problem hiding this comment.
I would prefer we get agreement on the strategy first, like get agreement to reuse WebCodecs constructs, then start discussing with WebCodecs how we can best do things.
With regards to EncodedMediaChunk, I did not think about it to hard, we might want to use a mixin instead of inheritance.
| "empty", | ||
| interface mixin EncodedMediaChunk { | ||
| readonly attribute unsigned long long timestamp; // microseconds | ||
| readonly attribute ArrayBuffer data; |
There was a problem hiding this comment.
Now that I look at it, data is readonly here but we want to be able to change it in RTCRtpSFrameTransform transforms.
|
Discussed with @aboba, and the plan might be to remove all encoded audio/video frames but leave RTP metadata specific bits, for instance as partial dictionaries. |
|
Related WebCodecs issues: |
3 participants
Initial try at fixing #99
Preview | Diff