2024-01-16, 10:59 PM
(This post was last modified: 2024-01-16, 11:16 PM by Bummerten. Edited 2 times in total.)
Half a year ago, i upgraded to a new jellyfin setup running on an older HP Elitedesk setup. Everything has been working flawlessly, and i love the system, but i have been encountering some random hickups - that im unable to identify.
Let me try to sum it up:
The problem started with very HQ remux files, that had issues with buffering. I could watch 1.5 hours of a movie, and then it would start buffering every 30 seconds. Looking at my setup, i see no unusual activities, no overheating or any hard load on any specific components - huh.
CPU is running at 30% and the Media HDD is maxed out reading and sending the file. It looked like the bandwidth could be too much for my wifi, so i went that direction for troubleshooting. First i tried too test a stream on my internal SSD and not from my media HDD, so rule that out. Same issue happened here (M2 SSD vs Sata HDD)
So i cashed out for a new Wifi 6 router.
This helped alot on the stability of our connection, but not the above issue. It started again at random times. The connection was still too poor. I ended up upgraded to a wired setup to my TV, and now have double the connection: 200-300 mbps.
Still the playback would stop once in a while on high quality streams.
A few weeks passes, i reinstall everything, try to debug - but found absolute nothing wrong. Tested with Emby, Plex and more, but didnt seem to have any issues. This must be some kind of software bug, but im just puzzled.
Fast forward to today, and it struggles to play even a regular 4-8gb 1080p with low bitrate. It will stop at least once every fifteen minutes, and often it starts in the first five minutes of a movie. To get it running again, i just need to rewind a few seconds and press play -> it will not start again by itself, like it would if it was buffering. The logs show nothing informative, and when it notices at all, it only tells me that the Client stopped playback. It happens on both AndroidTV and the official/sideloaded WebOS app, both remotely and on LAN.
Note: Everything plays as direct play, nothing is transcoding.
Specs:
Intel 7500T CPU
32 GB Ram
1 TB m.2 SSD as system drive
3 TB sata HDD for media
Network - Wired (200-300 mbps)
Running on Win 10 (since its not supported in Win11).
Now that i have ruled out bandwidth, somewhat completely, what could be the cause?
The CPU has been and should be more than enough for several simultaneous 4K streams, so i'm thinking software? Either missing drivers, some configurations missings, anything really.
Let me try to sum it up:
The problem started with very HQ remux files, that had issues with buffering. I could watch 1.5 hours of a movie, and then it would start buffering every 30 seconds. Looking at my setup, i see no unusual activities, no overheating or any hard load on any specific components - huh.
CPU is running at 30% and the Media HDD is maxed out reading and sending the file. It looked like the bandwidth could be too much for my wifi, so i went that direction for troubleshooting. First i tried too test a stream on my internal SSD and not from my media HDD, so rule that out. Same issue happened here (M2 SSD vs Sata HDD)
So i cashed out for a new Wifi 6 router.
This helped alot on the stability of our connection, but not the above issue. It started again at random times. The connection was still too poor. I ended up upgraded to a wired setup to my TV, and now have double the connection: 200-300 mbps.
Still the playback would stop once in a while on high quality streams.
A few weeks passes, i reinstall everything, try to debug - but found absolute nothing wrong. Tested with Emby, Plex and more, but didnt seem to have any issues. This must be some kind of software bug, but im just puzzled.
Fast forward to today, and it struggles to play even a regular 4-8gb 1080p with low bitrate. It will stop at least once every fifteen minutes, and often it starts in the first five minutes of a movie. To get it running again, i just need to rewind a few seconds and press play -> it will not start again by itself, like it would if it was buffering. The logs show nothing informative, and when it notices at all, it only tells me that the Client stopped playback. It happens on both AndroidTV and the official/sideloaded WebOS app, both remotely and on LAN.
Note: Everything plays as direct play, nothing is transcoding.
Specs:
Intel 7500T CPU
32 GB Ram
1 TB m.2 SSD as system drive
3 TB sata HDD for media
Network - Wired (200-300 mbps)
Running on Win 10 (since its not supported in Win11).
Now that i have ruled out bandwidth, somewhat completely, what could be the cause?
The CPU has been and should be more than enough for several simultaneous 4K streams, so i'm thinking software? Either missing drivers, some configurations missings, anything really.
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github){kind=icon}
