Failed to open hybrid_drv_video.so

Server Version#: Version 1.17.0.1709
Player Version#: all

Hello,
While doing some sanity checking and verification how the new transcoder reacts, I found the following error in my syslog everytime a HW transcode starts:
failed to open /data/jenkins/conan_build/290854760/conan/.conan/data/libva/2.4.0-1/plex/stable/package/81a2df5e16044d97d1b088b0e6c9598b5b17f233/lib/dri/hybrid_drv_video.so

It seems my box is doing HW transcoding, so I am not sure what this error is and what influence it has on the transcodings. My CPU is not as loaded as before when I didn’t have HW trancoding enabled, so that’s why I assume HW transcoding is working.

Does somebody know how to fix this? I checked around on Google, but could not find any real answers:

  • /dev/dri has the correct permissions and the plex user is added to the correct group
  • intel driver has been installed (although not sure if that is even needed)
  • found here one thread where it could be related to the CPU-type and source codec, but I am not sure about that.

CPU is Intel Atom x5-Z8350 on a Debian Buster.

Hope somebody can enlighten me.
Thanks in advance.

May I see the DEBUG (not VERBOSE), log ZIP file please of a recreation?

Thanks

PS: Per Intel, the CPU does not have Quick Sync Video. How is HW transcoding being accomplished? nVidia GPU card?

Hello,

According to this link https://chuckscoolreviews.blogspot.com/2019/05/plex-hardware-transcoding-performance.html and the last link in the comments, it does have HW transcoding.
My tests and the tests from Chuck (not you, the other Chuck), it indeed works fine.

Now, due to a very stupid human error where I formatted the disk containing the Plex Library, my Plex is gone for the moment…
So, I will have to restart from scratch and will provide you the logs ASAP.

Maybe you can verify the HW transcoding part on this CPU in the meantime.

Thanks

To be more clear on my fist post: I already had HW acceleration enabled and working before installing 1.17.
Some time ago, I did not yet have it enabled (due to plexuser not having access to /dev/dri etc…), which is the time I am refering to with the high cpu load.

1.17 is not different for me then 1.16 in terms of having HW accel enabled or not. The error I have was also there on 1.16 (something I was about verifying when playing around too much and wiping everything…)

THere are a few things missing from that CoolReview:

  1. PMS version
  2. How it got enabled previously.

Without that information, it can’t be replicated and repeated.

I’m Looking at the CPU specs from Intel. There’s nothing so unless this is a ‘cool trick’, it’s undocumented and unknown.

Intel is not marketing it as Quick Sync for some reason, but the Z8000 series supports hardware decode and encode of a fairly impressive list of codecs. From the data sheet:

• Intel's 8th generation (Gen 8) LP graphics and media encode/decode engine.
• Supports 3D rendering, media compositing and video encoding.
• Graphics Burst enabled through energy counters.
• Supports DX*11.1, OpenGL 4.3, OGL ES 3.0, OpenCL 1.2.
• 4x anti-aliasing.
• Full HW acceleration for decode of H.263, MPEG4, H.264, H.265 (HEVC), VP8, VP9, MVC, MPEG2, VC1, JPEG.
• Full HW acceleration for encode of H.264, H.263, VP8, MVC, JPEG.
• Supports Content protection using PAVP2.0, HDCP 1.4 (wired)/2.2 (wireless) and Media Vault DRM.

I’ve also tested that hardware decode/encode of H.264 works for PMS on my Windows 10 test system which is powered by an Atom X5-Z8300 (Intel Compute Stick). I only mention this to confirm that this chipset does indeed have the necessary silicon to support it. I cannot however attest to its functioning under Linux.

Windows isn’t Linux. That’s entirely different. I cannot help decode / map any of that to Linux.

It’s highly likely it does work under windows because of the much larger customer base than Linux (the money is there to finance the development and support).

Linux is free (for now). What we have, quality wise, is pretty darn good and in some ways, better than Windows.

My setup is pretty simple actually.

Let me know what you need. My Plex is up and running again.

While I don’t have an answer for you as to why the message is generated to syslog, I can confirm it occurs on the test system I just stood up as well. My system is Atom X5-Z8300-based, and is now running Ubuntu 18.04.03. This was a fresh install using PMS 1.17.0.1709.

Hardware transcoding (both encode and decode) works as expected. I tested by playing a 1080p movie at 480p on a browser running on a second system (Safari 13.0.1, if it matters). It played back with no stuttering or buffering.

The message was only generated at the start of playback on my system (7 times); it did not occur afterwards. Perhaps it is simply PMS probing the system to see what hardware/software is installed to see if hardware-based transcoding is supported. If you perform a forum search for “jenkins” several threads of discussion are returned, so this is not that uncommon. The context for some is transcoding is not working; for others it is transcoding is working.

I totally agree with you and I have the same syptoms as you have. Transcoding works based on CPU usage, HW mentioning in Tautulli and in the Plex app.
Message occurs a couple of times at start of transcode.

While I agree it is not uncommon based on the other threads on this forum, I could not find a final answer in there, hence the reason I made this thread. :wink:

This error is a red hearing and will be resolved in an upcoming PMS release. It does not have any effect on HW transcoding working or not. if HW transcoding is not working when it should be, it will be related to something else, which should be visible in the Plex Media Server.log at the time of transcoding :slight_smile:

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.