- From: T H Panton <tim@pi.pe>
- Date: Wed, 16 Mar 2022 14:25:52 +0100
- To: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
- Cc: public-webrtc@w3.org
> On 16. Mar 2022, at 11:53, Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org> wrote:
>
> murillo128 has just created a new issue for https://github.com/w3c/webrtc-extensions:
>
> == Allow having inactive by default codecs ==
> I am currently adding support for vp9 profile 1 and 3 and h264 Hi10P and Hi422P to libwebrtc, and the SDP generated is HUGE:
>
> 
>
> Most of these codec/profiles won't be used on a daily base, so I would be great if there could be a way of having them disabled by default so they don't appear on the offer (but they are negotiated on the answer) and have an API to enable them by the app if needed.
>
> I don't think we have anything similar at the moment.
>
In theory you can use:
transceiver.setCodecPreferences(codecs);
To reduce the size of the SDP, but there is a _super_ narrow moment when it can be called.
Also it doesn’t address your defaults point. Perhaps some way of managing capability sets is needed?
So RTCRtpSender.getCapabilities('video’) would return the normal mortals set and
RTCRtpSender.getExtendedCapabilities(‘video’) would give the full list, from which you’d select the subset you wanted to offer and call setCodecPrefs with that subset.
T.
>
> Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/100 using your GitHub account
>
>
> --
> Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
>
Received on Wednesday, 16 March 2022 13:26:10 UTC