• 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 Development Feature Requests Automatic hardware encoding settings by architecture

     
    • 0 Vote(s) - 0 Average

    Automatic hardware encoding settings by architecture

    tknx
    Offline

    Junior Member

    Posts: 7
    Threads: 3
    Joined: 2023 Jun
    Reputation: 0
    #1
    2025-03-12, 05:32 PM
    It would be nice if I could just have Jellyfin see that I am using an Intel Rocket Lake and prepopulate a good set of default hardware encoding settings instead of making me go back and forth with the Wikipedia article and try to map that to the settings.

    It would require a bit of database work to map what is supported by each GPU, but would make setup a lot easier and avoid incompatibilities.

    In addition, the mapping could be more exact, in my example, Rocket Lake for HEVC only supports encoding at 4:2:0 only and does not support AVC High 10, but there doesnt seem to be a way to get that granular in the settings.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #2
    2025-03-12, 08:05 PM
    The problem is that even within a generation of CPUs/GPUs there are inconsistencies. AMD and Nvidia are the bigger offenders. Intel is pretty consistent, but there are still exceptions. So having a static mapping would require a lot of work and validation.

    Even using vainfo to attempt to get a GPUs codec support is not a guaranteed way the get the full picture.

    Since we are not a for-profit business, we don't have dozens of test benches with various hardware combinations to validate this kind of capability.

    Having said that, there are efforts to figure out an acceptably reliable way of doing this. No ETA.
    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]
    tknx
    Offline

    Junior Member

    Posts: 7
    Threads: 3
    Joined: 2023 Jun
    Reputation: 0
    #3
    2025-03-15, 10:56 PM
    Yeah, I think there are a couple of ways to do it.

    Maybe the most dev heavy way would be to run suites on each processor to test encoding and decoding and then catalog the success and failures for that specific architecture.

    The other might be something like the other post where you were helping me out and just say, okay for Rocket Lake these are the defaults and if people want to mess with them, fine. And then add in architectures as they are validated.

    But I recognize it is a pain in the ass no matter what, especially if AMD and others aren't providing the exact specs easily. Would the ffmpeg group or someone already have this? I feel like someone would...
    « Next Oldest | Next Newest »

    Users browsing this thread: 4 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