- From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Dec 2023 13:00:29 +0000
- To: public-webrtc-logs@w3.org
If using a webcodecs encoder to encode a frame that is to be sent on an RTCPeerConnection, there has to be a step that supplies the metadata that the WebCodecs encoder does not supply. Doing that as part of the conversion step between WebCodecs encodedFrame and RTCRtpEncodedFrame seems logical. It's a small amount of data. WRT the PT, I think we're getting to a consensus that frames should be marked with MIMEtype, and that the processing step that needs a PT should look up the PT from the MIMEtype - since this lookup is transceiver-dependent, it seems logical to do the lookup when the frame is enqueued on a packetizer, not before this. This means, of course, that MIMEtype needs to be writable. -- GitHub Notification of comment by alvestrand Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/211#issuecomment-1842835330 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 December 2023 13:00:31 UTC