Current version 1.32.7.7571, on a 1019+, installed normally, works perfectly. There’s nothing special you need to do. Reinstall without docker, current version.
Thank you checking it in a few
Have a workaround for all GeminiLake CPUs.
We figured out the problem and what needs to be corrected.
Problem and solution space are now well defined.
Details here:
1.32.7.7571 still uses software transcoding on my DS1019+. This beta update did not fix my problem. I wish I knew what was different between your NAS and mine…
I’m confused. This is for a standard linux system. Is this applicable for my issue?
For you (on Synology),
-
Target directory is
PlexMediaServer/AppData/PlexMediaServer/Cache/va-dri-linux-x86_64
-
Install and use the Synology Text Editor to add the setting to Preferences.xml
Now Plex won’t load. I think it’s core dumping. Trying to locate the log for that.
PlexMediaServer/AppData/Plex Media Server
Right-Click Logs
→ Compress to Logs.zip
I bet you have a typo in Preferences.xml
(It gets TOTALLY STUPID when there’s an error – OR – Permissions are wrong)
Preferences.xml must be owned by PlexMediaServer:PlexMediaServer
The VaapiDriver=“i965” was already in the xml, by adding it w/o looking, it just simply died due to invalid XML. I should have checked, but I assumed since I didn’t ready to check that it doesn’t already exist, that it must be a new entry.
Adding the driver worked. My system prior to the update had (and still does) iHD_drv_video.so which is a symlink to /var/packages/PlexMediaServer/shares/PlexMediaServer/AppData/Plex Media Server/Drivers/imd-115-linux-x86_64/dri/iHD_drv_video.so
I wonder if my issue was because my Preferences.xml already had the VaapiDriver entry and the driver was missing?
T H A N K Y O U ! ! !
Now I can watch TV on my 1080p bedroom TV again.
You will indeed have iHD_drv_video.so. (Intel Media Driver)
Now you have two. IMD and i965
W E L C O M E ! ! !
You must have had things customized beyond out of the box before hand. I have never needed to do anything. Or you aren’t on a 1019+. BTW those instructions aren’t even for the 1019+, it’s apollolake.
ALL:
To be clear to everyone:
-
The ApolloLake CPUs were fixed by a permanent code change as of 1.32.5.7210
and do not require customization. Changing the driver is optional/ -
The customization I provided here will work with BOTH CPU families: J3xxx and J4xxx. Both are i965-capable.
-
For the time being. it’s a workaround until we implement the permanent code changes we need. Until today, while the problem was well known, the specifics were not well defined. Now. they are.

You must have had things customized beyond out of the box before hand. I have never needed to do anything. Or you aren’t on a 1019+. BTW those instructions aren’t even for the 1019+, it’s apollolake.
No, but I have been on the beta channel forever. I am a professional programmer, but I am hands-off when I end my day job, and have no interest in tinkering anymore. After 30 years, I’m burned out and just want to be a regular user.
I learned more about Plex on the Synology over this short venture than I ever cared to learn.
I’m just glad it’s working now.
Haha
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.