- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 23 Aug 2024 16:04:58 +0000
- To: public-webrtc-logs@w3.org
Note the **codec _dictionary_ match** algorithm only exists because codecs aren't interfaces. See https://github.com/w3c/webrtc-pc/issues/2955#issuecomment-2061510183. It exists to _differentiate_ codecs — i.e. these two are not the same thing, vs these two are the same thing — it does NOT speak to what codecs UAs should select in any particular situation (except where explicitly called from algorithms). Had they been interfaces, it would clear up that the only allowed API _inputs_ are local API _outputs_. E.g. constructing your own dictionary based on remote information is invalid if not not found locally. That said, I don't have a strong opinion on how browsers should respond when a `codec` parameter becomes outdated. Best efforts seems desirable given there's little in the way of reading back the effect of a set `codec` parameter, except stats. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2987#issuecomment-2307382396 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 23 August 2024 16:04:59 UTC