Hey,
I’m on vacation but keep seeing ApolloLake mentioned, what about Geminilake? I don’t believe this issue is fixed for those either without manually putting the driver in the Cache folder under Plex settings.
Several people tell me around this problem, that hi hasn’t with the last docker version…in the same 920+ this could be a coincidence? Or docker is more stable?
@ChuckPa
Here are some logs from me testing on Version 1.32.4.7195 with my DS920+
Test #1: Playing LG Colors of Journey HDR 4K Demo (no driver in Cache folder and no i965 mentioned in Preferences.xml (CPU shot to the moon) Plex Media Server Logs_2023-06-16_10-01-18.zip (4.2 MB)
Anyone who has been a sysadmin on any type of server will tell you about dependencies.
Docker removes that word from system administration.
New version of slapjack? Spin it up in Docker, it won’t break the other tools on the server…
New version of Plex? Spin it up in Docker.
When you go the native route you’re always running into new libraries, that other tools don’t work with, then you have to update those tools, then you have to update to libc++ 17.0 because something needs it, then you just broke 3 other tools that use libc++ 11.0……
Docker removes all those layers of sysadmining that are despised, with a little bit of up front setup.
Yes, I understand the game changer about dependencies, specially for developers with several library versions etc…but, I think the best performance always be on native applications, because docker is in some way an extra layer…what I can’t understand about this issue, if we’re talking about the same binaries, why works on docker an don’t on native in the same machine??
From what I understand in the thread, ALL the new versions of PMS break hardware encoding on the DS920+ (and other Synology NAS devices).
Native or Docker container, if it’s past version .6999 it’s broken.
I personally just happen to run PMS in a Docker container on my 920+ because I also have pi-hole, sonarr, radarr, nzbget, etc. running in containers as well.
Plex brings all its dependencies with it in every SPK file with exception of codecs and drivers.
Codecs and Drivers are downloaded and stored in the PlexMediaServer shared folder the first time PMS starts up. As versions update, these are automatically updated in sync with the SPK files.
I’ve been working with @ChuckPa. I loaded an alpha (pre-QA) version of PMS 1.32.5 on my DS918+, which has the Celeron J3455 CPU.
Here’s some initial results:
Jellyfish 80 Mbps H.264 HD & 120 Mbps HEVC UHD: Hardware transcoding engaged. Playback was smooth, with no buffering.
LG New York UHD HDR: Hardware transcoding & tonemapping engaged. Colors looked good. Playback was smooth with no buffering.
LG Colors of Journey UHD HDR: Hardware transcoding & tonemapping engaged. Colors looked good. Playback did buffer a few times. However, this video is 60 FPS, so it is pushing the limits of the J3455.
Clients were Android mobile on a Pixel 6a, configured to transcode to 1080p, 8 Mbps, and Plex for Windows, forcing a transcode to 1080p, 10 Mbps.
I loaded the alpha on my system a couple of hours ago and ran the tests. Chuck asked that I drop an update to the thread. Wanted to let you know things are progressing.
