• 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 SOLVED: "Playback failed due to a fatal player error." (Only in Firefox)

    Pages (2): « Previous 1 2

     
    • 0 Vote(s) - 0 Average

    SOLVED: "Playback failed due to a fatal player error." (Only in Firefox)

    Can't play some media, but this only occurs in Firefox
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #11
    2024-10-19, 11:11 PM
    In the list of codecs, you can check H264, MPEG2, and VC1.

    Can you share your jellyfin logs via pastebin?
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    altair
    Offline

    Junior Member

    Posts: 5
    Threads: 0
    Joined: 2024 Oct
    Reputation: 0
    Country:Greece
    #12
    2024-10-20, 12:07 AM
    (2024-10-19, 11:11 PM)TheDreadPirate Wrote: In the list of codecs, you can check H264, MPEG2, and VC1.

    Can you share your jellyfin logs via pastebin?

    There you go https://pastebin.com/HuKdeN9j
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #13
    2024-10-20, 12:18 AM
    Did you switch to VAAPI? You showed the screenshot of you switching, but the log is still saying you're using QSV?

    I noticed that the output of the transcode is 4K. I'm wondering if that iGPU just doesn't support transcoding to that resolution. In Firefox, go to the Settings > Playback menu (not the one in dashboard) and set the max transcode resolution to 1080p.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    altair
    Offline

    Junior Member

    Posts: 5
    Threads: 0
    Joined: 2024 Oct
    Reputation: 0
    Country:Greece
    #14
    2024-10-20, 02:26 AM
    (2024-10-20, 12:18 AM)TheDreadPirate Wrote: Did you switch to VAAPI?  You showed the screenshot of you switching, but the log is still saying you're using QSV?

    I noticed that the output of the transcode is 4K.  I'm wondering if that iGPU just doesn't support transcoding to that resolution.  In Firefox, go to the Settings > Playback menu (not the one in dashboard) and set the max transcode resolution to 1080p.

    Ah yes sorry my bad, that was the old paste, here is the with VAAPI : https://pastebin.com/EnYYNrY4

    And here is the log with max transcoding set to 1080p on firefox: https://pastebin.com/uzXx6v7B and apparently as you can see it plays on firefox although its quite choppy if you try to move around... 
    The thing is on chromium browsers i can play it on 4k with no problem at all smooth as hell and even when moving around in the movie the playback is almost instant its almost as fast as playing local so the iGPU is probably capable of it since it works on edge.
    Here is an image of player info from edge:
    [Image: FBlDVQq.png]

    And here is one from firefox with capped transcoding at 1080p:
    [Image: nysPrUD.png]
    Hope these tell you something more.

    Also here is the log with setting max transcoding to 1080p on my android device(xiaomi mi 10): https://pastebin.com/iWdjLGqg still isn't working there... even tried 360p to no avail. So no screenshot from there i still get the "Playback failed due to fatal player error"
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #15
    2024-10-20, 03:12 AM
    Firefox doesn't do HEVC, period. So it is transcoding, successfully this time. But it is BARELY managing 1x speed. Because of the specs of your server, I'd recommend using Jellyfin Media Player on your PC clients, since it can direct play pretty much anything.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    altair
    Offline

    Junior Member

    Posts: 5
    Threads: 0
    Joined: 2024 Oct
    Reputation: 0
    Country:Greece
    #16
    2024-10-20, 01:34 PM
    Hmm, what about the mobile app? i still get the error there. I tried the Android TV app and it works there, that's weird any idea about that?
    EDIT: I just found out that on the app you can Settings > Client Settings > Video player and change it to integrated player or external, instead of web player and HEVC should work on android app as well.
    I tried the windows app as well plays well again. I'll probably use that or edge.

    Documentation has H.265 as not supported on Firefox indeed. I didn't know HEVC is actually H.265.
    Thank you so much for the help TheDreadPirate really appreciated!
    DeNewGuy
    Offline

    Junior Member

    Posts: 6
    Threads: 1
    Joined: 2024 Oct
    Reputation: 0
    #17
    2024-10-20, 11:08 PM (This post was last modified: 2024-10-20, 11:09 PM by DeNewGuy. Edited 1 time in total.)
    (2024-10-13, 03:44 PM)TheDreadPirate Wrote: Did you setup low power encoding?

    https://jellyfin.org/docs/general/admini...e-on-linux

    Also, since you're using a backport kernel, did you also install all the kernel header, module, and firmware packages?

    My apologies for the late response, but when trying to follow the steps in the link you sent, I'm stuck on step 4.
    When using sudo dmesg | grep i915
    I get the following:
    Code:
    [    1.446714] i915 0000:03:00.0: [drm] VT-d active for gfx access
    [    1.446731] i915 0000:03:00.0: vgaarb: deactivate vga console
    [    1.446745] i915 0000:03:00.0: [drm] Local memory IO size: 0x00000001fc000000
    [    1.446746] i915 0000:03:00.0: [drm] Local memory available: 0x00000001fc000000
    [    1.459440] i915 0000:03:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=io+mem:owns=none
    [    1.460043] i915 0000:03:00.0: firmware: direct-loading firmware i915/dg2_guc_70.bin
    [    1.461236] i915 0000:03:00.0: firmware: direct-loading firmware i915/dg2_huc_gsc.bin
    [    1.462730] i915 0000:03:00.0: firmware: direct-loading firmware i915/dg2_dmc_ver2_08.bin
    [    1.464701] i915 0000:03:00.0: [drm] Finished loading DMC firmware i915/dg2_dmc_ver2_08.bin (v2.8)
    [    1.469020] i915 0000:03:00.0: [drm] GT0: GuC firmware i915/dg2_guc_70.bin version 70.29.2
    [    1.469021] i915 0000:03:00.0: [drm] GT0: HuC firmware i915/dg2_huc_gsc.bin version 7.10.16
    [    1.478411] i915 0000:03:00.0: [drm] GT0: GUC: submission enabled
    [    1.478413] i915 0000:03:00.0: [drm] GT0: GUC: SLPC enabled
    [    1.478626] i915 0000:03:00.0: [drm] GT0: GUC: RC enabled
    [    1.493811] [drm] Initialized i915 1.6.0 20230929 for 0000:03:00.0 on minor 0
    [    1.494437] i915 display info: display version: 13
    [    1.494438] i915 display info: cursor_needs_physical: no
    [    1.494439] i915 display info: has_cdclk_crawl: no
    [    1.494439] i915 display info: has_cdclk_squash: yes
    [    1.494440] i915 display info: has_ddi: yes
    [    1.494440] i915 display info: has_dp_mst: yes
    [    1.494440] i915 display info: has_dsb: yes
    [    1.494441] i915 display info: has_fpga_dbg: yes
    [    1.494441] i915 display info: has_gmch: no
    [    1.494441] i915 display info: has_hotplug: yes
    [    1.494442] i915 display info: has_hti: no
    [    1.494442] i915 display info: has_ipc: yes
    [    1.494442] i915 display info: has_overlay: no
    [    1.494443] i915 display info: has_psr: yes
    [    1.494443] i915 display info: has_psr_hw_tracking: no
    [    1.494444] i915 display info: overlay_needs_physical: no
    [    1.494444] i915 display info: supports_tv: no
    [    1.494444] i915 display info: has_hdcp: yes
    [    1.494445] i915 display info: has_dmc: yes
    [    1.494445] i915 display info: has_dsc: yes
    [    1.494502] i915 0000:03:00.0: [drm] Cannot find any crtc or sizes
    [    1.494548] i915 0000:03:00.0: [drm] Cannot find any crtc or sizes
    [    1.494566] i915 0000:03:00.0: [drm] Cannot find any crtc or sizes
    [    2.252804] snd_hda_intel 0000:04:00.0: bound 0000:03:00.0 (ops i915_audio_component_bind_ops [i915])
    [    2.594916] i915 0000:03:00.0: [drm] GT0: HuC: authenticated for all workloads
    [    2.594922] mei_pxp i915.mei-gsc.768-fbf6fcf1-96cf-4e2e-a6a6-1bab8cbe36b1: bound 0000:03:00.0 (ops i915_pxp_tee_component_ops [i915])


    And when using:
    Code:
    sudo cat /sys/kernel/debug/dri/0/gt/uc/guc_info
    sudo cat /sys/kernel/debug/dri/0/gt/uc/huc_info
    And
    Code:
    sudo cat /sys/kernel/debug/dri/1/gt/uc/guc_info
    sudo cat /sys/kernel/debug/dri/1/gt/uc/huc_info
    And
    Code:
    sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status
    sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status
    I get the following:
    "No such file or directory"
    When using ls in the /sys/kernel/debug/dri/ I get:
    Code:
    lrwxrwxrwx  1 root root 0 Oct 21 00:51 0 -> 0000:03:00.0
    drwxr-xr-x 16 root root 0 Oct 21 00:51 0000:03:00.0
    lrwxrwxrwx  1 root root 0 Oct 21 00:51 128 -> 0000:03:00.0

    Any suggestions on what I'm doing incorrectly?

    Kind regards

    P.S. My apologies for my incompetence.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #18
    2024-10-21, 12:12 AM (This post was last modified: 2024-10-21, 12:13 AM by TheDreadPirate. Edited 1 time in total.)
    Different distros locate the i915 status in slightly different places. On Ubuntu 24.04 with both an iGPU and Arc GPU, my Arc GPU's status is located in

    /sys/kernel/debug/dri/1/gt0/uc/guc_info
    /sys/kernel/debug/dri/1/gt0/uc/huc_info

    Start in /sys/kernel/debug/dri, then stop through each directory one at a time after that.

    Having said that, the dmesg output looks good. The above will show, essentially, the same info.
    Jellyfin 10.10.7 (Docker)
    Ubuntu 24.04.2 LTS w/HWE
    Intel i3 12100
    Intel Arc A380
    OS drive - SK Hynix P41 1TB
    Storage
        4x WD Red Pro 6TB CMR in RAIDZ1
    [Image: GitHub%20Sponsors-grey?logo=github]
    DeNewGuy
    Offline

    Junior Member

    Posts: 6
    Threads: 1
    Joined: 2024 Oct
    Reputation: 0
    #19
    2024-10-21, 01:02 PM
    (2024-10-21, 12:12 AM)TheDreadPirate Wrote: Different distros locate the i915 status in slightly different places.  On Ubuntu 24.04 with both an iGPU and Arc GPU, my Arc GPU's status is located in

    /sys/kernel/debug/dri/1/gt0/uc/guc_info
    /sys/kernel/debug/dri/1/gt0/uc/huc_info

    Start in /sys/kernel/debug/dri, then stop through each directory one at a time after that.

    Having said that, the dmesg output looks good.  The above will show, essentially, the same info.

    Couldn't get the cat commands to work, but I did enable low-power hardware encoding.
    And the file I couldn't play before plays now. Grinning-face

    I'll set your initial reference to the Jellyfin docs as the solution.

    Thank you soo much for all the help!!
    It's greatly appreciated.
    Again, thank you.
    Pages (2): « Previous 1 2

    « 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