Skip to content

Conversation

@m1k1o
Copy link
Owner

@m1k1o m1k1o commented Dec 8, 2021

SDP is wrong.

Chrome says:

DOMException: Failed to execute 'createAnswer' on 'RTCPeerConnection': Session error code: ERROR_CONTENT. Session error description: Failed to set remote video description send parameters for m-section with mid='0'..

And firefox refuses codec support.

image

@Crystalizedskytheater

This comment was marked as spam.

@Gauvino
Copy link

Gauvino commented Apr 1, 2023

Does you have info about making this know cause chrome and other have the support natively now ?

@m1k1o
Copy link
Owner Author

m1k1o commented Apr 1, 2023

@Uruknara I don't have any new info. Support is still not quite widespread. But this PoC could be repeated to see what changed in last 1.25 years.

@m1k1o
Copy link
Owner Author

m1k1o commented Mar 28, 2025

WebRTC H265 Support in chrome is targeted for release M136
https://issues.chromium.org/issues/391903235

Safari already supports the HEVC codec in WebRTC.

@Mmx233
Copy link
Contributor

Mmx233 commented May 20, 2025

M136 has been released in the stable channel for a month. Could we please move this PR forward?

https://chromestatus.com/roadmap

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants