CorpusColossus 10 Posted December 3, 2019 Share Posted December 3, 2019 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? hardware_detection-63710924479.txt Link to comment Share on other sites More sharing options...
Luke 36879 Posted December 3, 2019 Share Posted December 3, 2019 Hi there, did you follow our hardware acceleration setup guide? Link to comment Share on other sites More sharing options...
CorpusColossus 10 Posted December 3, 2019 Author Share Posted December 3, 2019 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. Link to comment Share on other sites More sharing options...
Luke 36879 Posted December 3, 2019 Share Posted December 3, 2019 What install package are you using? Link to comment Share on other sites More sharing options...
CorpusColossus 10 Posted December 3, 2019 Author Share Posted December 3, 2019 emby-server-deb_4.3.0.30_amd64.deb Link to comment Share on other sites More sharing options...
Luke 36879 Posted December 3, 2019 Share Posted December 3, 2019 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? Link to comment Share on other sites More sharing options...
CorpusColossus 10 Posted December 5, 2019 Author Share Posted December 5, 2019 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. 2 Link to comment Share on other sites More sharing options...
Luke 36879 Posted December 5, 2019 Share Posted December 5, 2019 That's interesting, thanks for the info ! @@softworkz might like to know that. Link to comment Share on other sites More sharing options...
softworkz 3301 Posted December 5, 2019 Share Posted December 5, 2019 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? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now