• 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 Transcoding when not necessary?

     
    • 0 Vote(s) - 0 Average

    Transcoding when not necessary?

    christiaanvdlaken
    Offline

    Junior Member

    Posts: 14
    Threads: 4
    Joined: 2023 Nov
    Reputation: 0
    Country:Netherlands
    #1
    2025-01-23, 05:19 PM
    So i've noticed that some files will initiate a transcode in the internal player but when I use an external player(justplayer) it says that it is direct playing. It also initiates the HDR10 on the external player but not on the internal player, probably because of the transcoding.

    I've attached 2 log files that include records of when I was trying it on Nosferatu (2024) but it happens at a lot of files, mostly higher quality ones.

    I have QSV enabled and checked pretty much all formats.
    I run Jellyfin in a ubuntu VM and have GPU pass through.
    I would like to attach my transcoding setting, is there a way to export those in some way ?

    Video
    Title: 4K HEVC Dolby Vision Profile 8.1 (HDR10)
    Codec: HEVC
    AVC: No
    Profile: Main 10
    Level: 150
    Resolution: 3592x2152
    Aspect ratio: 5:3
    Anamorphic: No
    Interlaced: No
    Framerate: 23.976025
    Bitrate: 25421 kbps
    Bit depth: 10 bit
    Video range: HDR
    Video range type: DOVIWithHDR10
    DV title: Dolby Vision Profile 8.1 (HDR10)
    DV version major: 1
    DV version minor: 0
    DV profile: 8
    DV level: 6
    DV rpu preset flag: 1
    DV el preset flag: 0
    DV bl preset flag: 1
    DV bl signal compatibility id: 1
    Color space: bt2020nc
    Color transfer: smpte2084
    Color primaries: bt2020
    Pixel format: yuv420p10le
    Ref frames: 1

    My TV: TCL 65p635


    Attached Files
    .txt   Jellyfin20250123.txt (Size: 172.29 KB / Downloads: 57)
    .txt   FFmpegTrancode.txt (Size: 45.46 KB / Downloads: 64)
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2025-01-23, 05:39 PM
    You did not check "Enable hardware encoding". It is CPU encoding.

    Code:
    Stream #0:0 -> #0:0 (hevc (native) -> hevc (libx265))

    Also, exoplayer has known issues with not actually falling back to HDR10.

    https://github.com/jellyfin/jellyfin-and...ssues/2700

    You could remove Dolby Vision, which would convert the video to HDR10. I wrote a guide for this.

    https://forum.jellyfin.org/t-converting-...n-to-hdr10
    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]
    christiaanvdlaken
    Offline

    Junior Member

    Posts: 14
    Threads: 4
    Joined: 2023 Nov
    Reputation: 0
    Country:Netherlands
    #3
    2025-01-23, 06:18 PM
    Thanks for the quick reply!

    I checked and i have 'Enable hardware encoding' checked. I find it strange that the internal player transcodes the file but when it is played in an external player it plays it directly with HDR10 and does it flawlessly. The thing is I much prefer the internal player because it is better integrated with the app, navigation is easier and it just looks much cooler with the banners.

    Could it be one of my settings in the transcoding section that initiates these transcodes ?
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #4
    2025-01-23, 08:16 PM
    No. This is a flaw in exoplayer (the internal player). Google has known about the flaw for years and has not addressed it. There are some plans to attempt to work around this in future versions of Jellyfin. For now, the workarounds are to force transcoding or convert the video to plain HDR10.
    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]
    gnattu
    Offline

    Team Member

    Posts: 341
    Threads: 0
    Joined: 2024 Feb
    Reputation: 17
    #5
    2025-01-23, 11:35 PM
    > No. This is a flaw in exoplayer (the internal player). Google has known about the flaw for years and has not addressed it. There are some plans to attempt to work around this in future versions of Jellyfin. For now, the workarounds are to force transcoding or convert the video to plain HDR10.

    Is this really the case? How could exoplayer not being able to even play Dolby Vision 8.1 in HDR10 fallback?
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #6
    2025-01-24, 03:31 PM
    I misspoke. I was thinking of this ticket.

    https://github.com/androidx/media/issues/1895

    But this appears to be a mediatek specific issue. The TCL TV the OP has is using a realtek chipset.
    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