Jump to content


Photo

Empty Hardware Encoders/Decoders Lists - ffdetect error


  • Please log in to reply
8 replies to this topic

#1 CorpusColossus OFFLINE  

CorpusColossus

    Advanced Member

  • Members
  • 32 posts
  • Local time: 12:38 PM

Posted 03 December 2019 - 12:23 AM

I noticed recently that there are no items listed under "Preferred Hardware Decoders/Encoders" anymore, where I had many options earlier this year. I thought this might have been caused by the update to 4.3.x, but rolling back as far as 4.1.x doesn't seem to solve the issue.

 

I have a Radeon RX 570 GPU which I was using for hardware decoding previously, but it is not working any longer. It is detected by vainfo and you can see I am using Mesa drivers:

$ vainfo
libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Mesa Gallium driver 20.0.0-devel for Radeon RX 570 Series (POLARIS10, DRM 3.23.0, 4.15.0-72-generic, LLVM 9.0.1)
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointVLD
      VAProfileH264ConstrainedBaseline:	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileHEVCMain               :	VAEntrypointVLD
      VAProfileHEVCMain               :	VAEntrypointEncSlice
      VAProfileHEVCMain10             :	VAEntrypointVLD
      VAProfileJPEGBaseline           :	VAEntrypointVLD
      VAProfileNone                   :	VAEntrypointVideoProc

This post describes a similar issue, though when I run the following I get an error regarding libavutil.so.56:

$ /opt/emby-server/bin/ffdetect vaenc
/opt/emby-server/bin/ffdetect: error while loading shared libraries: libavutil.so.56: cannot open shared object file: No such file or directory

Attached is the hardware detection log, which contains the error "Failed to initialize VA /dev/dri/renderD128. Error -1".

 

@softworkz is libavutil.so something that is bundled with Emby's FFmpeg?

Attached Files



#2 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142515 posts
  • Local time: 12:38 PM

Posted 03 December 2019 - 12:31 AM

Hi there, did you follow our hardware acceleration setup guide?



#3 CorpusColossus OFFLINE  

CorpusColossus

    Advanced Member

  • Members
  • 32 posts
  • Local time: 12:38 PM

Posted 03 December 2019 - 12:38 AM

Yes, I have read through that wiki page and the linked pages therein, but there aren't any obvious actions listed anywhere.

 

For example, I had to use these forums to figure out that the "emby" user needs to be added to the "video" group so that it could access /dev/dri/renderD128.



#4 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142515 posts
  • Local time: 12:38 PM

Posted 03 December 2019 - 01:00 AM

What install package are you using?



#5 CorpusColossus OFFLINE  

CorpusColossus

    Advanced Member

  • Members
  • 32 posts
  • Local time: 12:38 PM

Posted 03 December 2019 - 01:14 AM

emby-server-deb_4.3.0.30_amd64.deb



#6 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142515 posts
  • Local time: 12:38 PM

Posted 03 December 2019 - 01:15 AM

Yes, I have read through that wiki page and the linked pages therein, but there aren't any obvious actions listed anywhere.

 

Did you click the Linux link to review the requirements?



#7 CorpusColossus OFFLINE  

CorpusColossus

    Advanced Member

  • Members
  • 32 posts
  • Local time: 12:38 PM

Posted 04 December 2019 - 11:13 PM

For anyone who stumbles across this, there seems to have been a breaking change in the mesa drivers sometime between September 2019 and December 2019 (I use the oibaf PPA). Emby only officially supports the AMD Radeon Software for Linux 18.40. Which in turn is only supported on Ubuntu. I'm using Linux Mint so the installation of this flavor of driver fails. The mesa drivers worked for a time, but that time has ended.



#8 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142515 posts
  • Local time: 12:38 PM

Posted 05 December 2019 - 12:59 AM

That's interesting, thanks for the info !

 

@softworkz might like to know that.



#9 softworkz OFFLINE  

softworkz

    Advanced Member

  • Developers
  • 1894 posts
  • Local time: 06:38 PM

Posted 05 December 2019 - 01:51 AM

That's interesting, thanks for the info !

 

@softworkz might like to know that.

 

Thanks for the info is all I can say to that as well. 

 

@CorpusColossus Maybe you can just use the previous driver where it worked?






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users