+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Raspberry pi Playback failed due to a fatal player error. (/t-raspberry-pi-playback-failed-due-to-a-fatal-player-error)
Raspberry pi Playback failed due to a fatal player error. - Zraner - 2025-03-30
I am migrating my movie collection from Plex to Jellyfin, and it’s been quite a challenge. After managing to get the folders to appear in the libraries, it is not reading all the movies I have. It only detected 102, but I have quite a lot more (around 350).
In addition to this issue, when I try to play any of the files it does recognize, I get an error message: "Playback failed due to a fatal player error."
I have searched through forums and the internet and tried several things, for example, installing Jellyfin's ffmpeg6, but I haven’t been able to get it to work in any way. It won’t play on the computer or any device I’ve tested.
Log file: https://lesma.eu/wobadugi
I have managed to get all the series to appear, every time I identified one, the next one appeared, but now all the ones I have identified appear without seasons or episodes, I have checked that everything is well named, for example The Magicians/Season 01/The Magicians s01e01.
RE: Raspberry pi Playback failed due to a fatal player error. - TheDreadPirate - 2025-03-30
The way you have your movies organized is problematic. While having movies "loose" in the movies root folder is fine, the file names are problematic. EVERY part of the file name is used for querying for metadata. The movie name also needs to pretty closely match TMDB (the default metadata provider) if there are movies with similar names.
For example.
Code:
/media/pi/Peliculas/Jurassic.park.3.(2001).(Spanish.English.Subs).BDrip.1080p.x265-AC3.by.JJ.mkvI'm not sure if this is a movie that isn't being added, but everything after (2001) should be removed. Ideally, you'd also add the TMDB ID to the end for consistent, reliable, identification. And the movies should be in their own folder. But this isn't required if you don't intend to add extras.
Code:
/media/pi/Peliculas/Jurassic.Park.3.(2001).[tmdbid-331]/Jurassic.park.3.(2001).[tmdbid-331].mkv"Regarding the playback errors. I see some permission issues.
Code:
[2025-03-30 06:21:39.971 +02:00] [ERR] Error processing request. URL "GET" "/Videos/3b3a950331bcd9e7a2391870cc4994c7/stream.mkv".
System.UnauthorizedAccessException: Access to the path '/media/pi/Peliculas/Jurassic.park.3.(2001).(Spanish.English.Subs).BDrip.1080p.x265-AC3.by.JJ.mkv' is denied.I am pretty sure exit code 243 is a permission error.
Code:
MediaBrowser.Common.FfmpegException: FFmpeg exited with code 243Permission issues could possibly explain your issues identifying shows.
RE: Raspberry pi Playback failed due to a fatal player error. - Zraner - 2025-04-02
In the end it was a permissions problem, having reinstalled several times and tried everything, in the last installation I did not give the proper permissions, thank you very much.
Now I have another problem.
My TV is not HDR, I used to play HDR content without the TV having HDR through Plex, in Jellyfin as much as I try to touch a thousand things I always end up at the same point, the movie starts playing but nothing is seen, the movie is heard but I stop seeing anything on the screen, not even the menu to choose audio, pause, forward, etc... Transcoding is not an option for me since the raspberry model I'm using is the 3B+ and if I try to transcode something explodes everything, but when doing directplay with plex I never had problems, imagine not having problems with jellyfin either, but no luck.
My server version in 10.10.6
RE: Raspberry pi Playback failed due to a fatal player error. - TheDreadPirate - 2025-04-03
Plex uses their own playback engine while Jellyfin relies on the playback engine that Google providers (exoplayer). And there are known issues with exoplayer not properly handling HDR content. Or not falling back to compatible modes. If this is a Dolby Vision profile 8 video, Plex is probably falling back to SDR since that profile supports falling back to SDR.
But exoplayer does not gracefully handle fallback in a lot of cases.
It is a known pain point and there are efforts to workaround this.
RE: Raspberry pi Playback failed due to a fatal player error. - Zraner - 2025-04-03
So what do you recommend me to do? there are chances that my partner will give me a mini pc with a n200, 16gb ram and 1tb ssd, but until that time comes, any recommendation to play hdr content? what I find funny is that the Raspberry pi 3b+ is able to simultaneously play 2 movies 4k, the pity is that the hdr is screwing me so much.
RE: Raspberry pi Playback failed due to a fatal player error. - TheDreadPirate - 2025-04-03
When your server cannot transcode video, the recommendation is to not have HDR content at all or have all your clients run Kodi as the client.
You could also try converting the video to HDR10, which exoplayer has no problem playing. BUT since your TV is not HDR, I'm am pretty sure it will request a transcode due to the TV not supporting HDR. And HDR10 does not support falling back to SDR like DV profile 8 does.
https://forum.jellyfin.org/t-converting-dolby-vision-to-hdr10
When/if you do get that N200 mini PC, that has excellent transcoding support.