Unable to use Hardware (GPU) encoding on Intel HD Graphics 5500 #3351
Comments
|
I think this is the same as this issue: #1784 (comment) |
|
Oh, yes. |
|
I don't think so. Intel has dropped support for your (10 year old) GPU in their QuickSync implementation. Reverting back to a very old version of the QuickSync libraries compatible with Broadwell would break newer features like AV1 and HEVC 4:4:4 support. |
|
Ok but i'ts not possible to use 2 libraries? I mean, one for the old hardware and the other one for the new hardware? |
|
...so I assume there is no hope to have these GPUs working... |
The MFX/oneVPL library used for QuickSync is deeply coupled with FFmpeg, so we would probably have to move FFmpeg into a separate library so we could ship 2 of them with Sunshine. It definitely wouldn't be easy or likely worth the maintenance and testing burden.
I agree, but it's not something we can reasonably control. We're at the mercy of what Intel is willing to support here. You might be able to compile your own build using an older version of the MFX library that will work on your hardware, but FFmpeg also has its own minimum version of the MFX library. If you're below that, you'll need to also downgrade FFmpeg to match. You can see how this gets to be a non-trivial problem pretty quick.
I believe they work on Linux today. Unlike the official QuickSync libraries, VAAPI is much better about backwards compatibility. You can still compile the open-source VAAPI drivers for these old GPUs and they will work on modern distros today. [Edit: For fun, I booted ArchLinux on my Intel Ivy Bridge testbench and it had working hardware encoding through VAAPI] There's also a possibility that we will implement a MediaFoundation-based encoder in the future for supporting Windows ARM64 devices. That would be independent of the QuickSync libraries, so it would also enable functionality for older GPUs that Intel dropped support for.
For Windows, I believe that is correct. |
|
But since VAAPI works also on Windows, why don't use it? |
I don't think it would solve anything in your case because VAOn12 (the VAAPI backend for Windows) requires encoding support via D3D12 Video APIs. Those were not introduced until Windows 11, which was after driver support for your GPU was already discontinued. According to Microsoft's blog post, D3D12 video encoding is only supported on Ice Lake and later. |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the latest beta/pre-release?
This issue is present in the latest pre-release
Describe the Bug
Hello.
I'm aware I'm using Sunshine on an "old" HP notebook with Intel i7-5600U CPU and the Video GPU is Intel HD Graphics 5500.
It seems Sunshine is not able to use the Hardware (GPU) acceleration during encoding, then during streaming the CPU is at 100% and the video is not smooth.
In addiction, some print-screnn about Windows Task Manager that show the CPU at 100%:
Just for test, I installed Parsec and it uses the GPU.
As you can see with Parsec the GPU is used and the CPU is very low:
I'm available to test if a fix will be applied.
Many thanks!
Expected Behavior
I expect that Sunshine will use the GPU and not the CPU for encoding,
Additional Context
No response
Host Operating System
Windows
Operating System Version
Windows 10
Architecture
amd64/x86_64
Sunshine commit or version
Version v2024.1031.235235
Package
Windows - installer (recommended)
GPU Type
Intel
GPU Model
HD 5500
GPU Driver/Mesa Version
.
Capture Method
None
Config
No response
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: