Plex has overhauled its apps from the ground up to make them easier to navigate. The teams says it will be able to roll out new features faster as well.
For me, Plex works great on my Synology while Jellyfin is completely unusable - video payback simply crashes. Running Jellyfin on my desktop machine gets it to work, but it takes over 24 hours to scan my media library and doesn’t automatically add new media when I add new files.
Yep. I’m guessing it insists on transcoding the video but doesn’t have the horsepower. Plex either has a superior transcoder or detects it doesn’t need to transcode it.
I think the transcode part is decided by the client, but in the Jellyfin server admin you can control if a client can request a transcode (which may not be actually needed - and if you know what client they are running it’s probably easier to decide). This could just be client setting though, because I know on Jellyfin you can change the “backend” in the client that it tries to use and can make the difference on things like x265/HVEC playing back or not.
Hmm, I’m not sure that’s the case here. I tried this with two different browsers (Firefox & Chrome) on two different computers, plus the native client on an Android phone, Android TV, and Android tablet, with various server settings - none of them worked.
Yeah, sounds like the more mature Plex backend might just be better for your use case. But just because I’m curious are you running Jellyfin as an app or in docker? And is your Synology Intel based or AMD, as the latter will only do software transcoding and probably easily overwhelm a NAS CPU.
For me, Plex works great on my Synology while Jellyfin is completely unusable - video payback simply crashes. Running Jellyfin on my desktop machine gets it to work, but it takes over 24 hours to scan my media library and doesn’t automatically add new media when I add new files.
So the server part runs worse from your NAS? That seems odd but I have never run either from a NAS so no idea how to help. =(
Yep. I’m guessing it insists on transcoding the video but doesn’t have the horsepower. Plex either has a superior transcoder or detects it doesn’t need to transcode it.
I think the transcode part is decided by the client, but in the Jellyfin server admin you can control if a client can request a transcode (which may not be actually needed - and if you know what client they are running it’s probably easier to decide). This could just be client setting though, because I know on Jellyfin you can change the “backend” in the client that it tries to use and can make the difference on things like x265/HVEC playing back or not.
Hmm, I’m not sure that’s the case here. I tried this with two different browsers (Firefox & Chrome) on two different computers, plus the native client on an Android phone, Android TV, and Android tablet, with various server settings - none of them worked.
Yeah, sounds like the more mature Plex backend might just be better for your use case. But just because I’m curious are you running Jellyfin as an app or in docker? And is your Synology Intel based or AMD, as the latter will only do software transcoding and probably easily overwhelm a NAS CPU.
Running as a socket container - I don’t think there’s a native Synology package for Jellyfin. This is an Intel Synology.