MicrosoftEdge / MicrosoftEdge/MSEdgeExplainers

H.265 HEVC in WebRTC?

Open
#1,273 7 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
HTML
Stars
1.4k
Forks
286
Avg merge
3d 1h
Merged PRs (30d)
8

Description

I apologize if this is not the right place to ask, but I'm trying to understand the relation ship between the HEVC Video Extensions and Edge as well as any information on support with WebRTC.

H.265 HEVC is not currently supported with an RTCPeerConnection. I have the HEVC Video Extensions installed, but I'm unclear on if that is even needed. From what I can tell support shipped in Chrome 136. Is there an intent to enable support within Edge, and if so will it require the HEVC Video Extensions?

Relevant links:

https://chromium.googlesource.com/chromium/src/+/8ca090ecf9fcb51daaa549bbce830511b62f00aa
https://issues.chromium.org/issues/341986313
https://chromestatus.com/feature/5153479456456704

https://vdo.ninja/h265 when opened in Chromium vs Edge on the same Windows 11 machine confirms lack of support vs Chromium.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Chromium commit, Chromium issue 341986313, and ChromeStatus entry; compare the vdo.ninja behavior in Edge and Chromium on Windows 11. The issue is complete only when Edge's H.265 WebRTC support status and HEVC Video Extensions requirement are confirmed by the Edge team.

Written by the indexing model from the issue text.

Assessment

Domain
audio-video-rtc
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.