Jellyfin Forum
SOLVED: Fatal Playback Error - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: Fatal Playback Error (/t-solved-fatal-playback-error--13746)



Fatal Playback Error - Smuggles - 2025-09-18

Hello,

First I'd like to apologize if I'm asking this question in the wrong place.

I recently got a UGreen NAS which doubles as a media server. When I have hardware transcoding turned on, any media in the .mkv format completely fails to play. I can get around this issue by turning hardware transcoding off, but that puts more load on the CPU, which I'd prefer to avoid.

As far as I can tell, the solution for this would be to install/upgrade the version of FFMPEG that Jellyfin uses, but I have no idea how to do that on the NAS through UGOS and Docker.

Attached is a log file created when I attempted to play some .mkv media.

If anyone can help me out that would be much appreciated, thank you.


RE: Fatal Playback Error - IndianaLarry - 2025-09-20

Perhaps I am interpreting this wrong, but it looks like it is trying to access the GPU or something, but failing (possibly because the NAS is not equipped with a hardware-accelerating GPU).


RE: Fatal Playback Error - Smuggles - 2025-09-21

That is entirely possible. I was under the impression the the NAS (having an Intel N100 CPU) would support using Intel Quicksync for hardware transcoding.

I should also mention that when I'm streaming media with hardware transcoding turned on, the CPU usage is significantly lower than when hardware transcoding is turned off (~5% compared to ~99% utilization) which is the main thing I'm trying to avoid as I don't really want to have the CPU working that hard for a prolonged period when I just want to enjoy my shows and movies.


RE: Fatal Playback Error - Smuggles - 2025-09-21

UPDATE:

Turns out I hadn't enabled 'Graphics card perfomance' when creating the Jellyfin container in Docker. Going back through the settings and checking that box seems to have fixed my issue.