***GUIDE*** Plex Hardware Acceleration using Intel Quick Sync

[mmz06]

3 hours ago, drogg said:

So we don't need to run your script anymore (which worked wonders btw) and can instead just follow the new docker image?

Actually, the old script doing compilation eats CPU and takes long time to execute, at least in my environment, but it has the nice ability to be really adapted to Docker in Unraid, so it actually doesn't break anything (hopefully), and so can be used still.

 

The new script on the other hand, is much faster as no requiring compilation, and the GPU driver is officially supported by Intel, so by many aspect it's providing a better solution. But it's not fully adapted to Docker GUI in Unraid, and brakes the fancy container update process, so it requires a manual process for each upgrade of the LSIO Plex container

 

This is the full formal upgrade process by using this script:

 docker build --pull -t linuxserver/plex:opencl https://github.com/linuxserver/docker-plex.git#opencl

Then from Unraid Docker tab, switch to ADVANCED VIEW mode with the little switch on the top right.

And then click on "force update" for the Plex container.

 

At the end you can choose which solution suits best your needs !

😉

[Andiroo2]

What's the long term solution here?  Is it an update in the Unraid core, or simply an updated Plex container (or both)?  For now, the set of commands requiring compilation works perfectly for me, but I have to run them when I update the Plex container (I think).  In the future, will the new container handle this?

[mmz06]

I believe the best is to ask for it in the thread of the Plex container you are using.

For the LSIO one:

I actually totally forgot to ask them, and LSIO team may even not be aware of the need for many to fix this issue...

Edited December 17, 2020 by mmz06

[mmz06]

Hello,

 

It seems LSIO updated its Plex container which now includes up-to-date intel drivers, working with the last Plex version with HW transcoding and HDR tone mapping support.

If you previously used my 1st script, you can remove it and update Plex container, if you used the one which requires to create an intermediate image, just edit the container configuration, and remove ":opencl" at the end of "Repository" keeping only "linuxserver/plex", then click on apply.

It should download properly everything again and put you back in the original track.

This may leave you with 2 orphan images visible in the docker tab, which can be removed from the advanced view.

 

[Mbur371189]

On 12/10/2020 at 6:32 AM, Jbail804 said:

I am able to get this to work. Thank you for the instruction. I am having one issue I need help with. After modifying the "GO" file I hit control X and Y to save it, but when I exit the terminal, it gives me a warning that if I exit my changes might not be saved. Sure enough when I go back into the "GO" file, the script is not at the bottom. It's not that big of a deal to go back in and add the script after each reboot, but I was wondering what I am doing wrong when exiting the terminal? I am very new at this. 

I'm having the same issue

[lotetreemedia]

10 hours ago, Mbur371189 said:

I'm having the same issue

I think this has been discussed above and might be a permissions thing but try:

sudo nano /boot/config/go

 

[tmor2]

Hi. Thanks for posting detailed guide.

I have i-8700 with ASUS B360-I

 

I could not get hw to work.

My Bios: iGPU is enabled

terminal commands in UNRAID execute correctly.

edited Plex container and added Drive with mapping

Name: /dev/dri

Value:/dev/dri

 

Transcoding doesn't show (hw)

 

Also tried

Name: /dev/dri

Value:/dev/dri/     (note ending forward slash which was auto added, since I picked the folder from a dropdown list)

 

doesn't work.

 

Also tried

Name: /dev/dri/

Value:/dev/dri/ 

 

doesn't work.

 

Any help?

[Hoopster]

29 minutes ago, tmor2 said:

edited Plex container and added Drive with mapping

You have Plex Pass and have enabled hardware acceleration in Plex server, correct? I assume so since it is mentioned in the guide. but we just need to verify this.

 

I use the Extra Parameters method, but, the device method should also work.

 

Edited January 17, 2021 by Hoopster

[tmor2]

10 hours ago, Hoopster said:

You have Plex Pass and have enabled hardware acceleration in Plex server, correct? I assume so since it is mentioned in the guide. but we just need to verify this.

 

I use the Extra Parameters method, but, the device method should also work.

 

 

Ops. I don't have Plexpass. I'll get one though.

Edited January 17, 2021 by tmor2

[DingHo]

