this post was submitted on 24 Mar 2024
17 points (100.0% liked)

Jellyfin: The Free Software Media System

5752 readers
21 users here now

Current stable release: 10.10.2

Community Standards

Website

Forum

GitHub

Documentation

Feature Requests

Matrix (General Information & Help)

Matrix (Announcements)

Matrix (General Development)

Matrix (Off-Topic) - Come get to know the team and blow off steam!

Matrix Space - List of all the available rooms on Matrix.

Discord - Bridged to our Matrix rooms

founded 4 years ago
MODERATORS
 

Hi I have jellyfin installed in a VM with 24 cores and 32GiB RAM (VM also used for Docker). Whenever I attempt to play higher quality files, jellyfin crashes after a few minutes. I haven't seen it struggle with lower quality media. 

Here are some logs: FFmpeg.Transcode-2024-03-24_16-11-43_d48825174d455ae3ff859d8b28582853_ce3f3ebf.log upload_org.jellyfin.androidtv_0.16.7_20240324161053_d2befd034e424a3490e7ea55af1fe1f2.log Fmpeg.Transcode-2024-03-24_16-11-38_d48825174d455ae3ff859d8b28582853_dafa4555.log FFmpeg.DirectStream-2024-03-24_16-08-12_d48825174d455ae3ff859d8b28582853_dac7115f.log

I cannot for the life of me figure out whats wrong. I've tried disabling plugins, different clients, hard resets etc, but it still crashes.

Can someone enlighten me??  :(

you are viewing a single comment's thread
view the rest of the comments
[–] entropicdrift@lemmy.sdf.org 1 points 7 months ago (3 children)

There's a couple things that stick out to me in these logs:

  1. the androidtv client logs show the crash was due to a time-out while waiting for the server to respond to a request for over 3 seconds.

  2. you included a DirectStream log, that's usually not too hard for even a Raspberry Pi to handle reasonably well

  3. the first log I looked at showed libx264 was using 36 threads

So my guess is that, due to video encoding not scaling all that well across larger numbers of threads, your server is being bogged down with this transcoding and isn't providing http responses fast enough to your client device(s).

A simple way to troubleshoot this would be to explicitly set the transcoding thread count to something a bit lower than what your server has, say 16 or 20, and see if that does any better.

An obvious potential fix would be to use hardware acceleration if it's available to you. I run my Jellyfin server off of a little N100 mini PC and it can transcode 4K HDR 70 Mbps video (tonemapping included) at about 45 fps due to the hw acceleration. That said, I know it can be tricky to set up in a VM and you may not have the HW accel capability in your server CPU anyhow.

[–] sammeeeeeee@lemmy.world 2 points 7 months ago (2 children)

Wow, I never considered that too many cores may be the issue. I will for sure try that.

I believe my cpu is compatible, but I believe this is not iGPU transcoding. Pretty sure my server does have an iGPU (although I've never actually plugged in a screen so I can't be sure). I will research passing through either of those.

I also read that it's possible to use a different server for just transcoding. I have an old laptop I've been considering setting for that, but it's network speeds are shite.

[–] cooljimy84@mastodon.social 0 points 7 months ago (1 children)

@sammeeeeeee @entropicdrift not sure if Intel igpus are the same, but my ryzen 5700g igpu won't transcoded unless when it boots it has a monitor plugged in and powered on...

[–] sammeeeeeee@lemmy.world 1 points 7 months ago

Oh well that's definitely not possible for me (unless idrac counts)