I’m being told that once the next version of Unraid is released with the newest linux kernel that plex still won’t work with the arc a380 due to plex packaging itself with an outdated intel media driver. I’m a little confused by this but guess it has to do with what ffmpeg is using. How difficult would it be for plex to update it’s codec/drivers used? Would there be a means to force plex to use the new intel drivers once supported in unraid?
1 Like
I purchased an ARC A380 card to supplement/replace the transcoding of my Ryzen’s APU.
The Intel based card basically does nothing in my system and only transcodes about 2% (guessing) of all transcodes!! The remaining transcodes fall back to SW transcoding.
When will Plex acknowledge their commitment they made to supporting Intel hardware transcodes with a statement of support, no support or future support for this product?
No one from Plex can answer? I’m sitting in my a380 card hoping to toss it in my current system.
On my Windows 11 PC I can get the A380 to be utilized by Plex Media Server even running in Normal mode.
When PMS is run as a service, only h264 connect is transcoded.
This is a limitation of Windows. There is nothing Plex or nVidia can do about it.
The only options you have is to run Plex Server regularly or to switch to Linux.
I’m pretty sure there was no change. It’s always been like that.
I am running my own server as a Windows service as well. I’d jump at the opportunity to use HW transcoding, believe me.
Then why can h264 use HW transcode when run as a service, but other codecs can not? Doesn’t Plex’s ffmpeg implementation do the HW and SW transcoding for all codecs? I don’t see why it would be different for different codecs.
It cannot.
transcode = Decode + Encode
As a system service, you might be able to use the H.264 Encode abilities, but never the Decode abilities.
The reason is that Decoding is handled by some system library (DirectX , I think) which is not available to system services, but only to apps which are run in a user context.
Encoding on the other hand is using a different API which doesn’t have that limitation, AFAIR.
So, when transcoding e.g. HEVC to H.264, the main load is decoding the HEVC video, while encoding to H.264 is comparably low in computational demand.
As far as getting the A380 to work (even with 6.2 kernel) on Linux/docker I am thinking that they need to bundle in the newest iHD_drv_video.so with their application (does not use the system one I do not think). On windows HW decoding works with the A380…
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
