- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 17 Nov 2023 20:18:49 +0000
- To: public-webrtc-logs@w3.org
> SDP negotiates codecs per m-line and does not support per-codec directionality. Ah, thanks for clarifying! https://github.com/w3c/webrtc-pc/issues/2888 confused me a bit. So end-points may have directional codec limitations, but m-lines cannot express them? Still, I can use `transceiver.sender.setParameters` to send e.g. h264 while my `transceiver.receiver` receives vp8, right? > I would agree to a statement saying baking SDP into the API as transceivers botched it though. 👍 In this case, the SDP result is an effect of applying a transform: - If I apply an [RTCRtpScriptTransform](https://w3c.github.io/webrtc-encoded-transform/#rtcrtpscripttransform) then I need to specify what "codec" describes it. - If I apply an [SFrameTransform](https://w3c.github.io/webrtc-encoded-transform/#sframetransform) then I don't. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-encoded-transform/pull/186#issuecomment-1817047712 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 17 November 2023 20:18:51 UTC