• 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 Ubuntu Server 22.04 ESXi Virtual with GPU passthrough

     
    • 0 Vote(s) - 0 Average

    Ubuntu Server 22.04 ESXi Virtual with GPU passthrough

    GPU passthrough on ESXi ubuntu server not working
    digitaltrance
    Offline

    Junior Member

    Posts: 10
    Threads: 1
    Joined: 2023 Oct
    Reputation: 0
    Country:United States
    #1
    2023-10-21, 06:40 PM
    Hello all,

    New here, I am coming from Plex looking to abandon that ship.

    I got Jellyfin running on ESXi Virtual Machine - Ubuntu Server 22.04
    I have a Nvidia Quadro P2000 that I want to use as the hardware accelerator. Got all the nvidia/cuda drivers/toolkits installed but still not seeing Jellyfin utilize the GPU.

    When I do nvidia-smi while playback, I don't see any Jellyfin processes in use (see attached).

    This works fine on Plex, so I would think this shouldn't be a problem.

    Am I missing anything on the settings for Jellyfin within the GUI?

    Thanks in advance!

       
    Deleted User

    Unregistered
     
    #2
    2023-10-21, 06:44 PM
    check the jellyfin web panel dashboard, under logs and see if there is an ffmpeg log - this will typically only appear during transcoding

    if it exists, it should show what methods were used - direct copy, hardware accel, etc.

    the rest of the settings are in the web panel dashboard under Playback
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #3
    2023-10-21, 07:09 PM
    Jellyfin will only use the GPU when transcoding video. If you're seeing CPU transcoding, make sure that you setup hardware acceleration in the playback dashboard.
    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]
    digitaltrance
    Offline

    Junior Member

    Posts: 10
    Threads: 1
    Joined: 2023 Oct
    Reputation: 0
    Country:United States
    #4
    2023-10-21, 07:17 PM (This post was last modified: 2023-10-21, 07:22 PM by digitaltrance. Edited 3 times in total.)
    Ah, yes there it goes. I was needing to select the NVIDIA hardware within the playback settings. I see it being used now.

    Is there a reason some file types it would use direct copy instead of hardware even through the format is selected to use hardware?

    EDIT: sorry that last question, I think I answered myself. that is for DEcoding, not transcoding.
    Deleted User

    Unregistered
     
    #5
    2023-10-21, 07:26 PM
    (2023-10-21, 07:17 PM)digitaltrance Wrote: Ah, yes there it goes. I was needing to select the NVIDIA hardware within the playback settings.

    Is there a reason some file types it would use direct copy instead of hardware even through the format is selected to use hardware?

    EDIT: sorry that last question, I think I answered myself. that is for DEcoding, not transcoding.

    to answer the initial question, whether or not self-answered

    what it decides to transcode vs direct stream depends on the client settings (user settings)

    if the source video is 4K and the user max resolution is 4K and the bitrate is less than the max bitrate - it will serve it up directly, nothing the server needs to do

    same for codec, if hevc is accepted then direct, if not transcode to avc

    audio too, client determines it cannot play DTS so DTS gets transcoded to something compatible


    note not all of the user settings are implemented into all of the clients so you may observe in the web player it transcodes because the web player has the setting
    - but in the android app there is no setting to tell the server to transcode all DTS to DD+ so the client receives DTS anyway
    digitaltrance
    Offline

    Junior Member

    Posts: 10
    Threads: 1
    Joined: 2023 Oct
    Reputation: 0
    Country:United States
    #6
    2023-10-21, 07:40 PM
    (2023-10-21, 07:26 PM)000 Wrote:
    (2023-10-21, 07:17 PM)digitaltrance Wrote: Ah, yes there it goes. I was needing to select the NVIDIA hardware within the playback settings.

    Is there a reason some file types it would use direct copy instead of hardware even through the format is selected to use hardware?

    EDIT: sorry that last question, I think I answered myself. that is for DEcoding, not transcoding.

    to answer the initial question, whether or not self-answered

    what it decides to transcode vs direct stream depends on the client settings (user settings)

    if the source video is 4K and the user max resolution is 4K and the bitrate is less than the max bitrate - it will serve it up directly, nothing the server needs to do

    same for codec, if hevc is accepted then direct, if not transcode to avc

    audio too, client determines it cannot play DTS so DTS gets transcoded to something compatible


    note not all of the user settings are implemented into all of the clients so you may observe in the web player it transcodes because the web player has the setting
    - but in the android app there is no setting to tell the server to transcode all DTS to DD+ so the client receives DTS anyway


    Perfect, yes, that makes 100% sense!

    Thanks to both for your help!
    « Next Oldest | Next Newest »

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