Hello fellow selfhosters! I reformatted my USB hard drive from exFAT to XFS because I needed a filesystem that could handle hardlinks. I remounted the hard drive and now jellyfin webUI has a severe stuttering problem on some videos, all of them are MKV but it may be a coincidence. On android (using exoplayer) the same files works smoothly. what could be the problem?
in the logs I get a bunch of Slow HTTP Response from http://fedoraserver:8096/ to 192.168.1.30 in 0:00:07.4635856 with Status Code 200

OT: while looking at the logs this happened

SOLUTION: I enabled hardware acceleration, and manually selected also the HEVC and Allow encoding in HEVC format settings, and now the stutter disappeared! thanks to everyone for your help!!!

tubbadu
creator
link
fedilink
English
29M

How did you solve it?

@Gnorv@feddit.de
link
fedilink
English
39M

I did not really solve it. I looked around for a bit but found no good solution. The only thing that sort of worked was to copy the stream URL in Jellyfin and paste it into VLC Media Player, which could play the videos okay. But that was not really satisfactory for me.

In the end I installed a new OS on my PC which already came with the codecs to decode x265 preinstalled. I installed it for other reasons but it fixed also that issue and now I can play any video in the Jellyfin Media Player. I did not try if it also works in the browser. The OS I am now using is called Nobara.

tubbadu
creator
link
fedilink
English
19M

So it’s a problem on codecs on my pc, not my server, correct? So installing the correct drivers should solve the issue?

@Gnorv@feddit.de
link
fedilink
English
49M

I do not think they are called drivers, but yes, installing the needed codecs should work. I just did not find out how to do it properly.

KptnAutismus
link
fedilink
English
5
edit-2
9M

not OC, but i ended up redownloading whatever was x265 and replacing it with 264 or anything else.

also the 1060 in my NAS can do NVENC encoding. that helped a lot with compatibility.

You can also use something like handbrake to convert everything to 264 instead of redownloading everything. You can also set it up to convert after items are downloaded.

lazynooblet
link
fedilink
English
29M

Does jellyfish not transcode on the fly?

@Blackmist@feddit.uk
link
fedilink
English
29M

Yes, but if the server isn’t fast enough to do it, then you’re going to have a bad time.

@AustralianSimon@lemmy.world
link
fedilink
English
2
edit-2
9M

It can but it’s the server hardware that decides your performance, you can just avoid transcoder on the fly and have h264 mp4 and can run JF on a toaster smoothly.

@punkhazard@feddit.de
link
fedilink
English
29M

I just used ffmpeg to encode my files to h264, worked on all my devices

tubbadu
creator
link
fedilink
English
29M

Doing this will prevent my files from seeding, I’d like to find a more “universal” solution

Thanks for the info tho!

I had the same issue, I used tdarr to re encode to h264 mp4

I do the same. I just have it do a transcode job every Sunday.

i had this problem. i fixed it with a faster machine. same os, same files. more cpu worked.

tubbadu
creator
link
fedilink
English
29M

You mean a new sever or a new client?

@superbirra@lemmy.world
link
fedilink
English
29M

yes!

server. it was choking on decoding

tubbadu
creator
link
fedilink
English
2
edit-2
9M

But I know of people running jellyfin on a raspberry, I have an old laptop but it’s not that old… There’srno way to run it smoothly?

yeah, re-encode to a lighter encoding like 264. might be slightly larger, but less work for the cpu

Create a post

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.

Resources:

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

Questions? DM the mods!

  • 1 user online
  • 127 users / day
  • 422 users / week
  • 1.16K users / month
  • 3.85K users / 6 months
  • 1 subscriber
  • 3.68K Posts
  • 74.2K Comments
  • Modlog