- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Tue, 13 Feb 2024 12:14:17 +0000
- To: public-webrtc-logs@w3.org
> We haven't unshipped default . The answerer will try to match the order unless it uses sCP to override it I mean we only support "offer send codecs" if the send codecs are sendrecv codeces, we're making this not work for the sendonly codec use case. > I am still looking for a sendonly codec (and thought I had one but ... nope). We might want to be future proof. Besides, custom codecs might become a thing? Should they have to be sendrecv? > But if you look at the differences you'll notice that so far we are just extending profiles (in their different spellings) of already supported codec families, some of which define rules for dealing with this kind of stuff. So we're only changing things for certain profiles. I'm having trouble understanding what this means in practice? Is there anything we could previously do that we can no longer do? -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2937#issuecomment-1941383002 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 13 February 2024 12:14:20 UTC