Luke 40082 Posted May 5, 2020 Posted May 5, 2020 Hi there, did you follow our hardware acceleration setup guide? https://support.emby.media/support/solutions/articles/44001160148-hardware-acceleration-overview
rutgerputter 0 Posted May 5, 2020 Posted May 5, 2020 Hi there, did you follow our hardware acceleration setup guide? https://support.emby.media/support/solutions/articles/44001160148-hardware-acceleration-overview Yes I did, many times. I installed the correct drivers and when using Jellyfin I can just use VAAPI pointed to /dev/dri/renderD128 and it works. When I check under the advanced transcoding tab in Emby, the list of GPU's stays empty.
Luke 40082 Posted May 5, 2020 Posted May 5, 2020 Yes I did, many times. I installed the correct drivers and when using Jellyfin I can just use VAAPI pointed to /dev/dri/renderD128 and it works. When I check under the advanced transcoding tab in Emby, the list of GPU's stays empty. Please attach the emby server log as well. Thanks.
rutgerputter 0 Posted May 5, 2020 Posted May 5, 2020 Here are the logs after a fresh restart. Thanks for the fast reply embyserver.txt hardware_detection-63724319244.txt
rutgerputter 0 Posted May 6, 2020 Posted May 6, 2020 So... I've found something: When I use the console with "ffdetect vaencdec" It shows me the "Failed to initialize VA /dev/dri/renderD128. Error -1" error. Then, after I set then ENV variable: export LIBVA_DRIVERS_PATH=/usr/lib/x86_64-linux-gnu/dri:/usr/lib64/dri:/usr/lib/dri Then it works and shows me the correct devices. I'm trying to set this path at the docker startup now, maybe it yields some results
rutgerputter 0 Posted May 6, 2020 Posted May 6, 2020 I was just able to change this behaviour and it works! Sorry to bother you. But maybe a request for the official Emby docker image? Include the mesa-va-drivers package and maybe vainfo for troubleshooting? This would help all those people with AMD APU's out there a lot . I'm willing to test for you if you want.
Luke 40082 Posted July 6, 2020 Posted July 6, 2020 On 5/6/2020 at 3:03 AM, rutgerputter said: I was just able to change this behaviour and it works! Sorry to bother you. But maybe a request for the official Emby docker image? Include the mesa-va-drivers package and maybe vainfo for troubleshooting? This would help all those people with AMD APU's out there a lot . I'm willing to test for you if you want. Thanks for the feedback ! Yes I'm sure this can be improved in future updates.
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