On 1/17/2021 at 3:10 PM, tmor2 said:

 

Ops. I don't have Plexpass. I'll get one though.

@tmor2 Did this fix it?  I have the same CPU as you, and I'm considering to move it to my unraid tower.  Any chance you could confirm if you can get HW x265 4k HDR --> 1080p SDR with tone mapping encoding to work with the iGPU?  Very much appreciated.

[tmor2]

On 1/20/2021 at 10:23 PM, DingHo said:

@tmor2 Did this fix it?  I have the same CPU as you, and I'm considering to move it to my unraid tower.  Any chance you could confirm if you can get HW x265 4k HDR --> 1080p SDR with tone mapping encoding to work with the iGPU?  Very much appreciated.

I haven't gotten Plex Pass yet, so I cannot confirm it works for Plex.

I did add the path for HW acceleration driver for Jellyfin docker, but it is still transcoding without HWA. Maybe Jellyfin doesn't support HWA?

[DingHo]

8 hours ago, tmor2 said:

I haven't gotten Plex Pass yet, so I cannot confirm it works for Plex.

I did add the path for HW acceleration driver for Jellyfin docker, but it is still transcoding without HWA. Maybe Jellyfin doesn't support HWA?

@tmor2 I can confirm HW accel does work when you get the plex pass.  I've got your exact setting above, and it works great.  However I'm still on on old i5-3570k so I'm really curious about the 4k encoding on the newer processor.  Let us know when you can.

[mmz06]

15 minutes ago, DingHo said:

@tmor2 I can confirm HW accel does work when you get the plex pass.  I've got your exact setting above, and it works great.  However I'm still on on old i5-3570k so I'm really curious about the 4k encoding on the newer processor.  Let us know when you can.

 

I can transcode in hardware 5 4K HDR streams concurrently on my i5-9600k with embedded UHD630, as I mentioned a few weeks ago:

 

[gustomucho]

On 1/5/2021 at 7:26 PM, Mbur371189 said:

I'm having the same issue

 I am also having this issue.

 

I also tried "sudo nano /boot/config/go", but it doesn't save either.

 

Have you figured this out?

[murk00]

This works for my system, but anytime I have to shutdown my server I have to edit the go file and reenter the modprob info. Any ideas on reboot why this gets removed?

[gustomucho]

To anyone who is having trouble with the modified go file saving the changes after a system restart, you may be making the same stupid mistake as me. When you edit your go file via the terminal with "nano /boot/config/go", you then add the line "modprobe i915", and the you press CTRL+X to save, followed by Y to accept. According to the first post of this thread, "And you should be golden!"

If you are new to all this, like me, you have probably just closed the window afterwards thinking all was good. After many unsuccessful attempts, I finally noticed that after following these steps, a line of text appears in the bottom of the command window the terminal :

At this point, you just need to press Enter and the file will be saved. And then you can close the window...

This must seem pretty basic for most of you, but hey...you gotta start somewhere

 

Edited February 26, 2021 by gustomucho

[Hoopster]

25 minutes ago, gustomucho said:

To anyone who is having trouble with the modified go file

Or you could just export your flash drive (secure or private if there are other users who have access to your server on the LAN) and edit it with Notepad or Notepad++ on Windows.  No dealing with nano, vi or other command line driven Linux text editors.

 

That's what I do.

[Zendikar]

Gah; I can't get mine working! I can see the listing in /dev/dri -> ls, did a modprobe i915, added the /dev/dri to devices in the settings. When I used "docker exec -it plex ls -lh /dev/dri" in the console, it returns both my iGPU as well as my PCIE GPU: 

Still, it doesn't work off the iGPU and instead continues to software transcode. I made sure to as well establish the transcoding is enabled in Plex.

 

For context, I'm using the ASRock C236 WSI paired with the i7-7700K, with my 3060ti thrown into the PCIe slot.

I assume that the iGPU does exist and is usable, since I went ahead and installed Handbrake and added the /dev/dri to its devices. It does show it as an option in the Video Encoder: 

Edited February 28, 2021 by Zendikar

[alitech]

Is there a guide for Ryzen with Quadro GPU for Plex docker? I have plex docker and a quadro p600 and no idea on how to get it to transcode with the quadro. Is there a guide I can follow somewhere?

 

