halexh Posted January 12, 2023 Share Posted January 12, 2023 Hi, Just started using unraid for the first time about a week ago and it has been great. Got the *arr suite of software setup, along with my downloaders, and now trying to configure jellyfin to utilize quiksync within my i5-12600k on my ASUS TUF GAMING Z690-PLUS WIFI D4 motherboard. I am utilizing binhex's jellyfin container. Within the setup of the container in unraid, I have added the following to the extra parameters section: --device /dev/dri/renderD128:/dev/dri/renderD128 --device /dev/dri/card0:/dev/dri/card0 I can obviously see this within the Jellyfin container's shell. I have also installed intel_top_gpu as a means of confirming the transcoding is actually utilizing the iGPU. This is what I see when running that, obviously no load since its not being utilized. intel-gpu-top: Intel Alderlake_s (Gen12) @ /dev/dri/card0 - 0/ 0 MHz; 100% RC6; 0.00/ 6.66 W; 0 irqs/s ENGINES BUSY MI_SEMA MI_WAIT Render/3D 0.00% | | 0% 0% Blitter 0.00% | | 0% 0% Video 0.00% | | 0% 0% VideoEnhance 0.00% | | 0% 0% PID NAME Render/3D Blitter Video VideoEnhance If I attempt to utilize either VAAPI or Intel Quicksync in the Transcoding settings of Jellyfin, I am met with the following when attempting to play something: Quote Playback Error This client isn't compatible with the media and the server isn't sending a compatible media format. When I select VAAPI, it correctly defaults to /dev/dri/renderD128 Lastly, just for the sake of conforming with all the other instructions I have found. I created /boot/config/modprob.d/i915.conf (because it didnt exist) and added "blacklist i915" to it. Probably pointless, as I believe this only exists to ignore pre-existing drivers in favor of whats in /dev/dri/ ? Anyways, looking for advice on what I am missing. Thanks! Quote Link to comment
robine Posted January 29, 2023 Share Posted January 29, 2023 Hi, I got Jellyfin working with my Intel i5-13500 by simply adding "--device=/dev/dri" to Extra Parameters. In Jellyfin I selected Intel Quicksync and it works as it should. I have the official Jellyfin Docker image, but I don't think that should make a difference. I hope I can help you. 1 Quote Link to comment
mArBLe Posted April 28, 2023 Share Posted April 28, 2023 @robine Did you need to add modprobe i915 to the Go file? Did you need to set any specific permissions to the /dev/dri folder? I have the exact same CPU as you but cannot get Jellyfin use the Intel iGPU. Quote Link to comment
quietwalker Posted May 2, 2023 Share Posted May 2, 2023 Do you have any news on this? I'm having the same issue and I'm still struggling to make it works Quote Link to comment
mArBLe Posted May 3, 2023 Share Posted May 3, 2023 I finally got this working, simply by switching to the official Jellyfin Docker container. The reason for the switch was that I read somewhere that the official container uses Debian, whereas the other well known Jellyfin containers (linuxserver.io, hotio, etc.) uses Ubuntu. This made me think that some device drivers might actually be present in Debian but not in Ubuntu, for my particular hardware (Intel QuickSync via an i5-13500 CPU). As soon as I replaced my old linuxserver.io container with the official one, I only needed to add "--device=/dev/dri" to the Extra Parameters section when creating the container. After this, hardware transcoding worked straight away after enabling it in the Jellyfin control panel. Do note that I did add a line with modprobe i915 into the Go file when trying to get HW transcoding to work with the linuxserver.io and hotio containers, so this line is still in my Go file. I have not tried removing it to see if the official container still works, so you might as well try the official container without changing the Go file. If it does not work, then just change the Go file (please let us know if this is necessary or not). If you need instructions on how to edit the Go file, you can follow the below: You can edit the Go file easily by opening a terminal window directly via the Unraid GUI In the terminal window, type the command: nano /boot/config/go Add the following line at the bottom of the Go file modprobe i915 When you are done, press Ctrl + X, followed by Enter to confirm the file name, to save the file. Then restart the computer. Quote Link to comment
quietwalker Posted May 3, 2023 Share Posted May 3, 2023 @mArBLe I really appreciate your instructions. I will try and I will let you know Quote Link to comment
quietwalker Posted May 3, 2023 Share Posted May 3, 2023 @mArBLe It works!!! Thanks you so much Quote Link to comment
mArBLe Posted May 3, 2023 Share Posted May 3, 2023 @quietwalker Excellent! You are welcome. Did you need to add the modprobe i915 to the Go file or did it work without that? Quote Link to comment
Camo200sx Posted May 13, 2023 Share Posted May 13, 2023 Just to others out there that find this. Have been battling with the binhex version and couldn't get it to work so tried the official. All is well without adding anything to the go file . Am using a 12400 Quote Link to comment
cloudyhome Posted May 15, 2023 Share Posted May 15, 2023 quick feedback: switched to the official jellyfin docker as proposed. Did not change anything with the go file, just installed intel-gpu-top, added the parameter to the jellyfin docker and selected quicksync for hardware decoding. Works for intel 12500 Read this from the intel-gpu-top app information: "This plugin adds the tool 'intel_gpu_top' to your unRAID server and also enables your Intel iGPU from the installation of this plugin on, so no editis to the 'go' file or creation of other files are necessary." So it seems with installing the app from the app store, the go file is already updated, no manual update needed. Thanks for pointing this out, really helped me out Quote Link to comment
Derek_ Posted May 29, 2023 Share Posted May 29, 2023 Hmm.. when you changed to the official Docker, did you have to re-do all of your metadata stuff? I spent a while changing show ratings to suit my kids more appropriately. Quote Link to comment
DevanteWeary Posted July 26, 2023 Share Posted July 26, 2023 On 5/28/2023 at 9:56 PM, Derek_ said: Hmm.. when you changed to the official Docker, did you have to re-do all of your metadata stuff? I spent a while changing show ratings to suit my kids more appropriately. Hey did you ever figure it out? I'm in the same situation and would hate to redo everything ha Quote Link to comment
Derek_ Posted July 27, 2023 Share Posted July 27, 2023 Hiya. I procrastinate bad. So i haven't tried. A friend of mine suggested installing the new one and copying the database across. I don't know how to do that in a Docker and he didn't know if it'd work, so i had a quick look and i found this - but as i say, i haven't tried anything yet. https://jellyfin.org/docs/general/administration/migrate/ Quote Link to comment
LanceM26 Posted December 18, 2023 Share Posted December 18, 2023 On 5/3/2023 at 2:29 AM, quietwalker said: @mArBLe It works!!! Thanks you so much How do you get this output? Quote Link to comment
wayner Posted December 27, 2023 Share Posted December 27, 2023 There is talk in this thread about the "official" Jellyfin docker. Where is that? When I look in apps in unRAID I see the binhex, linuxserver, and hotio dockers. But I don't see an official one. Quote Link to comment
quietwalker Posted December 28, 2023 Share Posted December 28, 2023 On 12/18/2023 at 9:58 PM, LanceM26 said: How do you get this output? using intel-gpu-top Quote Link to comment
quietwalker Posted December 28, 2023 Share Posted December 28, 2023 (edited) 10 hours ago, wayner said: There is talk in this thread about the "official" Jellyfin docker. Where is that? When I look in apps in unRAID I see the binhex, linuxserver, and hotio dockers. But I don't see an official one. The template for the official one was removed recently because the maintainer of the template wasn't able anymore to maintain it anymore. I guess you can just select one of the template available in the App Center and just use the official docker image in the field "Repository" (it is jellyfin/jellyfin ). Of course you should adapt the container internal paths Edited December 28, 2023 by quietwalker 1 Quote Link to comment
mich2k Posted January 12 Share Posted January 12 On 12/28/2023 at 10:04 AM, quietwalker said: The template for the official one was removed recently because the maintainer of the template wasn't able anymore to maintain it anymore. I guess you can just select one of the template available in the App Center and just use the official docker image in the field "Repository" (it is jellyfin/jellyfin ). Of course you should adapt the container internal paths Facing same issue now, tried editing the repository url from the linuxserver with no success, tried installing the intel igpu plugin with no success too May you share the official template? Since seems you all did solve with that and we have no reference Thanks Quote Link to comment
mich2k Posted January 12 Share Posted January 12 There is the bbergle/jellyfin that states This uses the offical Jellyfin container. This official container should help more people with hardware transcoding since this is a Debian base image instead of ubuntu to me transcoding does not work anyways, just wanted to flag that there is already a template using the official image Quote Link to comment
quietwalker Posted January 12 Share Posted January 12 4 hours ago, mich2k said: May you share the official template? sure, if it may help you. 4 hours ago, mich2k said: tried installing the intel igpu plugin with no success too In alternative you can install GPU Statistic plugin (this is the package URL: https://raw.githubusercontent.com/b3rs3rk/gpustat-unraid/master/gpustat.plg) 3 hours ago, mich2k said: to me transcoding does not work anyways have you added the following in the Extra Parameters setting of Jellyfin container (you have to enable the advanced view)? --device=/dev/dri If you have done it, check in the host and into the docker container (with docker exec -it <container name> bash or using the Unraid interface to open a terminal session into the container) if that device is available. jellyfin-template.xml 1 Quote Link to comment
BBergle Posted January 14 Share Posted January 14 (edited) On 1/12/2024 at 8:07 AM, mich2k said: There is the bbergle/jellyfin that states This uses the offical Jellyfin container. This official container should help more people with hardware transcoding since this is a Debian base image instead of ubuntu to me transcoding does not work anyways, just wanted to flag that there is already a template using the official image Yes, I added the template because I read this thread and saw that the official container was removed. After adding --device=/dev/dri, transcoding with the intel iGPU worked first try. Edited January 14 by BBergle 1 Quote Link to comment
mich2k Posted January 20 Share Posted January 20 On 1/14/2024 at 6:45 AM, BBergle said: Yes, I added the template because I read this thread and saw that the official container was removed. After adding --device=/dev/dri, transcoding with the intel iGPU worked first try. thank you for reaching out, actually I was having two issues: templates not using official image AND I had to enable the Low power HuC/GuC due my processor type Thank you for the template :) Quote Link to comment
antonispgs Posted January 23 Share Posted January 23 Wait, HW acceleration with QSV option is not working for me on i5 13500 using the hotio jellyfin? I am just setting things up so I cannot play any files at the moment. Just to avoid confusion, is adding --device=/dev/dri in the hotio container extra parameters enough? Quote Link to comment
maullah Posted January 26 Share Posted January 26 I've just set up my Jellyfin using the "bbergle/jellyfin" and transcoding appears to be working. ASRock motherboard and Intel 12600K. Unraid 6.12.6 I think the comments in the posts above about using the official Jellyfin image is correct. I added --device=/dev/dri in to Extra parameters and also added a path for transcode to /dev/shm to use some RAM for transcoding. I can see iGPU is active on GPU Statistics plugin or when I type intel_gpu_top in the terminal. I left the network option to host (not bridge or custom network) as I was having some issues connecting my android devices. I am not sure what was the trouble but I can reach the server if Jellyfin container network is set to Host! I hope the above comments are helpful for other noobs like me trying to get Transcoding to work. Quote Link to comment
LanceM26 Posted February 15 Share Posted February 15 On 1/25/2024 at 4:49 PM, maullah said: I've just set up my Jellyfin using the "bbergle/jellyfin" and transcoding appears to be working. ASRock motherboard and Intel 12600K. Unraid 6.12.6 I think the comments in the posts above about using the official Jellyfin image is correct. I added --device=/dev/dri in to Extra parameters and also added a path for transcode to /dev/shm to use some RAM for transcoding. I can see iGPU is active on GPU Statistics plugin or when I type intel_gpu_top in the terminal. I left the network option to host (not bridge or custom network) as I was having some issues connecting my android devices. I am not sure what was the trouble but I can reach the server if Jellyfin container network is set to Host! I hope the above comments are helpful for other noobs like me trying to get Transcoding to work. I am able to get it to work on this docker app as well. But it doesn't work with my reverse proxy for some reason. The binhex one works over reverse proxy. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.