I'm not sure about how this works in kodi but in jellyfin the client might request a different resolution which causes the server to try and reencode the provided file on the fly. In my case my server isn't fast enough for this which leads to constant buffering
this post was submitted on 12 Aug 2024
102 points (85.4% liked)
Selfhosted
40313 readers
139 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Likely, This is it. It transcodes and hence it has to buffer because the server isn't strong enough. Best is to use a gpu like intel a380 as described in jellyfin's doc.
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.
Installing the Jellyfin add on into kodi takes a few minutes. Nothing much to consider, just try it and see if that changes anything.
I have a similar setup (rpi with OSMC, media hosted on file server) and prefer using Jellyfin as the source for all clients, as it keeps track of watched status across everything. It's not perfect, but better than without Jellyfin.
I havent used kodi in a long time, since swapping to jellyfin. I personally found kodi would always buffer sometimes, far more than it should ever need to. With jellyfin, same server, no buffer
load more comments
(1 replies)
Kodi doesn't do any transcoding. It just mounts the NFS share and plays the file.
Leave Kodi behind in 2010 and switch over to Jellyfin for better results.
That's the correct answer.
All that kodi hassle killed my brain. Nowadays I have a jellyfin server and a wifi6 router streams everything to a roku device I bought for 11€. Never saw some buffering again.
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.
Why would your Jellyfin traffic need to go over the Internet if it's on your local network? You should be able to install the Jellyfin app on your smart TV/Roku/etc or use the web client from a computer, point it at the Jellyfin local IP address, and view it over your LAN.
load more comments
(2 replies)
Traffic for a local Jellyfin server should definitely not be going over the internet. Also any reasonably modern client should be able to direct play most media without transcoding.
As for my own Jellyfin setup, one TV has an Nvidia shield plugged in and is using the standard Android TV client. The other is a Samsung smart TV onto which I have side-loaded the Jellyfin Tizen app.
load more comments
(4 replies)
There are dedicated Jellyfin clients but I mainly just use the web client that is part of the server 90% of the time.
load more comments
(4 replies)
EASY KILLER
I DON'T SEE ANY JELLYFIN DISTROS
"JUST ENOUGH OS FOR JELLYFIN?" no
Though jellyfin/emby as the back end works really well
Kodi/LibreELEC is awesome for all the different stuff you can add in
EDIT for typos
You can install it anywhere. You just run the container with you media directories passed though. They have lots of documentation
It is way easier than Kodi
load more comments
(1 replies)
Kodi/LibreELEC + JellyCon add-on works great!
Before you buy anything, put some of the same content that buffers on a USB stick or powered drive and play it directly from the pi4. Also connect via ethernet to your router from another PC and check your dl speed from the NFS share.
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.
I'd lean towards the pi being the problem, but you can test the network throughput with iperf, and would want to test the videos outside of Kodi on the pi, so you could also check top and see what the processing looks like.
If I remember my pi 4 hardware decoding specs correctly, I believe h.264, MPEG 2, and VC1, and some support for HEVC. If I had to guess, you may have some codecs that aren't handled by hardware acceleration, and instead just CPU.
My best rec would be to use either a dedicated stream box (like a fire stick, Nvidia shield, etc) which has better codec support, or pick up like a little Intel n100 based system, which will handle a drastically wider set of codecs with full acceleration support.
Right now I've got a Roku and a Google TV Chromecast, and I've been trying with various environments on an old Lenovo m910q so I can find my favorite fit of UI/distro. The Roku and Chromecast never stutter, and I don't do transcoding for inside the home. Works with 4K HDR HEVC no problem.
Edit: Autocorrect annoyances.
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.
load more comments
(1 replies)
Are you by any chance using flat Ethernet cables? Those are not to spec and are vulnerable to radio noise. Friends don’t let friends buy and use flat Ethernet cables.
Woah really?? I am actually…
Your setup sounds much too complex and misses key information and troubleshooting steps. The flat cables are kind of the cherry on top.
You need to start laying out which devices grab which stuff from where and which cables, switches, routers and panels you are using.
Otherwise people wont be able to help you. A new router isnt going to help you at all.
Example: I run plex on a terra miniserver, stream to my phones and computers over wifi (the server is connected via cat7 wired networking with a tested gigabit connection). I also stream to a libreelec-pi in another room which is also on wifi and has issues sometimes. That is why I‘m gonna wire the connection later this month so that is no issue. I also have an appletv in the livingroom which is connected by wire and has no buffering. There are 3 gigabit switches and a fritz!box also connected but they‘re all gigabit as well: Between PCs and the main router, appletv and the main router and the server and the main router.
load more comments
(2 replies)
Flat cables can be conformant and they still have twisted pairs. Cables just have to meet the physical properties set by the standard.
Sure they might exist but the ones you buy off of That Website never are.
load more comments
(1 replies)
Your router doesn't handle LAN traffic so an upgrade shouldn't make any difference, unless you have multiple VLANs and are passing traffic between them and don't have a Layer 3 switch in use to handle inter-VLAN routing.
I would probably start with an iperf test for download bandwidth to the Pi from the server. If that looks OK then I would benchmark the NFS share for read speed on the Pi, make sure that's not doing something weird.
If that all looks good then I would probably suspect that Kodi either isn't using hardware acceleration properly, or the specific media codec is not supported by the Pi for hardware acceleration.
I gave up on kodi. Jellyfin works better, presumably because it transcodes better.
Haven't used Kodi but am running Jellyfin via the official docker image on a Raspberry Pi 4. Even there transcoding works reasonably well for one user at a time, admittedly didn't try with several users at the same time so far.
Just mentioning the docker image because I used to install it without docker directly via the repository and I never got transcoding to work on the same hardware.
load more comments
(1 replies)
can you run something like iperf3 or openspeedtest between the server and client to prove its a network throughput issue?
do you have a network switch you can add to avoid switching through your router (if it is indeed bad?)
Have you ensured you arent unknowingly using wifi at either end?
That is a complex setup. What's wrong with Jellyfin?
Also doing media streaming from a RPI is not going to work well. Go with a old minipc as they are cheaper anyway
load more comments
(1 replies)
Change the baby for a dog. You're welcome.
Instructions unclear. Baby is now a werewolf and howls loudly when Kodi is buffering.
My bad, I apologize. Put it in the freezer for now and I'll shout out when I have clear instructions in a codeberg repo.
What quality is the content? I have a pi4 running OSMC, kode front end and things are buttery smooth. All content is 1080p or lower as the pi can't handle 4k
Network is a 1gb switch from the mini pc running NFS and homeplugs to get the network from a bedroom to the living room.
Do you experience buffering if you watch on a pc / laptop on VLC via network? This will tell you if it’s network speed related or hardware power related. I would assume the pi is not quite powerful enough. I am using a device called a Vero 4k+ and it works wonderfully. But my network setup sounds similar to yours, I just have an smb share on my pc and I added it as a source in kodi.
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.
load more comments
(4 replies)
To me it looks like you don't have enough power, either on the Pi4 side to decode, or the mini-pc to encode.
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.
load more comments
(5 replies)
Before getting all crazy and changing the setup why don’t you try Wi-Fi. Yes Wi-Fi. Your cable might only be 100mbit and your WiFi may be faster.
Wi-Fi 5 can theoretically transmit data at speeds of up to 3.5 Gbps. And obviously WiFi 6 and 7 are even faster.
I have a similar setup but my nfs server is not a mini pc.
You could try diagnosing if it's the network or if your mini pc is too busy (maybe out of disk i/o?).
If that's too hard, temporarly stop all other programs on the mini pc. Does it help?
Does streaming something from the internet to kodi work without freezes? If it's ok, then network is likely not the issue
Last but not least, does playing the same video from an USB stick work smoothly? If not, maybe the quality is too high or the video is x265
The Pi4 USB controller and network adapter share bandwidth. Do you have any devices on the USB port that could be causing collisions? I really can’t think of anything in that kind of scenario that would cause that sort of issue unless somehow you were using USB for video out…
Kodi on my 2015 Nvidia Shield doesn't stutter for me playing back 30GB+ 4k files on a 1Gb network from an ancient (2012) AMD Athlon TrueNAS box. It could be network related, but you can test this from another machine (laptop, desktop, etc) or by using local playback on the pi. I have cheap network hardware, and have never needed better. All this is to say Kodi mounting NFS shouldn't need much bandwidth or high end gear. Perhaps the issue is on the playback side. Good luck!
Edit: ~~and~~ an
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.
view more: next ›