[Hoopster]

4 hours ago, alitech said:

Is there a guide for Ryzen with Quadro GPU for Plex docker?

 

[Arte83]

hi, sorry in advance for my english, i hope to be able to explain myself well.
I have a problem with plex transcoding.
my build is:

 

Unraid 6.9.0 (i had the same problem with 6.8)

linuxserver/plex

ASUS Prime H310I-PLUS R2.0 
I3-9100
Crucial RAM CT16G4DFRA266 16GB DDR4 2666

I believe I have configured everything correctly as follows:

 

The appdata use cache pool.

 

But it doesn't work, i see the trascode in plex

 

 

the stream never starts and seems just to buffer up to 8 seconds.

 

 

I tried to look for the plex logs a bit (tail -f PlexMediaServer.log | grep Transcode
), below a printscreen

 

 

Anyone have any suggestions?

Edited March 2, 2021 by Arte83
missing info

[AL_Fonce]

Hi, I have the exact same issue on my build.

It used to work but for some reasons, plex is not using my igpu anymore but is rather using the cpu so every time i try to transcode my cpu takes a huge hit and plex goes in buffering. 

 

If anyone has an idea....

[jumpy]

Thank you for this, worked perfectly. MSI Z490-A Pro and i3 10100.

[craigr]

This guide by lotetreemedia has been very helpful for me, but starting with unRAID 6.9.x the steps that are unraid specific should be done differently because unRAID has implemented GPU drivers.  Everything lotetreemedia says to do in PLEX is still valid, but activating the driver is different.  If you have lines in your "go" file you should remove them and change unRAID as follows:

 

https://wiki.unraid.net/Unraid_OS_6.9.0#GPU_Driver_Integration

 

Quote

Unraid OS now includes selected in-tree GPU drivers: ast (Aspeed), i915 (Intel), amdgpu and radeon (AMD).  For backward compatibility, these drivers are blacklisted by default via corresponding conf files in /etc/modprobe.d:

/etc/modprobe.d/ast.conf

/etc/modprobe.d/i915.conf

/etc/modprobe.d/amdgpu.conf

/etc/modprobe.d/radeon.conf

 

Each of these files has a single line that blacklists the driver, preventing it from being loaded by the Linux kernel.

It is possible to override the settings in these files by creating a custom conf file in the config/modprobe.d directory on your USB flash boot device.  For example, to un-blacklist the amdgpu driver create an empty file by typing this command in a Terminal session:

touch /boot/config/modprobe.d/amdgpu.conf

This only needs to be done once, it does not need to be added to your go script.

In 6.9.1, if your go script contains a modprobe command for your GPU and/or a command to fix the permissions on /dev/dri, you should remove them:

modprobe amdgpu 
chmod -R 777 /dev/dri

In 6.9.0, if the docker you are using is unable to access the GPU, add/keep this line to your go script:

 

chmod -R 777 
/dev/dri

but remove this one:

modprobe amdgpu

 

 

After completing lotetreemedia 's steps in the PLEX docker, all I had to do to get QuickSync working with 6.9.1 was remove the lines from my "go" file and create a file in \flash\config\modprobe.d\i915.conf.  The i915.conf file is just empty.

 

craigr

Edited March 15, 2021 by craigr

[AL_Fonce]

On 3/15/2021 at 5:20 PM, craigr said:

This guide by lotetreemedia has been very helpful for me, but starting with unRAID 6.9.x the steps that are unraid specific should be done differently because unRAID has implemented GPU drivers.  Everything lotetreemedia says to do in PLEX is still valid, but activating the driver is different.  If you have lines in your "go" file you should remove them and change unRAID as follows:

 

https://wiki.unraid.net/Unraid_OS_6.9.0#GPU_Driver_Integration

 

 

After completing lotetreemedia 's steps in the PLEX docker, all I had to do to get QuickSync working with 6.9.1 was remove the lines from my "go" file and create a file in \flash\config\modprobe.d\i915.conf.  The i915.conf file is just empty.

 

craigr

 

Thanks a lot @Craig, I should have payed more attention to the release note. After completing the steps you linked all is back to normal.

 

Thanks again!