We are using **VisioForge MF Mux v11.0.0.0** in our 64-bit C# Windows application (Photo Booth Upload) and are experiencing an H.265 encoder initialization issue.
**Environment:**
- VisioForge_MF_Mux_x64.ax – Version 11.0.0.0
- CPU: Intel Core i9-12900H
- GPUs: Intel Iris Xe and NVIDIA RTX 3080 Ti Laptop GPU
- Encoder selected: QSV_H265
**Test Results:**
- H.264 encoding works successfully using Intel QSV at both 1080p and 4K.
- H.265 encoding fails at both 1080p and 4K.
- NVIDIA H.264/H.265 COM activation returns `0x8000FFFF`.
- Intel QSV_H265 COM detection succeeds, but actual encoding fails.
**H.265 Error Logs:**
```text
Selected encoder: QSV_H265
Video graph connected: 0x00000000
Audio graph connected: 0x00000000
Video encoder not found.
Unable to create MP4 encoder.
mediaControl.Run() failed: 0x80004005
```
The source MP4 is readable, and the video/audio graph connections succeed. The failure occurs when the VisioForge mux attempts to initialize the H.265 encoder.
**Questions:**
1. Does MF Mux v11.0.0.0 support Intel Quick Sync H.265 (`QSV_H265`) encoding?
2. Are there any known H.265 compatibility issues with this version?
3. Are specific Intel graphics drivers, Media Foundation settings, or HEVC encoder configurations required?
4. Would upgrading the VisioForge MF Mux resolve this issue? If yes, which version would you recommend?
5. Is there a way to enable detailed native encoder initialization logging to identify the underlying failure?
Please let us know what additional information or logs would help investigate this issue.