fix(OPEN-20): Intel iGPU WebRTC black video on Windows#177
Closed
fix(OPEN-20): Intel iGPU WebRTC black video on Windows#177
Conversation
Detect Intel-only systems via Win32_VideoController and omit D3D11/MF video features so Chromium falls back to CPU decoders, avoiding black video on some ANGLE/Intel configurations. Co-authored-by: Zortos <zortosdev@proton.me>
Collaborator
Author
|
Better fix for this is coming |
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
2 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.
Description
On some Intel-only (iGPU) Windows machines, Chromium’s D3D11 + Media Foundation WebRTC video path can fail to decode frames while the connection stays up—symptoms match OPEN-20 (black video, 0.0 Mbps, Connecting..., ANGLE/Intel in diagnostics).
This change detects Intel-only systems at startup (via
Win32_VideoController: no NVIDIA/AMD adapter names) and sets software video decode and encode for Chromium: we omitD3D11VideoDecoder/MediaFoundationD3D11VideoCapturefromenable-featuresand applydisable-accelerated-video-decode/disable-accelerated-video-encode, so WebRTC uses CPU decoders (e.g. OpenH264 / dav1d) instead of the broken HW path.If GPU enumeration fails, behavior stays auto (unchanged).
Files:
opennow-stable/src/main/videoAccelerationBootstrap.ts(new),opennow-stable/src/main/index.ts(wire-up).Testing:
npx tsc --noEmitinopennow-stable(node + app tsconfigs). Runtime verification requires an Intel-only Windows machine with the reported issue.Linear Issue: OPEN-20