Keep your eye on the prize. Google and Mozilla aren’t even in the same area code of shit. Firefox is the obvious answer.

Napster

Not a boat! Not a family vacation! Gasp! An… RV!?!?? SOMEONE THINK OF THE RIGHTSHOLDERS!

Woah really?? I am actually…

https://lemmy.world/comment/11720780

Thanks, really appreciate the thoughtful response. I have an intel n100 NUC actually on the network. It used to be the jellyfin machine but has shifted to other duties. I probably should have tried to throw that in and reconfigure things but I just went with the OSMC Vero box which should tick all the necessary hardware boxes to at least free that from being the problem. Bonus: I get to add the pi4 back to the homelab stack.

FWIW I have jellyfin as well already, it’s also on the machine serving the nfs shares. I would expect streaming over lan to always be a lighter load then sending a transcoding request through the internet and back to the machine four feet away, but I could be wrong. I am always curious though what people are using as jellyfin clients for their TVs. How are you actually getting jellyfin into your living room? I had hoped to use a dedicated pi4, and I’ve already gone down the route of trying to boot to a light desktop with an auto loading chrome kiosk window to my jellyfin server, but those results were less than ideal too.

I don’t, super helpful. So I’m guessing this is a pi bottleneck. Just ordered the Vera V so we’ll see! Fingers crossed for happy toddler.

Thanks! Super helpful data point. I don’t have the same buffering issues streaming the same video to my desktop over nfs, so I’m leaning towards it being a pi4 bottleneck. Just plopped down for a Vera V so fingers crossed that’s the issue.

❤️

Right? The absolute gall.

Oh brilliant. Thanks. Yes. This only tends to happen on larger files, 5gb mkvs or multi audio track deals etc. I was also concerned it’s just a pi4 bottleneck, but that’s fixable too with more hardware. Just need to figure out what to get.

Right. The architecture we’re talking about right now is a NFS hosted share going to a Kodi instance, not a jellyfin instance sharing to Kodi. Kodi does not transcode. It handles things similarly to VLC afaik.

It’s not doing hardware transcoding afaik. This is the equivalent of running VLC, right? It’s kodi we’re not talking about jellyfin transcoding.

Appreciate the solicited technical advice, less so the unsolicited parenting advice, thanks! You’ll be shocked to hear that hyperbole exists, I’m sure. I’m just trying to watch the Aristocats with the kiddo without them wondering why the screen stops mid song, stranger.

No no transcoding happening on kodi, it’s just playing it straight over the lan. That said I do have jellyfin set up on a machine that can handle transcoding for a number of clients. I gave considered switching to Kodi +Jellyfin and seeing if that’s better.

No it doesn’t. It implies exactly what the other poster said. Convicts were let out of prison to fight. What a weird hill for you to die on.

This is going to blow your mind but it’s a joke, and not even a mean spirited one. We all started with training wheels, nothing wrong with that.

Portainer is just training wheels for people that haven’t learned to manage their own containers yet.

Any idea if it’s self host able if it’s open source?