Skip to content

Add a new webrtcCodec parameter to MediaCapabilitiesInfo - #186

Closed
youennf wants to merge 6 commits into
w3c:mainfrom
youennf:issue-185
Closed

youennf wants to merge 6 commits into
w3c:mainfrom
youennf:issue-185

Conversation

@youennf

@youennf youennf commented Nov 19, 2021 •

Copy link
Copy Markdown
Contributor

Fixes #185


Preview | Diff

@chcunningham

Copy link
Copy Markdown
Contributor

Generally looks good. See questions in #185 (posting there to increase visibility).

Comment thread index.bs Outdated
Comment thread index.bs Outdated
Comment thread index.bs
Comment thread index.bs
Comment thread index.bs Outdated
Comment thread index.bs
Comment thread index.bs Outdated

@marcoscaceres marcoscaceres left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple of suggestions...

@alvestrand

alvestrand commented Jan 25, 2024 •

Copy link
Copy Markdown

I think we need this, now that we're using codec descriptions more in APIs.
Ref #webrtc-encoded-transform issue 172 for one example of such usage.

@youennf

youennf commented Feb 20, 2024

Copy link
Copy Markdown
Contributor Author

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).

@chrisn chrisn added the webrtc label Jul 9, 2024
chrisn and others added 4 commits September 13, 2024 19:55
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>
@chrisn chrisn added the TPAC2024 Topic for discussion at TPAC 2024 label Sep 13, 2024
@markafoltz

Copy link
Copy Markdown
Contributor

I wonder if this should be marked for the V2 milestone (instead of V1) since it's adding a new feature / API surface.

Comment thread index.bs
@markafoltz

Copy link
Copy Markdown
Contributor

This currently seems underspecified in terms of deriving the webrtc.audio and webrtc.video values from other values passed into the API.

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 WebRTCMediaCapabilitiesInfo dictionary with optional audio and video codec capabilities
  • Extends MediaCapabilitiesInfo with an optional webrtc field
  • Updates encoding and decoding algorithms to populate WebRTC codec information when applicable

@marcoscaceres

Copy link
Copy Markdown
Member

looks like this needs a rebase

Comment thread index.bs
@markafoltz markafoltz added TPAC2025 Agenda topic for TPAC 2025 and removed TPAC2024 Topic for discussion at TPAC 2024 labels Aug 25, 2025
markafoltz added a commit that referenced this pull request Nov 10, 2025
@markafoltz

Copy link
Copy Markdown
Contributor

This has been migrated to #250 , please add new comments there.

@markafoltz markafoltz closed this Nov 10, 2025
markafoltz added a commit that referenced this pull request Nov 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

TPAC2025 Agenda topic for TPAC 2025 webrtc

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Retrieving RTCRtpCodecCapability from MediaCapabilities when queried for webrtc

8 participants