The Shield 2019 supports Dolby Vision.
Earlier versions support HDR10, but not Dolby Vision.
2 Likes
@ChuckPa Oh i understand, it’s just those first couple of lines genuinely did sound positive for everyone, until the final bit excluding all us Synology/Gemini Lake users
I know. We want to push as fast as we can and get this all working FOR EVERYONE but we did get hit pretty hard internally.
We have to make sure these first steps are solid and reliable.
There was a new build today, I looked through the notes, doesnt look like this issue is fixed there. Can you confirm?
Pick an issue… 
Which one? 
Do you have Docker versions too? I’d love to test it on my DS1019+ (although @mfisherden already reported it to be working for the normal installation).
The docker containers are built separately but you can manually install the DEB file in the Plex Docker container.
The DEB installer supports installing in an existing Plexinc docker container
- Put the DEB file where
/configcan see it docker exec -it Container_name bashcd /configdpkg -i filename.deb
It will install and you’ll be at that version
Thanks. Installing this version worked fine.
Though the results aren’t good. I’ve played an episode and ran into multiple buffer timeouts. What do I have to do to provide logs?
Edit 1:
I just created some logs for @ChuckPa . Here you go.
Plex Media Server Logs_2023-09-19_13-08-16.zip (596.1 KB)
Edit 2:
Gotta say I don’t run into buffer timeouts with this test build as often as in previous versions but it still happens.
1.32.6.7515-873995547 confirmed working HDR to SDR 4k on Xeon(R) W-1350P in docker plexpass container.
note, it does not auto-restart after manual installation within a running container, you need to issue a s6-svc -r /var/run/s6/services/plex/ after dpkg -i ..
I suppose FreeBSD is not expected to support Intel hardware transcoding by now. Is that so?
After installing the new build I simply restarted the PMS docker container. After its restart I checked and saw that the new version was running. This should do too, right?
Synology 1019+ DSM7 64bit - appears all normal, except there’s no desktop or tray icon for Plex anymore, it only shows in Package Manager.
Thanks. Can’t help but think that’s nooooot really the expected behavior or best practice though…
I noticed this last night as well. Went to watch a movie, it would not play at all on Apple TV and buffered every few seconds on Shield Pro 2019.
Also, sorry I should have stated in my first post that I was indeed using docker. (linuxserver image with latest tag).
It’s a mixed bag – to be honest.
Some want it. Some don’t.
The issue starts when a DSM admin allows users to sign into the NAS directly.
(not smart in my opinion as it’s a server machine)
From there, these DSM desktop users suddenly have access to Plex/web.
The question / issue does come down to:
-
How many folks DO and how many DO NOT allow users to sign into DSM directly?
-
How do you want it ?
I will gladly go with whatever the community wants.
I’ve offered this in this 1.32.6.7512 Forum Preview build for precisely this reason.
If the wishes are strongly against, then I will remove it.
( I wish I could setup a poll )
I need version info.
LSIO:latest is not what’s being offered here. They don’t have this yet.
I have Shield Pro 2019 and everything is DirectPlay – no stuttering whatsoever
Given that it’s the ONLY package I have installed that operates this way, I vote remove it, go back to standard. The option is nice, but don’t default to hidden.
I’m trying to figure it out. I know. Mixed bag here.
If I can’t stabilize it, I will pull it.
I want “default = visible” so it’s transparent to everyone until wanted.
The DSM UI code is written as visible:
{
".url": {
"com.plexapp.plexmediaserver": {
"title": "Plex Media Server",
"desc": "Plex Media Server Web App",
"icon": "images/plexmediaserver_{0}.png",
"type": "url",
"protocol": "http",
"port": "32400",
"url": "/web",
"allUsers": true,
"grantPrivilege": "all",
"advanceGrantPrivilege": true
}
}
}
