- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Sat, 20 Mar 2021 18:09:59 +0000
- To: public-webrtc-logs@w3.org
> In addition to feedback streams, this needs the capacity for telling the browser "don't bother with instantiating encoders/decoders, I'm doing this myself". Indeed, the pluggable codec use case seems like an additional API to me which would run prior WebRTC encoded transform in senders, and after in receivers. For instance, WebRTC encoded transform API is solely based on RTCEncodedVideoFrame/RTCEncodedAudioFrame. Pluggable codecs will probably also rely on AudioFrame/VideoFrame objects. I could see some requirements derived for WebRTC encoded transform API from the pluggable codec use case. For instance, it might be beneficial for encoded transform API to provide ways to read/write RTP headers. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/90#issuecomment-803436980 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 20 March 2021 18:10:01 UTC