- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 15 Apr 2021 16:00:20 +0000
- To: public-webrtc-logs@w3.org
From looking at the spec, here is the list of obvious things that differ right now: - data is settable here, not in WebCodecs. This is expected to change in WebCodecs - 'empty' is a valid video frame here, not in WebCodecs. Not sure why we have 'empty' here so I hope we can drop it. - getMetadata is defined here, not in WebCodecs. This is expected to change in WebCodecs. - Some metadata fields are RTP specific and would stay here. The plan might be in this spec to: - Directly use EncodedVideoChunk and EncodedAudioChunk - Define the additional metadata fields using partial dictionaries To do so, we need WebCodecs to first fix attribute data setter and add getMetadata. @chcunningham, any thoughts on when these will happen in WebCodecs? If we directly use WebCodecs structures, we also need to ensure they stay aligned with our model and constraints here. For instance, we probably want to stick with readonly timestamps. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/99#issuecomment-820544226 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 15 April 2021 16:00:23 UTC