You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-up to #15. When the system has no hardware H.264 Media Foundation Transform (MFT) registered (e.g. broken AMD AMF registration, missing GPU drivers, headless / no-GPU environments), OpenScreen currently fails outright. We should fall back to the Windows software H.264 encoder (mfh264enc.dll) so recording still works — slower, but functional.
Context
See #15 for the root cause analysis. Items 1 and 2 (pre-flight MFT check + better error message) are landing separately. This issue is specifically about the fallback path.
The software encoder is registered under the same category (MFT_CATEGORY_VIDEO_ENCODER) with a different CLSID and no MF_TRANSFORM_FLAG_HARDWARE attribute. MFTEnumEx returns both.
Add a config flag (preferSoftwareEncoder: boolean) so users can opt in permanently (e.g. on VMs or broken-driver machines) and so the smoke tests are deterministic.
Summary
Follow-up to #15. When the system has no hardware H.264 Media Foundation Transform (MFT) registered (e.g. broken AMD AMF registration, missing GPU drivers, headless / no-GPU environments), OpenScreen currently fails outright. We should fall back to the Windows software H.264 encoder (mfh264enc.dll) so recording still works — slower, but functional.
Context
See #15 for the root cause analysis. Items 1 and 2 (pre-flight MFT check + better error message) are landing separately. This issue is specifically about the fallback path.
Proposed approach
Acceptance criteria
pm run test:wgc-helper:win) covers the software path.
Out of scope