Closed nyanmisaka closed 2 years ago
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-136/index.html https://ci-tests.linuxserver.io/lspipepr/jellyfin/10.7.7-1-pkg-26621a5e-pr-136/shellcheck-result.xml
@nyanmisaka this is so much better, thanks
I'll merge when the tests are complete.
Do you think in the future, jellyfin can somehow note which version of the drivers ffmpeg is built against, somewhere that we can parse during build time so we don't have to manually update each time? Or is it already listed somewhere in the ffmpeg git repo (didn't look too hard)?
Do you think in the future, jellyfin can somehow note which version of the drivers ffmpeg is built against, somewhere that we can parse during build time so we don't have to manually update each time? Or is it already listed somewhere in the ffmpeg git repo (didn't look too hard)?
Yes. We can set the version of libva and other libs in build script so as to parse from it and intel’s repo.
Description:
Specify Intel iHD driver versions to avoid mismatched libva errors
Benefits of this PR and context:
Should fix these issues with upstream jellyfin-ffmpeg 4.4.1-1.
107
109
115
129
https://github.com/jellyfin/jellyfin/issues/5993
How Has This Been Tested?
Source / References: