As of late I’m tired of fire fighting problems with Plex. It’s just getting to unpredicatable and complex for its own good.
A simple process of changing ones password should not result in being unable to login to my own frickin ‘paid for’ local plex server. Spent hours trying the hack of removing settings from Preferences.xml to no avail. My only option it would seem is to reinstall Plex from scratch and set up user accounts all over again and then authenticate them.
Secondly Plex is becoming problematic for remote users, fragmented client versions that all seem to vary in appearance now across various platforms and seem to constantly run into security issues. The simplicity and reliabilty have gone.
Changing passwords should not break your local Plex install period!!
Its problems like this that should not exist, yet it seams to have been an issue for years now.
I’ve been running emby along side plex for a month now and found its much more oriented around serving your own media. Just like plex used to be!
A big things for me is being able to use it while my internet is down, trakt synchronisation and good library management which Emby is better just because Plex’s focus is elsewhere right now.
The only thing I’m missing right now is HDR support. I’ve started using Infuse as it is the best play for ATV and iOS devices and they are working on direct Emby support. Once that is done I can look at if I should move from plex and donate my £ elsewhere.
I was running Emby up until a week ago, I like it and its options to theme but I’ve since switched to using a simpler Kodi set up as an alternative to Plex for when Plex isn’t working.
Im looking at changing to Emby as well, because Plex wont fix the problems that prevent the hard drives from hibernating on a synology nas. From what I read Emby works with hard drive hibernation.
Allowing drives that serve media to hibernate is a bad idea. Servers should not hibernate or sleep and neither should the drives attached to them. It saves very little in power and may actually increase wear and tear on the drives and computers involved. Failures most often occur during power up/down or spin up/down cycles.
However each to their own and there are many other good reasons to move away from Plex.
You will find much of the same advice about hibernation/sleep on the Emby forums.
Except for the reduced life of the drive caused by power cycles and spin ups and downs. And the inconvenience of having to wait, albeit for a fairly short time, while the drive gets up to speed so it can serve the files. Also the amount of power saved is very tiny.
I think most modern drives do spin down on their own and they’re so fast no-one even notices, but sleeping a drive is RIGHT OUT here in Juicetown. I catch one sleeping on the job and it’s FIRED!
lol
I’ve even got my database on a Local HDD (5400 too) - there may be a bit of lag time on a spin-up, but if there is I’m not seeing enough of it to matter to me.
Perhaps if you only have one drive in the NAS it doesnt make much difference, but when there are 9 drives depending on the models its at least 50 watts per hour saved.
That “may” be true but I believe that “feature” can be and should be turned off by the drive’s software and in the OS settings.
There have been tremendous advancements in electronic, bearing and other technologies involved in drives over the years but the last time I looked at detailed drive statistics I saw that there was a strong correlation between spin up/spin down cycles and failures.
I just see no real reason to allow drives to spin down or sleep. It just does not save enough to justify the increased hardware failure possibilities.
There are no specific settings for any of my WD drives regarding ‘Spin Down’.
All I got is ‘Sleep’ and that’s not allowed.
If they’re spinning down - super.
If they’re not - super.
I can tell ya these WD 8TB externals are ice cold normally - but do get slightly warm when something’s coming on or off - so all things being equal - I’d say they’re spinning down.
