Closed nyanmisaka closed 2 years ago
@aptalca Could you review this? Thanks.
I am a bot, here are the test results for this PR: https://ci-tests.linuxserver.io/lspipepr/jellyfin/10.7.7-1-pkg-26621a5e-pr-135/index.html https://ci-tests.linuxserver.io/lspipepr/jellyfin/10.7.7-1-pkg-26621a5e-pr-135/shellcheck-result.xml
Thanks for lending a hand, but I don't think uploading a binary to our git repo is the proper solution to this for a couple of reasons: 1) It doesn't work with our ci automation (would require a new upload to git and a commit every time it's updated) 2) We prefer having full transparency as to how everything in our images is built or where they came from so we avoid uploading binaries manually (curling one during build from an upstream repo would be fine)
How is jellyfin currently handling this with their image? Wouldn't it be ideal for jellyfin to ship the necessary drivers alongside ffmpeg in their apt repo? Or perhaps link the correct version of the intel driver as a dep for it?
Actually I am awared of these when writing this PR.
The reason why jellyfin forked from emby is that they used some libraries that are not compatible with GPL and they refused to provide source code. Therefore, avoiding non-free things has always been a rule in the core team since day 1.
So no non-free driver is included in jellyfin official images. User have to build or install it manually to enable QSV support.
Or perhaps link the correct version of the intel driver as a dep for it?
I think this advice is feasible, we have to specify a certain version of intel driver for apt install. Drivers usually doesn't need to be updated frequently, unless the key functions or fixes we need are introduced.
This PR can be closed by #136
Description:
Switch to custom
jellyfin-ffmpeg
package that contains full feature Intel iHD driver.I will continue to maintain this package whenever the upstream tags a new release.
You can also build it by removing the commented out lines around https://github.com/jellyfin/jellyfin-ffmpeg/blob/883570db52d230f7f9ab6c532069002d7a5ed90c/docker-build.sh#L165
The
intel-media-driver-non-free
package from intel repo is always linked against their latestlibva
, which will break the QSV/VAAPI support in our ffmpeg over time.Benefits of this PR and context:
libva
version errors.107
109
115
129
https://github.com/jellyfin/jellyfin/issues/5993
How Has This Been Tested?
Intel QSV/VAAPI HWA + OpenCL/VPP Tone-mapping are all verified with
jellyfin-ffmpeg
4.4.1-1.I'm the main maintainer of
jellyfin-ffmpeg
in the past two years, many HWA improvements have been made in this new ffmpeg and the upcoming Jellyfin 10.8 release. Hope everyone who uses linuxserver container can enjoy it!