Jellyfin
Question for running Intel QSV Hardware Acceleration on Old Hardware (3rd gen Intel Core i5) #14444
-
|
Hello Jellyfin devs, I have a question. I'm using an Intel HD 2500, an Ivy Bridge generation iGPU on an i5-3570, which supports Intel Quick Sync Video decoding and encoding for MPEG-2 and AVC (H264) video codecs. When running QSV directly on ffmpeg, it works as expected. Based on my testing with GPU-Z, the GPU load increases, and compared to libx264, QSV is three times faster than regular libx264 CPU encoding. The ffmpeg command line I use is: However, when trying Jellyfin QSV Transcode, I noticed that Jellyfin sends different command arguments to ffmpeg. I understand that using complex chains of arguments is necessary for Jellyfin and similar setups, but when I try transcoding with QSV in Jellyfin, I get the following error: Could this issue be due to the ffmpeg version used by Jellyfin not supporting old, Intel Core i5 3rd generation graphics? The ffmpeg QSV wiki documentation also doesn’t list 3rd gen graphics. Sorry if it's weirdly worded. I'm just curious. Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
The oldest intel platform where QSV on Windows is known to work properly is Haswell which is 4th gen. Not sure about 3rd gen Ivy Bridge, intel has a habit of deprecating old platforms. If you still get the error after using DDU to wipe the old drivers and installing the drivers from intel.com, I'm afraid you need to upgrade your server. |
Beta Was this translation helpful? Give feedback.
-
|
I think the I don't see it attempting to fall back to libx264 either, but my CPU usage shoots up to 100% (probably since i didn't choose any of the Jellyfin decode checkboxes) with the Intel GPU load rising to 30-40%. Does this means the QSV is working? Also note, i also have a discrete AMD GPU (but it can't be used since it don't have encoding capabilities). on Task Manager, the Video Decode engine rises to 10-15% while playback. Does this mean it's a dead end trying to use QSV on such old hardware, or it means its working? I'm just testing and experimenting to see what works and what doesn't :) Thanks for answering! |
Beta Was this translation helpful? Give feedback.
-
|
Intel has dropped dxva2/dx9 in the latest VPL SDK, this might be the reason. As an alternative you can install Linux, where the intel-vaapi-driver still provides VA-API support for IVB. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @nyanmisaka I have an Intel Haswell-ULT Integrated Graphics [8086:0a06] with i915 driver support ( $ sudo vainfo --display drm --device /dev/dri/renderD128
[sudo] password for quazi:
libva info: VA-API version 1.20.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: va_openDriver() returns -1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_8
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.20 (libva 2.12.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.4.1
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264Main : VAEntrypointVLD
VAProfileH264High : VAEntrypointVLD
VAProfileH264MultiviewHigh : VAEntrypointVLD
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc
VAProfileJPEGBaseline : VAEntrypointVLDBut I have no ability to use it in Jellyfin's docker container services:
jellyfin:
image: jellyfin/jellyfin:10.11.4
container_name: jellyfin
network_mode: 'host' # optional but required in order to use DLNA
volumes:
- ./config:/config
- ./cache:/cache
- media:/media/media/
restart: 'unless-stopped'
environment:
- TZ=Europe/Minsk
- LIBVA_DRIVER_NAME=i965
- LIBVA_DRIVERS_PATH=/usr/lib/jellyfin-ffmpeg/lib/dri
extra_hosts:
- 'host.docker.internal:host-gateway'
group_add:
- 109 # Add container user to render group = 109
- 44 # Add container user to video group = 44
devices:
- /dev/dri/renderD128:/dev/dri/renderD128
- /dev/dri/card0:/dev/dri/card0I see that ffmpeg fails always when hw acceleration used for transcoding |
Beta Was this translation helpful? Give feedback.
-
|
h264 encoding is not supported on 8086:0a06, which is your gpu const static char *hsw_cpu_hook_list[] = {
"Intel(R)Pentium(R)3556U",
"Intel(R)Pentium(R)3560Y",
"Intel(R)Pentium(R)3550M",
"Intel(R)Celeron(R)2980U",
"Intel(R)Celeron(R)2955U",
"Intel(R)Celeron(R)2950M",
};
...
if (found) {
codec_info->has_h264_encoding = 0; // h264 encoding is not supported on 8086:0a06
codec_info->has_h264_mvc_encoding = 0;
codec_info->has_mpeg2_encoding = 0;
} |
Beta Was this translation helpful? Give feedback.
The oldest intel platform where QSV on Windows is known to work properly is Haswell which is 4th gen. Not sure about 3rd gen Ivy Bridge, intel has a habit of deprecating old platforms.
If you still get the error after using DDU to wipe the old drivers and installing the drivers from intel.com, I'm afraid you need to upgrade your server.