- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Nov 2022 10:09:45 +0000
- To: public-webrtc-logs@w3.org
There's currently no way to tell the encoder which RTP stream / encoding layer to forward the encoded chunk to other than by SSRC. But if instead of specifying SSRC you specified encoding layer, that would remove the need to figure out what SSRC to use. It's a good point actually. When we hacked together a POC, we obtained the SSRC by parsing SDP. But that SSRC is only exposed for backwards compat reasons, it would be perfectly valid for the browser not to expose what the SSRC is, so what would you do then? Using the encoding layer's index sounds more future-proof and makes the API simpler to use since you could use the same identifier regardless of which RTCRtpSender happens to be the receiver of the chunk! -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/issues/162#issuecomment-1330388155 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 November 2022 10:09:55 UTC