Draft
Conversation
This comment was marked as spam.
This comment was marked as spam.
|
Does you have info about making this know cause chrome and other have the support natively now ? |
Owner
Author
|
@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. |
Owner
Author
|
WebRTC H265 Support in chrome is targeted for release M136 Safari already supports the HEVC codec in WebRTC. |
Contributor
|
M136 has been released in the stable channel for a month. Could we please move this PR forward? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SDP is wrong.
Chrome says:
And firefox refuses codec support.