![]() |
SOLVED: Can't get hardware transcoding to work - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: SOLVED: Can't get hardware transcoding to work (/t-solved-can-t-get-hardware-transcoding-to-work) |
Can't get hardware transcoding to work - Fardenco - 2025-05-14 Hi, I'm trying to get hardware transcoding to work on my server but I don't know why it won't work. My Jellyfin server is running in a docker container. Jellyfin Server version is 10.10.7 The CPU is an Intel Pentium Gold 8505 I added the user to the "render" group, and added the group number and render devices in my docker.compose, following the documentation. But I have a feeling that the issue is still related to user group or at least to user. I'm using Portainer. If I open a container console with user "root", running the "/usr/lib/jellyfin-ffmpeg/vainfo" command, returns a list of profile. But if I do the same thing whith a console with user "1000", then the command returns an error. Because of this, I guess that the issue is not with the transcoding settings but maybe with the container settings ? When trying to play a movie with transcoding, the error shown in the logs is Code: Failed to set value 'vaapi=va:,vendor_id=0x8086,driver=iHD' for option 'init_hw_device': Generic error in an external library Here is my docker.compose : Code: services: Thank you for your help RE: Can't get hardware transcoding to work - bitmap - 2025-05-15 Double check you followed the steps in the HWA guide. There's more than just passing the device into the docker container. https://jellyfin.org/docs/general/post-install/transcoding/hardware-acceleration/intel The verification steps can help you identify any issues. It might be a driver problem based on that error message. RE: Can't get hardware transcoding to work - Fardenco - 2025-05-15 I believe I followed all the steps for Intel GPU on Linux with virtualization I found what the issue was My changes to the docker compose file were not used, because I was recreating the container from Portainer without previously updating the stack, it seems that the changes to the compose file are only taken into account after updating the stack. Because of that, the "add_group" option in my compose file was not used, I saw this when I used the "id" command in the container console and the render group was not present. Everything is working great now, thank you for your help |