Repository navigation
Conversation
|
Generally looks good. See questions in #185 (posting there to increase visibility). |
marcoscaceres
left a comment
There was a problem hiding this comment.
Couple of suggestions...
|
I think we need this, now that we're using codec descriptions more in APIs. |
|
Discussed at today's WebRTC interim and this would probably help moving WebRTC piggy backing on Media Capabilities to expose codecs (instead of exposing all/most codecs). |
Co-authored-by: Marcos Cáceres <marcos@marcosc.com>
Co-authored-by: Marcos Cáceres <marcos@marcosc.com>
Co-authored-by: Marcos Cáceres <marcos@marcosc.com>
Co-authored-by: Marcos Cáceres <marcos@marcosc.com>
|
I wonder if this should be marked for the V2 milestone (instead of V1) since it's adding a new feature / API surface. |
|
This currently seems underspecified in terms of deriving the |
There was a problem hiding this comment.
Pull Request Overview
This PR adds WebRTC codec capability information to the Media Capabilities API by introducing a new webrtc parameter to MediaCapabilitiesInfo. This enhancement allows developers to obtain detailed codec information for WebRTC scenarios and configure codec preferences using the RTCRtpTransceiver API.
- Introduces
WebRTCMediaCapabilitiesInfodictionary with optional audio and video codec capabilities - Extends
MediaCapabilitiesInfowith an optionalwebrtcfield - Updates encoding and decoding algorithms to populate WebRTC codec information when applicable
|
looks like this needs a rebase |
|
This has been migrated to #250 , please add new comments there. |
Fixes #185
Preview | Diff