• 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 Can't play movie (2160p HDR H265 mkv 90Gb) on Android/LG WebOS/PC Web

     
    • 0 Vote(s) - 0 Average

    Can't play movie (2160p HDR H265 mkv 90Gb) on Android/LG WebOS/PC Web

    Videos are not playing
    Norrodar
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 Dec
    Reputation: 0
    Country:Germany
    #1
    2024-12-04, 12:42 AM
    Hey Smiling-face

    I'm trying to play Wolf of Wall Street and no player (Android, LG WebOS, PC Web) is able to play it.

    Android: endless loading
    LG WebOS: endless loading
    PC Web: error (fatal error)

    I'm providing all logs and media-info, because I think it has something to do with the h265-codec or file-size. Other movies/series with similar codec/size/etc. have the same issue.
    Also Trickplay isn't generating images.

    I hope I collected all needed information - if not please ask.

    Thanks for your time Smiling-face


    Attached Files
    .txt   trans3.log.txt (Size: 19.65 KB / Downloads: 61)
    .txt   trans1.log.txt (Size: 19.65 KB / Downloads: 47)
    .txt   trans2.log.txt (Size: 19.65 KB / Downloads: 47)
    .txt   mediainfo.txt (Size: 11 KB / Downloads: 49)
    .txt   The Wolf of Wall Street 2013.nfo.txt (Size: 12.02 KB / Downloads: 44)
    .zip   log_20241204.log.txt.zip (Size: 400.62 KB / Downloads: 33)
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2024-12-04, 01:53 AM (This post was last modified: 2024-12-04, 01:54 AM by TheDreadPirate. Edited 1 time in total.)
    What are your hardware specs. And did you pass in the GPU into the container? Can you share your docker compose with us?
    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]
    Norrodar
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 Dec
    Reputation: 0
    Country:Germany
    #3
    2024-12-04, 10:50 AM (This post was last modified: 2024-12-04, 12:20 PM by Norrodar. Edited 3 times in total.)
    Hey and thanks for your help! Smiling-face

    I'm using a Synology NAS 920+:
    • CPU: Intel Celeron J4125, 4-Core, 2.0 GHz (base) up to 2.7 GHz (turbo) 
    • Ram: 20Gb total (14Gb free to use)
    • Lan: 2x 1Gbps

    GPU Passthrough:
    • The Synology DS920+ does not support direct GPU passthrough to Docker containers as it doesn't have a dedicated GPU, and the integrated GPU of the Intel Celeron J4125 is not designed for such purposes.

    My Docker-Compose looks like:
    volume2 = M.2 SSD
    volume1 = HDD (7200rpm, SHR/Raid5)

    Code:
    services:
      jellyfin:
        image: jellyfin/jellyfin
        container_name: jellyfin
    #    user: uid:gid
        network_mode: 'host'
        volumes:
          - /volume2/docker/jellyfin/config:/config
          - /volume2/docker/jellyfin/cache:/cache
          - /volume1/mediathek:/media
    #      - /path/to/media2:/media2:ro
        restart: 'unless-stopped'
        # Optional - alternative address used for autodiscovery
    #    environment:
    #      - JELLYFIN_PublishedServerUrl=http://video2.lan
        # Optional - may be necessary for docker healthcheck to pass if running in host network mode
    #    extra_hosts:
    #      - "host.docker.internal:host-gateway"

    Update:
    I just realized that the devices-entries are missing, so I added:

    Code:
        devices:
          - /dev/dri:/dev/dri #optional
          - /dev/dri/renderD128:/dev/dri/renderD128
          - /dev/dri/card0:/dev/dri/card0


    Now LG WebOS: Can't play because media is not supported from this device (TV).
    Android still the same: Audio, but no image/video
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2024-12-04, 01:41 PM
    The devices section only needs to be one line.

    Code:
    devices:
          - /dev/dri:/dev/dri #optional

    Share your new logs now that the GPU is passed into the container.
    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]
    Norrodar
    Offline

    Junior Member

    Posts: 3
    Threads: 1
    Joined: 2024 Dec
    Reputation: 0
    Country:Germany
    #5
    2024-12-09, 05:43 PM
    Hey TheDreadPirate, I'd a few days off, sorry Smiling-face

    I also used my time to start over the whole jellyfin-topic.
    Now my movies/series are all working!
    Except on the web-client, where the 4k movies are laggy every 3-5secs for 1-2secs. CPU is only at 60%, Ram is at about 11/20Gb, HDDs 3-7Mb/s read/write.
    The LG WebOS also has rarely lagging in moments where lots is happening on the image.
    Android seems to be totally fine.

    I'm trying to reproduce it and to generate a log.

    All the best,
    Norro Smiling-face




    For Googlers:

    I'm using a Synology DS920+ NAS (20Gb Ram) with a "Cache-SSD" as Volume2 (see github-Repo for a howto) for my Docker-Containers (using Portainer).

    My docker-compose (stack) looks like this:
    Code:
    services:
      jellyfin:
        image: jellyfin/jellyfin
        container_name: jellyfin
        environment:
          - TZ=Europe/Berlin
          - LIBVA_DRIVER_NAME=iHD
        network_mode: 'host'
        volumes:
          - /volume2/docker/jellyfin/config:/config
          - /volume2/docker/jellyfin/cache:/cache
          - /volume1/mediathek:/media
        devices:
          - /dev/dri:/dev/dri
        restart: 'unless-stopped'

    For Jellyfin itself you have to use settings like this. You've to find out what your CPU is capable of, you can find a list here: https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video

    Hardware Decoding
    Enable hardware decoding for:
    • H264
    • HEVC
    • MPEG2
    • VC1
    • VP8
    • VP9
    • HEVC 10bit
    • VP9 10bit
    • Prefer OS-native DXVA or VA-API hardware decoders
    Hardware Encoding Options
    • Enable hardware encoding
    • Allow encoding in HEVC format
    • Enable VPP tone mapping
    Make sure to set the hardware acceleration to "Intel QuickSync (QSV)" in the Jellyfin settings under "Playback."
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,375
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2024-12-09, 08:30 PM
    Most streaming devices/smart TVs have a max bit rate they can handle and I'm wondering if you're bumping up on the limit. Since the bit rate advertised in the media info of a file is the AVERAGE bit rate. Scenes with a lot of motion will spike the bit rate while still scenes will use less.
    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]
    « 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