• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Support Troubleshooting jf 10.10.7 Ugreen 4800 plus - Playback failed due to a fatal player error

     
    • 0 Vote(s) - 0 Average

    jf 10.10.7 Ugreen 4800 plus - Playback failed due to a fatal player error

    hardware transcoding error
    fisao
    Offline

    Junior Member

    Posts: 1
    Threads: 1
    Joined: 2025 Jun
    Reputation: 0
    Country:France
    #1
    2025-06-07, 12:19 PM (This post was last modified: 2025-06-07, 12:31 PM by fisao. Edited 3 times in total.)
    Hello everyone, 

    I have not found a solution to my exact problem in the search functon of this forum and am therefore starting this new thread

    I have the following error: 
    "Playback Error Playback failed due to a fatal player error."

    on the following setup: 
    jellyfin 10.10.7 on Ugreen DXP4800plus (32GB RAM)
    running the stock OS (UGOS I believe) in version 1.5.0.2628
    installed via Docker image 

    my file setup is: 
    Cache
    /config/cache
    Logs
    /config/log
    Metadata
    /config/data/metadata
    Transcodes
    /config/cache/transcodes
    Web
    /usr/share/jellyfin/web

    and I have attached the latest log output for the last three attempts.

    - the playback error seems to only occur on x265 HEVC 10bit files 
    - when hardware encoding is enabled, for all file formats -> always immediate fail 
    - when hardware encoding is disabled -> transcode starts, but is understandably very laggy, so not a solution unfortunately

    the cpu on the machine is (I believe):
    - Intel Pentium Gold 8505 4400 5 Cores 6 threads with 32 GB of RAM (because I had it available, it is of course overkill)

    I see that ffmpeg is exiting with an 187, but I am not knowlegeable enough to understand why in this case

    I would be immensely grateful if anybody could give me some pointers as to what could be done to remedy the situation

    Please let me know if any additional information that I could provide could help, thank you very much if you can


    Attached Files
    .txt   linuxserver_jellyfin.txt (Size: 93.33 KB / Downloads: 19)
    Winifred99
    Offline

    Junior Member

    Posts: 1
    Threads: 0
    Joined: 2025 Jun
    Reputation: 0
    Country:Germany
    #2
    Yesterday, 02:02 PM
    Hey fisao,
    I have literally the same hardware and also using the pre-installed UGOS. I can make the Jellyfin app to start in a docker container, make it find the media folder (it finds all the files and lists them in the library), but I could never figure out how to troubleshoot the "Playback failed due to a fatal player error". Docker logs do not show errors, webbrowser dev-tools do not show the error message. For any settings, be that with hardware acceleration or not, with admin docker permission or not, I can't make it work with any file.

    Now is the tricky part. By authenticating into the docker container using ssh, I could check if the ffmpeg is showing any errors with the following command:


    root@xxxxxxxxxxxxConfused-face# /usr/lib/jellyfin-ffmpeg/ffmpeg -i "/data/Music.mp3" -acodec aac -v "debug" -f mp4 /cache/test.mp4


    And the output on interruption was this:


    [in#0/mp3 @ 0x558811278100] Input file #0 (/data/Music.mp3):
    [in#0/mp3 @ 0x558811278100] Input stream #0:0 (audio): 22668 packets read (16726656 bytes); 22667 frames decoded; 0 decode errors (26112384 samples);
    [in#0/mp3 @ 0x558811278100] Total: 22668 packets (16726656 bytes) demuxed
    [AVIOContext @ 0x558811281080] Statistics: 16744448 bytes read, 0 seeks
    Exiting normally, received signal 2.


    so I just assume that ffmpeg _can_ read the file and the problem is in permissions.

    How did you test the transcoding? I seriously wonder why you have no issues with some file formats and with the same software+hardware I get errors.
    Fate
    Offline

    Member

    Posts: 221
    Threads: 3
    Joined: 2023 Jun
    Reputation: 16
    #3
    4 hours ago
    The main issue I think is that it can't access an iGPU/ GPU.

    Did you guys passthrough your iGPU to the docker container?
    Is it running as privileged?

    Can you share docker compose file?
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode