btw intel QSV on iGPUs is actually crazy, you can put a little intel cpu from like 12th gen and it’ll decode and encode most content for you perfectly fine, unless you’re extremely picky about tone mapping and color space (idk in that case, i don’t have super strenuous content requirements lol)
the arc cards are even better, but not needing an entire GPU for decoding/encoding is SO nice for smaller homelabs.
both, probably.
jellyfin is quite literally seamless in this regard, the only thing that wont work is metadata scraping (which if like me you run a yt archive, can be relatively frequent, but often isn’t even a huge problem) I only notice network outages when other shit breaks lmao.
Hardware acceleration still kind of sucks. You can get it to work, but the Jellyfin port of ffmpeg doesn’t work anywhere near as well as Plex’s.
pretty much just works for me on intel QSV. as long as you have drivers and hardware support it seems perfectly fine. Maybe plex has a cleaner implementation? Not sure, never used it.
Public network support is finicky. This is hard to quantify, but I’ve been on several remote networks where my Jellyfin connection dropped in and out and Plex did not. I suspect this is due to the Plex Relay service making up for bad routes between my house and the network.
depending on your network configuration, and routing of the network, this is most likely to be plex relays, this wouldn’t be a jellyfin issue, it would be a plex feature. You could easily fix this with a relay VPN server or something like that. (you probably shouldn’t publicly expose services these days anyway.)
i only wish jellyfin would add chapter titles and hover cards (maybe thats in the new thumbs now? I haven’t yet migrated because lazy lmao)
and that they fix the weird UI shenanigans from it’s emby days. Some QOL shit would be nice, auto sorting so that its not manually default to the stupidest setting ever. and the other usual shit.
I’m still having issues with my client freezing on playback of high bitrate video (like heavy 4K content) but transcoding down fixes that, im not sure what causes that, something gets caught up i guess, a refresh fixes it though.
there’s finamp. and i think jellyfin is just running a sonic server? Not sure, but that’s basically what it is under the hood, so.
i’ve never used plex or benchmarked it, so it’s possible that it does, i wonder if anybody else has reproduced that behavior, i know a lot of people do plex/jellyfin benchmarks these days. Be surprised if that hadn’t yet happened. It shouldn’t be any faster or slower if you’re using the exact same transcoding settings, it’s all limited by the hardware physically, so it’s possible it was that. Could theoretically be bad drivers, or bad support i guess, but that would be a separate issue.
definitely a possibility, but then again there are several ways of solving this problem, in homelab universal manners, so maybe they should offer a more generic service instead.