Kind of curious to see how everyone is doing on various Synology NAS with the now public release of 1.40.0.7998?
Seems like a pretty significant update and just want to see how everyone is getting along with this new version on their Synology NAS?
I’m a DS920+ user. Interested to hear from others how it’s all going.
not great, have playback errors since then ,never happened before, can’t rollback 
Which model NAS do you have and exactly what kind of errors?
920+, random , but rare playback errors
You can rollback to the previous 1.32.8 if you follow normal synology downgrade procedure Once at 1.32.8, you can then continue to previous versions
As alternative, you can use one of the previous database backup files (in the Databases directory) and, after downgrading the package, but before restarting, copy the backup to be the active. ( i have a tool which will help with that )
@ChuckPa - can you send me or link me the tool for that, please? If I’ve got a safe and easy easy way to rollback, I’ll update and start testing 1.40.x and then make sure to post threads/logs if I can replicate/uncover any bugs!
Same here,getting playback errors on synology DS1520+
can I get the link for 1.32.8, or can I downgrade to 1.32.1.6999. That one is stable for me
A quick question about your amazing tool @ChuckPa : are the vacuuming/cleaning operations different from the ones you can run through the Troubleshooting section in the Plex app settings?
(clearly, the repairs etc are not provided through the Plex app, but I was wondering about these specific two options…)
The operations I perform in the tool occur when PMS is stopped.
All the operations you perform through the Plex apps require PMS to be up & running normally.
Because PMS is stopped and the databases are 100% closed & idle, I can operate at the base SQLite level which is below the database schema level PMS operates at.
Regarding the VACUUM operation.
Vacuum only repacks the DB file. This is equivalent to the a partial defrag of a HDD where all the files are moved to the start of the HDD
Table records are not reordered / made contiguous.
In my tool,
With ‘repair’, you end up ‘dropping’ any/all bad records (the damage). You end up with a database which is valid --AT THE SQLITE level–.
It can’t fix schema damage because the tool makes no attempt to understand what PMS is doing with the data (only PMS knows)
Seems to be working fine for me, but the Apple TV app is almost useless. Will play my pre-roll video fine, but the movies never start. Just get spinning wheel for a minute or two, then goes back to Play screen. If I try 3 more times, the movie (or maybe select Play in original format) the movie might play. If I play on IOS or my Mac or my pc, movies play fine every time so it must be the AppleTV app.
Thanks a million for clarifying @ChuckPa . This makes perfect sense.
Upon examining the shell script, I already understood the benefits of the repair operation.
The only thing that made me a but uncomfortable is that in order to run the script under Synology DSM 7, I have to set myself as a root user, which gets me nervous… I guess I can also create another script that removes me from the root users once done.
In any case, thanks for the tool! I wasn’t aware of its existence and it’s a great new addition to my toolset 
Is this issue with AppleTV new for you under 1.40.x and worked fine on versions prior to 1.40.x?
Also, which AppleTV model are you using?
I would very much love for the script to run non-privileged as SystemInternalUser PlexMediaServer but DSM does not allow this.
I already had Plex running as a non-privileged username but Synology took it to a whole new leel.
Given it’s still just Linux underneath, You could customize certain things but Synology would balk pretty loudly.
In the script, you’ll find that everything is already locked down and very specifc.
While the script does support multiple hosts, once it detect DSM 6 or DSM 7 there is no deviation allowed from where the databases are and what can be done.
It’s very tight. while it runs as sudo privilege (a DSM 7 requirement due to super-strict apparmor settings, it puts everything back to as it belongs.
( You can find the stat, chown and chmod commands which perform this)
Playback was an issue with Apple TV before 1.40.x, but now it seems to happen all the time, where before was not all the time, or was fixed by using “play original quality” and it was fine. Since the update to 1.40 it seems to happen every time?
Apple TV 4K. tvOS 17.3
Sadly the player is constantly crashing.
Plex server version 1.40.0.7998-7000
NAS: DS118 DSM 7.2.1-69057 Update 3 (latest)
I am not the least bit worried about your script. Since it’s a shell script (and that the source is on GitHub), I had the leisure to look at it in details (and it’s well annotated on top of everything).
I just don’t like to leave my account setup to be able to run as root in case I do stupid things and touch things I shouldn’t be touching (or in case my account gets hacked and someone else uses it for nefarious purposes). As I was saying, I could simply remove me from the sudoers list
Which player is crashing? AppleTV, web player? Is the player causing the server to crash/halt or does client player just crash?
Hi, I’m using the Plex app in W11. The app doesn’t crash, only the player does. In many cases I also lose progress (video starts from the beginning or from the last stopping point before crash). Thank you
I use the Mac Plex app and it doesn’t really crash: it jut sometimes stops playing with a warning and I have to go back one level to resume playing again. I use the PMS on a Synology NAS running DMS 7 but people have reported similar issues with a number of different platforms.
