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.
a text editor that has a tutor because it’s been around for so long and it’s had so many years to establish itself with an outside control interface that’s quite literally about as optimal as it can be. Vim basically allows you to never move your hands away from the homerow keys, even when navigating and doing bulk edits. The sheer amount of gained speed and productivity you get from this combined with the amount of times you’ll have to deal with text editing throughout your life is probably going to outweight any potential learned annoyances.
idk man, vims pretty chill, it even has a tutor in it already, what more could you want?
welp, time to go buy intel… wait.
uhm, well you can’t primarily because android is a hot mess (quick note: this is mostly me ranting about the hell that android is for no fucking reason)
First of all, android only supports MDNS since android 12 and newer, MANY years after the standard was even finalized and put into use. (like a concerning amount) And yes, you can technically use that networking on a per app level (since android 6 or 8 i think), if it’s implemented, but most apps don’t because they’re android apps. And the ones that do are basically useless (very cool thanks android)
Ignoring this, let’s say that you have a samba server, and have a local DNS config setup to get around the MDNS bullshit. Oops, funny story, android doesn’t natively support SMB shares, because apparently they aren’t real and don’t fucking exist. Now to be clear, most file managers do actually support SMB, the problem here is that those are often shit, and only supported in the actual file manager itself. If you wanted to per se, mount a samba share on android on the FS level, it is either impossible, or REQUIRES ROOT ACCESS.
Man it’s a good thing rooting is easy, and not super convoluted, or risks bricking your phone in the event that it’s designed like utter shit and cannot recover from being flashed incorrectly. (to be clear, i don’t know shit about rooting, because it’s a fucking disaster, and i might be misrepresenting it here, but only rooting, everything else is accurate)
so basically, cool story, the only option here that you have is using apps that are specifically designed to implement their own file transfer functionalities and protocols. There is one redeeming factor to this, and it’s the fact that rsync exists, and that it isn’t shit, but rsync isn’t samba, so eat shit android. Rest in piss you disaster of an OS.
And here’s the reason why layman should not: they’re much more likely to make that one wrong move and suffer irrecoverable data loss than some faceless corporation selling their data.
and yet americans still drive cars.
I don’t disagree, but you just have to be aware that you can fuck shit up. And if you do, that’s not my problem, or anybody elses at the end of the day.
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.