• 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 Live TV w/DLNA creates high bit rates

     
    • 0 Vote(s) - 0 Average

    Live TV w/DLNA creates high bit rates

    Live TV over DLNA w/QSV creates high bitrates of 140Mbps and overloads clients / server
    jmoney
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Mar
    Reputation: 0
    #1
    2025-03-04, 10:39 PM (This post was last modified: 2025-03-05, 08:12 AM by jmoney. Edited 1 time in total.)
    I'm encountering an issue playing live TV (iptv) over DLNA when QSV transcoding is enabled.  Client used is VLC / upnp and selecting a channel will cause stuttering on older devices.  It appears the bitrate is being converted from 8Mbps to 140Mbps.  If I enable VAAPI transcoding, then the bitrate is 4-5 Mbps, but I'd rather leverage the hardware transcoding of QSV.  QSV works fine for other transcodes but for some reason playing LiveTV over DLNA forces transcoding and creates these high bitrates.  Anyone seen this issue or have a workaround?

    Ideally I'd prefer not to transcode live TV over DLNA but I haven't been able to disable this.  I have a few older Android tablets that don't play nice with the Jellyfin app but DLNA works fine.

    Any help is greatly appreciated! Thanks.
    jmoney
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Mar
    Reputation: 0
    #2
    2025-03-05, 07:42 AM
    Just an update -- seems that Jellyfin uses an extremely high bitrate (139808000) when streaming live TV over DLNA with QSV per this command: -low_power 1 -preset veryfast -b:v 139808000 -maxrate 139808000 -bufsize 279616000

    The b:v flag is not used when VAAPI or None is selected for transcoding. The network adapter on the server shows that it is taking an 8Mbps stream and sending 140Mbps to the client and creating a 140Mbps .ts file in the transcode directory. Definitely looks like a bug with Jellyfin since I'm using the latest server version and latest Intel GPU drivers.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #3
    2025-03-05, 04:46 PM
    Do you have a reverse proxy handling client connections?
    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]
    jmoney
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Mar
    Reputation: 0
    #4
    2025-03-05, 06:26 PM
    No, m3u file is handled directly in Jellyfin. QSV is the only encoder that this happens with though. VAAPI or none does not expand the stream from 8Mbps to 140Mps like QSV is doing. This also has the effect of creating a 140Mbps .ts file in the transcode directory.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #5
    2025-03-05, 07:13 PM
    I'm talking about something like Nginx handling https connections. Not a proxy for the live TV stream.

    I've only seen the issue you are describing when someone was using Nginx with caching enabled. Specifically with QSV transcoding, in general.
    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]
    jmoney
    Offline

    Junior Member

    Posts: 4
    Threads: 1
    Joined: 2025 Mar
    Reputation: 0
    #6
    2025-03-06, 04:15 AM
    No, not using Nginx or anything similar. Basic setup. QSV works fine for every other type of transcode and in regular TV where I can manually set the bitrate in the jellyfin app. For some reason DLNA is setting the bitrate to 140Mbps for just Live TV which most of the clients can't handle and it also creates a 140Mbps transcode file. Looks like a bug though.
    TheDreadPirate
    Offline

    Community Moderator

    Posts: 15,374
    Threads: 10
    Joined: 2023 Jun
    Reputation: 460
    Country:United States
    #7
    2025-03-06, 02:09 PM
    Very likely is a bug. I see you already submitted a github issue.
    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