this post was submitted on 01 Apr 2026
25 points (96.3% liked)

Selfhosted

58061 readers
719 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I tried "all" settings. I tried reading the logs and norhing helped. I had many months without issues. How do you guys debug it? The logs aren't too helpful for me and there are too many settings for me to play with. I've got an intel GPU with eirher QSV or VAAPI. Disabling does not work either. CPU is normal, GPU is normal. RAM is not full.

you are viewing a single comment's thread
view the rest of the comments
[–] pHr34kY@lemmy.world 5 points 7 hours ago* (last edited 7 hours ago)

Just start listening to dubstep and you'll stop noticing 😆.

Maybe run lm-sensors and make sure the CPU/GPU isn't being thermothrottled? I'd usually look at dmesg and look for red stuff. Any hardware issues are usually pretty obvious.

Try other apps. If you youtube or VLC behaves the same, the problem may be outside of jellyfin. If not, it narrows it down.

If could even be the server not being able to transcode in realtime. Try watching a file known to already be in a suitable format. It should direct stream and be much less load on the server. I've seen server encode CPU saturation and it does kinda look the same as client decode stutter. If it's the server, you'll probably see the same stutter from another device such as a phone.