3 ms·
> That said, I don't actually like Jellyfin, and I wish it weren't implemented in such a Windows-centric language framework. That's an unfortunate holdover fro
by stryan 5y ago
> That said, I don't actually like Jellyfin, and I wish it weren't implemented in such a Windows-centric language framework.
That's an unfortunate holdover from it's origin as an Emby fork.
> Once I found out that Jellyfin existed, I excitedly spun up an instance and put all my media on it. It can't handle any AVI videos and lags a lot more than my Plex VM with exactly the same specs.
AVI is just a container format and Jellyfin leverages ffmpeg to do most of the actual decoding work, so that sounds like an issue with the VM's ffmpeg. Jellyfin also doesn't enable hardware decoding by default; could be related? I'm not sure what Plex does (for codecs/etc).
- brimble 5y ago> That's an unfortunate holdover from it's origin as an Emby fork. Unfortunate? My initial guess on first contact with the project was that it'd be some Node thing. I was so relieved to see it wasn't. My unkind but honest and built-on-experience assessment is that it's a big part of why it's so not-shitty. C#'s a great choice for a backend language.
- fomine3 5y agoI realized AVI and AV1 is confusing.