I have the J5005 CPU (ASRock J5005-ITX) in a Debian Buster OS and using the LSIO Plex docker container (latest beta: 1.18.8.2527). I’m having the same exact pixelated issue when I use hw transcoding. Any idea how to fix this? It’s very frsutrating to say the least.
@chrisallen @ChuckPa Here’s my Plex Media Server logs that show HW and non-HW transcodings:
your logs don’t show any FFMPEG activity except from when the butler ran.
@kevindd992002 Please provide logs that cover your use of HW transcoding 
Ohh. That’s weird. Let me recreate the problem again and give you a fresh set of PMS logs.
Here you go:
So I force transcoded “Elementary - S4 E16 - Hounded” and it shows in this log file.
@ChuckPa @chrisallen Have you guys had the chance to look at the PMS logs I uploaded recently?
I resolved my problems with enforcing subtitle burning on the firetv app and the android app.
Not yet, I am based in New Zealand and currently helping getting my family sorted while we are in Lockdown due to COVID-19, I’ll try and look over the next few days. One think you can do as a test, is to delete the iHD.so driver as some others have done. Let me know if that resolves the issue for you?
i got the same issue on a J4105
deleting iHD_Drv_video.io fixed the issue for me but i have to do it after every update
docker exec -it /bin/bash -c “cd /usr/lib/plexmediaserver/lib/dri && rm -f iHD_drv_video.so”
and restart the container
Ok, so just delete the driver on the container and not on the host, right? You can use custom startup scripts with LSIO containers.
@chrisallen deleting the iHD_Drv_video.io driver file as @dominik.b suggested did fix the problem for me. What’s next?
Hi @kevindd992002 you can use the following URL the force the i965 driver to be used instead of the iHD
You will need to change PMS_IP to the IP of your NAS, and change MY_TOKEN to your PMS token. (https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/)
http://PMS_IP:32400/:/prefs/set?VaapiDriver=i965&X-Plex-Token=MY_TOKEN
(Just copy and paste that into your browser and press enter)
But then that would only be for the web client, right? I rarely use the web client as I use the Plex client in either Nvidia Shield TV or LG TV.
No this would set a hidden preference on your server which will change what driver is used for all HW TRANSCODING
Oh ok, I see. And this preference is saved in a config file in Plex so it will survive a container update, correct?
What is the reason behind why the iHD driver breaking things? And will this be fixed automatically in future Plex releases?
So I recreated the container to bring back the iHD driver and used the API call you posted above to force the transcoder to use the i965 Vaapi driver and it’s not working. Right after I used the URL, I tried transcoding and the issue is there. I thought I needed to restart the container for it to take effect but it was still like that. So far, the only workaround that’s working is deleting the iHD driver from the container.
Any thoughts?
I have had a different experience. I tried it and it worked perfect and even survived an update!
Ok, that’s really weird. Are you using LSIO’s docker container too?
I’m sure I have the correct PMS server IP and Plex Token in that URL. Which preference file should I be looking at anyway to make sure that the API call took effect?
Not using plex in docker. Sorry I didn’t specify. I followed the instructions to get my token and placed it in the url as well as the ip to my plex server. Pasted it all into a browser and pressed enter and it just worked.
Would you mind checking your Preferences.xml for me and see if the change is visible on that file?
