I've attempted to pass the iGPU though to plex by "add another Path, Port, Variable, Label, or Device" and using /dev/dri. I can select the iGPU in transcode settings in the Plex webUI, but it always transcodes using my CPU. Am I doing something wrong? I've asked Claude and it's saying there is an incompatibility issue, but I tend to not trust AI very much.

Do you have a plex pass subscription? I think its required for hardware transcoding. Im asking as hw transcoding worked out of the box for me. No configuration needed. Im running plex in docker though.

1 hour ago, Arie said:

Do you have a plex pass subscription? I think its required for hardware transcoding. Im asking as hw transcoding worked out of the box for me. No configuration needed. Im running plex in docker though.

Yes I do. Bought it many years ago. What CPU/Motherboard do you have? I also run plex in docker.

Edited April 24Apr 24 by Ogbassist

I use a 12600K with Asrock Z790 motherboard. Running the Plex container with network type 'Host', and it automagically works. No need to pass through anything (isnt that VM only?) Maybe do a fresh container install (and reboot the server afterwards so any residual passthrough settings are canceled? Also, what kind of file are you using to test it?

Some people have had to downgrade their plex containers lately as transcode broke for some platforms in recent updates.

Edited April 24Apr 24 by Kilrah

^^^ This

Also be sure to do your testing on a real streaming device (such as AppleTV 4K, Roku, etc) and not with the web browser, and turn off sub titles. Web browser is known to cause issues when switching transcoding values, and sub titles will (in many cases) result in CPU transcoding.

10 hours ago, ConnerVT said:

^^^ This

Also be sure to do your testing on a real streaming device (such as AppleTV 4K, Roku, etc) and not with the web browser, and turn off sub titles. Web browser is known to cause issues when switching transcoding values, and sub titles will (in many cases) result in CPU transcoding.

I'm fairly sure the web browser always uses transcoding, but I was using the Xbox One. That's where 99% of my media is played from. I never use subtitles unless forced subs are needed which are sitting next to the media file.

Edited April 24Apr 24 by Ogbassist

11 hours ago, Arie said:

I use a 12600K with Asrock Z790 motherboard. Running the Plex container with network type 'Host', and it automagically works. No need to pass through anything (isnt that VM only?) Maybe do a fresh container install (and reboot the server afterwards so any residual passthrough settings are canceled? Also, what kind of file are you using to test it?

I had the z790 and I7-12700k before and it worked fine with that hardware, not so much with the new stuff.

11 hours ago, Kilrah said:

Some people have had to downgrade their plex containers lately as transcode broke for some platforms in recent updates.

I'll check that out, thank you. Claude was saying the libs used for transcoding were incompatible with the new xe architecture.

11 hours ago, Arie said:

I use a 12600K with Asrock Z790 motherboard. Running the Plex container with network type 'Host', and it automagically works. No need to pass through anything (isnt that VM only?) Maybe do a fresh container install (and reboot the server afterwards so any residual passthrough settings are canceled? Also, what kind of file are you using to test it?

passthrough might have been the wrong word. Yeah you need to pass a device through to your VM instance. When you do that with a VM, its locked to that VM and nothing else can even see it exists anymore. I was referring to just letting the device know where the hardware I want to use is located aka /dev/dri

8 hours ago, Ogbassist said:

passthrough might have been the wrong word. Yeah you need to pass a device through to your VM instance. When you do that with a VM, its locked to that VM and nothing else can even see it exists anymore. I was referring to just letting the device know where the hardware I want to use is located aka /dev/dri

Yes i was wondering how plex could see the igpu if you had bound it on startup. Let us know if/how you find a solution. Im actually looking to upgrade to a 270k plus so would be interested to learn if this is a persistent issue.

Edited April 25Apr 25 by Arie

14 hours ago, Ogbassist said:

passthrough might have been the wrong word. Yeah you need to pass a device through to your VM instance. When you do that with a VM, its locked to that VM and nothing else can even see it exists anymore. I was referring to just letting the device know where the hardware I want to use is located aka /dev/dri

At the Docker, use "Host" - thats all you need.

And you ned "also" to select the iGPU at the plex settings...

Edited April 26Apr 26 by Zonediver

6 hours ago, Arie said:

Yes i was wondering how plex could see the igpu if you had bound it on startup. Let us know if/how you find a solution. Im actually looking to upgrade to a 270k plus so would be interested to learn if this is a persistent issue.

So after rolling back to version 1.43.0.10492, its working. I guess the new version just broke it.

54 minutes ago, Zonediver said:

At the Docker, use "Host" - thats all you need.

And you ned "also" to select the iGP at the plex settings...

Plex was already in "host" mode and I did select the iGPU in transcoder settings :D its ok I fixed it, just had to roll back to a previous version.