This is quasi-beta.
If you need / want HDR, run docker.
Synology does not have any support for anything I need (we knew this)
We’re creating the whole thing for all the NAS platforms. ( it’s a lot of work )
1 Like
It seems that my plex app on fire tv cube has a problem to discover my plex libraries after update my synology with this version. After restart of the fire tv cube it works fine until i close the app and start the app again. it shows me all my libraries on the left but will never shown any content. always the retry dialogue will be shown. and the plex tv and Vod content. same happen on my fire tv stick which i use to stream from remote. but after restart i can access my content the whole day.
using the webpage works always
thats very strange
That is definitely an app problem.
It is apparently able to connect to the server in only certain conditions.
I wish I could help but I don’t have any of that equipment here to begin testing with.
Best I can suggest is: Plex for Android - #374 by romancamelia
1 Like
@noyse See above ^^ ? I edited when I found the link.
1 Like
Is it normal, “Season 1”, “Season 2” etc are in English with new “Plex TV Series” Scanner ? With TvDB or TMDB I have it in french.
And is it possible to show also posters from TvDB with “Plex TV Series” Scanner ? Most of the season posters are missing.
It would be good to be able to edit the links of the trailers, to be able to put a trailer in the language you want, most of them are in English.
And also an issue with TheTVDB rating, when selected it show TMDB rating.
Another thing,
I would ask about it here:
I don’t know much about the new scanner yet. I have been working on DSM 7 and other different developmemt work. Sorry
well I seem to be having my HDR and Dolby Vision working.
I haven’t updated my Main system yet, I was testing it out in a virtual machine.
upgraded it to DSM 7 and Plex seems to be working just fine, HDR videos and Dolby Vision working without transcode (in the beta version and the latest PMS 1.21.3.3988-7000.
I was about to go through with my Main system upgrade but saw your comment about no HDR support.
Can you please elaborate on that ?
Sure, It’s actually quite simple:
The native package (SPK file) does not include the extra runtime libraries to perform tone mapping (HDR → SDR) in hardware.
If you look at normal desktop Linux (Ubuntu/Debian), you see where the installer checks for the two external packages and suggests you install them if not already installed.
We don’t have these files available from the NAS vendors; which isn’t a surprise.
I have been told Engineering is working on building their own versions of the two packages so we can then include them with all the other NAS packages.
When they make those files available to us, we will automatically include them in the package SPK file.
2 Likes
To all DSM 7 Preview Participants.
Plex Media Server 1.21.3.3988-7000
is now available for download.
- Links are in the Preview thread.
- Normal upgrade
- New “Plex TV Series” Scanner is incorporated
- Changes to legacy (Existing) scanner for TheTVDB changes included (PMS 1.21.1.3943)
Existing TV sections may be ‘upgraded’ after changing the agent (advanced tab).
- Change agent
- In the same panel where you EDIT the library section, see “Upgrade Matching”.
Upcoming:
- Download via Plex.tv/downloads
- Handling in the package for rare cases of needing access to Crash Report files.
3 Likes
Fortunately my Plex Media Server migration to DSM7 worked well 2 months ago. But this weekend I got stuck after reorganizing things a bit. In order to change file systems of my 2 volumes in a DS220+ to btrfs I had to shift my data from one volume to the other and in the end reinstall Plex - like many other apps. I did a new install of Plex Media Server but neither with normal installation nor with claim token or address via localhost:9000 I get access to my server.
I always get “access denied to that server” entering my Plex account. How can I reset the connection? Maybe the former packet hasn’t been removed completely? I’m really stuck. Any ideas?
- Plex does not use port 9000. The standard Plex port is 32400
- Have you examined https://app.plex.tv → Settings - Authorized Devices - Server to remove the old server instance ?
- you are right w/ the port 32400 - i know - sorry. anyway - 32400 - the port itself isn’t the problem.
- yep - i deleted the server as authorized device - installed anew - get my “access denied” and find the server-related entry again in the authorized devices-list.
still clueless.
I’m going to ask the basic questions – run the checklist
- Both server and accessing computer using the same Plex.tv account ?
- Both server and accessing computer on the SAME RFC-1918 compliant subnet ?
- Has the server been claimed?
- Is a certificate involved?
- Were the connection requirements of the server set to require Secure connections?
Hi Chuck - checklist
- yes
- yes
- yes - I claimed the token w/ the re-installation of packet PMS_1.21.3.3988… and could verify that my account matched on the token provision page.
And somehow this must have worked - as - when opening http://domain:33400 after installation I’m routed to my acount login where I can choose login option and finally request access - but w/o success. And when I deleted the server as authorized device, it comes back on list after reinstallation w/ the claim token. for me it looks like the initial connect works as designed. - as far as i know, no certificate for the plex server communication service is in place - means - I didn’t install one besides standard installation procedure. Just checked: Certificate should be in place for:
- same like 4. “Where” could the connection requirements of the server be set to require secure connections?
Is there another - additional option - to purge the former server connection from my account besides the deletion of the entry from the “authorized devices list”?
The setting which requries secure is here:
Settings - Server - Network - Show Advanced
Secure connections: Required
When set to “Required”, some unencrypted connections (originating from the Media Server computer) will still be allowed and apps that don’t support secure connections will not be able to connect at all.
sorry - where is the “entrance”? w/i DSM7-settings I see no option for “Server”.
You reference: http://domain:33400
This is your domain name?
Have you tried to open and claim it by http://ip.addr.of.syno:32400/web while on the same network?
PMS will not allow you to claim / reclaim it using a FQDN
it was late yesterday - once more a typo that mislead. 
sorry
the port for my installation is 32400 - whatever i may have stated here - and that works fine.
but w/ the simple last statement about pms not able to claim via fqdn (what i already knew) you made my day.
behavior before was - when i opened http://my_domain:32400 i was routed to “https://app.plex.tv/” with the only option to login and get the access denial.
using http://ip.addr.of.syno:32400/web didn’t work either after reinstall but i didn’t remember the behavior/ error message. therefore i tried some minutes ago and it worked. i could complete the installation (e.g. mount a media-folder) and access the server settings.
i set the public port manually from something like 2??? to 32400 and afterwards could activate remote access. now everything seems to work fine.
as i’m absolutely sure, that access via ip-address didn’t work before (and that there was no typo) question is - what’s the difference?
i come from a plex server running w/ dsm 6.x successfully automatically migrated to dsm 7 and now after two months - moving the shared folders from one volume to each other in order to change the file system from ext4 to btfs and afterwards reinstall the apps.
this didn’t work for plex and synology photos in a proper way. plex didn’t reconnect and wasn’t accessible, synology photo (still) doesn’t provide the pictures in its own default shared folder “photo”. the pics in personal folders are shown btw.
therefore i decided yesterday to restore the photo folder from last weeks backup INCLUDING complete DSM-CONFIGURATION. i didn’t do that before because i didn’t change anything in my dsm config. but this DSM CONFIG RESTORE in the end may have made the difference for plex.
but - to be honest - i have no clue which dsm-config-item should interact while adressing the server instance via ip:port 
for the synology photos issue i opened a bug at synology.
thanks a lot for your support on this topic.
Experiencing issues when upgrading from Plex Media Server - 1.21.1.3906 to Plex Media Server - 1.21.3.3988-7000 using the links provided in the DSM 7.0 preview post.
a) Have uninstalled previous version without removing the files then installed 7000 version (x64).
b) Tried my local path directly which is 192.168.0.220:32400/web/ - failing
c) Double checked that PlexMediaServer has full control over Plex folder
I’m a bit clueless here. Could you perhaps provide a link to the previous build again so I can check if downgrading solves the problem?
Upgrading to the the latest build is a normal “Update” process.
I’m surprised it is giving you issues.
Also, you can forget about the Plex share. We don’t use it anymore.
It’s free for you to use (or delete) as you wish. (this is documented in the Preview thread)
- Uninstall & Keep
- In the Preview thread - immediately below build 3988-7000, you will find 3906-7000. I kept both versions for this reason
