Otw but after replacing the flat Ethernet cable (no change), and while waiting for the vero I switched to connecting to jellyfin / jellycon via its local address instead of its external one (🤦♂️) and zero buffering silky smooth everything. I don’t understand why but holding my breath for now while I wait for the vero when I can retire this unit at least to the office tv where it doesn’t have the responsibility of always performing for the family.
You know once I expose a service to the internet and get a nice easy to remember url I practically forget that I can still access locally. I should check that out.
We’re a googleless house as much as possible. I did consider going down the chrome cast route but it’s less than ideal on iOS.
It’s really neither much too nor very complex at all. I have a home lab stack of mini PCs and raspberry pi’s in my office hooked up to a switch to my router. Among the stack is an intel nuc with a few attached usb hdd, sharing those drives via NFS and Samba and hosting Jellyfin. The same machine serves jellyfin to my other devices and a few family members over the internet. That machine is more than capable for the task. In order to get that media to the living room I have a raspberry pi 4 running libreelec also hard wired to the Ethernet also to the same switch (running through a cable window in the wall). No, I had not heard of the issues with flat Ethernet cables that are otherwise advertised as cat 7 compatible, because I have (some) of the machines networked with flat Ethernet cables. Those are getting replaced.
For the most part the pi4 libreelec machine handles content fine. But I have a number of multichannel audio, hd not-quite-4k animated movies that do routinely cause buffering issues. It seems most likely upon review and after the comments in this thread that it was a simple bottleneck at the pi4. The same content plays unstuttwring on other more equipped machines on the network. I do think the router is on its way out though and deserves an upgrade but that looks to be an optional next step. I’m replacing the pi as a media machine for now.
Sorry you seem to not be getting it https://lemmy.world/comment/11720780
? Not particularly. I have an intel mini pc hosting jellyfin and a few drives via nfs and samba in one room along with the rest of my homelab. In the living room I need to get that media to the tv so I’m using a pi4 running libreelec atm to connect to those shares.
Woah really?? I am actually…
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.
Using the local address for the jellyfin instance solved things. I have no idea why whatever jellyfin is doing via jellycon is somehow more performant than just streaming via smb or nfs in vanilla kodi but 🤷♂️. Good pull.