mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-01-23 23:20:51 +01:00
HEVC on VAAPI & AMD AMF on Jellyfin 10.6.0 Docker #1903
Labels
No labels
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
EFjellyfin.db
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: starred/jellyfin#1903
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Protektor-Desura on GitHub (Jul 20, 2020).
On Jellyfin 10.6.0 the render group has been fixed for /dev/dvi/renderD128 but VAAPI will not transcode HEVC because the docker does not include Mesa 20.1 or higher. I can't fix this using the last fix because you have switched the base image away from Ubuntu and over to Debian Buster which doesn't have a ppa for the newest Mesa. So you will have to compile these yourself and add the updated libraries to the docker image or switch the docker image back to Ubuntu, more specifically Ubuntu 20.04 and then let us use the PPA to upgrade the Mesa libs to at least Mesa 20.1.
If this isn't done then VAAPI and HEVC hardware transcoding will never work and AMD AMF transcoding will never work.
@Protektor-Desura commented on GitHub (Jul 20, 2020):
I can verify that any codec other then HEVC works with the current setup. But the second you get HEVC involved in anyway then it breaks. H.264, MPEG2, VC1 all work without any issues.
@stale[bot] commented on GitHub (Nov 19, 2020):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@Protektor-Desura commented on GitHub (Nov 22, 2020):
Still an issue.
@viggy96 commented on GitHub (Feb 17, 2021):
IMO, Jellyfin's official image should include an updated version of Mesa to aid users who use AMD instead of NVIDIA. There are users out there who refuse to buy NVIDIA products who would benefit from this.
@Protektor-Desura commented on GitHub (Feb 18, 2021):
I tried to recommend that but got shot down.
@yesrod commented on GitHub (Feb 18, 2021):
Bullseye is frozen; it has the newer version of Mesa needed. Once the official Docker containers update to Bullseye, we'll be set.
@viggy96 commented on GitHub (Feb 18, 2021):
@yesrod That's not really a solution though. Mesa is not updated often enough in Debian stable. Debian testing might be a more suitable choice.
@viggy96 commented on GitHub (May 3, 2021):
Could we at the very least have the backports repository enabled in the image to have a more updated Mesa version?
@stale[bot] commented on GitHub (Sep 21, 2021):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@NCLI commented on GitHub (Jan 4, 2022):
Still a huge issue.
@crobibero commented on GitHub (Jan 4, 2022):
This is not an issue in 10.8
@viggy96 commented on GitHub (Jan 4, 2022):
Just out of curiosity, how was this issue "solved"? Because I fear that this issue will keep cropping up, until a permanent solution is found, like enabling the Debian backports repo, or switching the Jellyfin container image back to Ubuntu, and including a repo like ppa:kisak/kisa-mesa.
@Shadowghost commented on GitHub (Jan 4, 2022):
This issue was fixed by moving to bullseye as base image for the docker images. It includes the required version of mesa.
@viggy96 commented on GitHub (Jan 4, 2022):
Will bullseye-backports be added, so that Mesa doesn't fall too far behind in the future? And will the appropriate backports repo be added to future Jellyfin container image releases, when it's rebased onto the lastest Debian stable image in the future?
@Protektor-Desura commented on GitHub (Jan 6, 2022):
It would be far better to use a base of Ubuntu but for some reason they are totally opposed to it so I will continue to do my own thing instead so that I have a working solution and up to date solution at all time.
@viggy96 commented on GitHub (Jan 7, 2022):
@Protektor-Desura I agree it would be a better solution to switch to an Ubuntu base image. Then I would include Valve's Mesa PPA, ppa:kisak/turtle.
But Debian backports repos seem like an okay solution IMO, since it looks like they're not too far behind.
@viggy96 commented on GitHub (Jan 7, 2022):
As it stands now, this issue is going to keep cropping up, until it's fixed properly.