starred/jellyfin
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.git synced 2026-05-04 18:09:12 +03:00
Code Issues 822 Packages Projects Releases 10 Wiki Activity

[help] Poor Transcode Performance on DS423+ using JF with Intel QSV transcoding one stream #5296

New Issue
Closed
opened 2026-02-07 01:39:56 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-07 01:39:56 +03:00
Owner
Copy Link

Originally created by @bradleycundari on GitHub (Dec 7, 2023).

Media Info of the file
info

Stats for Nerds Screenshots
system usage

Server System (please complete the following information):

  • OS: Docker on Linux/Synology
  • Jellyfin Version: Latest on Linux Server Image
  • Hardware settings & device: intel qsv
  • Reverse proxy: synology reverse proxy
  • Other hardware notes:
DS423+ expanded RAM with 16gb CT16G4SFRA266
Volume 1: 18TBx4 Seagate Exos X20 ST180000NM003D
Volume 1 Read Only Cache: 4 TB - TEAMGROUP MP 34 m.2
Volume 2: 4 TB - TEAMGROUP MP34 m.2

Client System (please complete the following information):

  • Device: LG B2
  • OS: LGOS
  • Client: JellyFin
    Poor performance regardless of client

Container params:

services:
 jellyfin:
   image: linuxserver/jellyfin:latest
   container_name: jellyfin
   environment:
     - PUID=1028 #CHANGE_TO_YOUR_UID
     - PGID=65536 #CHANGE_TO_YOUR_GID
     - TZ=America/New_York #CHANGE_TO_YOUR_TZ
     - UMASK=022
     - JELLYFIN_PublishedServerUrl=192.168.0.119
   volumes:
     - /volume2/docker/jellyfin:/config
     - /volume1/data/media:/data/media
   devices:
     - /dev/dri/renderD128:/dev/dri/renderD128
     - /dev/dri/card0:/dev/dri/card0
   ports:
     - 8096:8096 #web port
     - 8920:8920 #optional
     - 7359:7359/udp #optional
   network_mode: synobridge
   security_opt:
     - no-new-privileges:true
   restart: always
Originally created by @bradleycundari on GitHub (Dec 7, 2023). **Media Info of the file** ![info](https://github.com/jellyfin/jellyfin/assets/8679059/ef9e21ca-908f-4216-9570-6a8b7bfb1933) **Stats for Nerds Screenshots** ![system usage](https://github.com/jellyfin/jellyfin/assets/8679059/9c061677-86c4-42c8-ba47-cd6ec5946117) **Server System (please complete the following information):** - OS: Docker on Linux/Synology - Jellyfin Version: Latest on Linux Server Image - Hardware settings & device: intel qsv - Reverse proxy: synology reverse proxy - Other hardware notes: ``` DS423+ expanded RAM with 16gb CT16G4SFRA266 Volume 1: 18TBx4 Seagate Exos X20 ST180000NM003D Volume 1 Read Only Cache: 4 TB - TEAMGROUP MP 34 m.2 Volume 2: 4 TB - TEAMGROUP MP34 m.2 ``` **Client System (please complete the following information):** - Device: LG B2 - OS: LGOS - Client: JellyFin Poor performance regardless of client Container params: ``` services: jellyfin: image: linuxserver/jellyfin:latest container_name: jellyfin environment: - PUID=1028 #CHANGE_TO_YOUR_UID - PGID=65536 #CHANGE_TO_YOUR_GID - TZ=America/New_York #CHANGE_TO_YOUR_TZ - UMASK=022 - JELLYFIN_PublishedServerUrl=192.168.0.119 volumes: - /volume2/docker/jellyfin:/config - /volume1/data/media:/data/media devices: - /dev/dri/renderD128:/dev/dri/renderD128 - /dev/dri/card0:/dev/dri/card0 ports: - 8096:8096 #web port - 8920:8920 #optional - 7359:7359/udp #optional network_mode: synobridge security_opt: - no-new-privileges:true restart: always ```
OVERLORD added the media playback label 2026-02-07 01:39:56 +03:00
OVERLORD commented 2026-02-07 01:39:59 +03:00
Author
Owner
Copy Link

@felix920506 commented on GitHub (Dec 7, 2023):

Hi, thanks for the report, 2 things here.

  1. You could avoid transcoding video altogether by enabling fMP4 containers in your client settings. (Assuming your device supports it, I don't own a LG TV so I don't know for sure)
  2. This looks like it is related to #1557
@felix920506 commented on GitHub (Dec 7, 2023): Hi, thanks for the report, 2 things here. 1. You could avoid transcoding video altogether by enabling fMP4 containers in your client settings. (Assuming your device supports it, I don't own a LG TV so I don't know for sure) 3. This looks like it is related to #1557
OVERLORD commented 2026-02-07 01:40:01 +03:00
Author
Owner
Copy Link

@bradleycundari commented on GitHub (Dec 7, 2023):

Hi, thanks for the report, 2 things here.

  1. You could avoid transcoding video altogether by enabling fMP4 containers in your client settings. (Assuming your device supports it, I don't own a LG TV so I don't know for sure)
  2. This looks like it is related to Setting too high of a bandwidth for ffmpeg trips up NVENC (and probably other hardware encoders) #1557

Hey Felix, thanks for the quick response. I hope I've provided enough debug info here, let me know if anything else would help.

I do try to direct play when possible, I stumbled into this issue when intentionally forcing transcodes when trying to validate my transcoding configuration for my server. I was assuming it was just misconfiguration on my part which I spent a long time trying to resolve.

It seems that at the moment there is no way to configure JF to resolve the linked issue right?

Thanks again!

@bradleycundari commented on GitHub (Dec 7, 2023): > Hi, thanks for the report, 2 things here. > > 1. You could avoid transcoding video altogether by enabling fMP4 containers in your client settings. (Assuming your device supports it, I don't own a LG TV so I don't know for sure) > 2. This looks like it is related to [Setting too high of a bandwidth for ffmpeg trips up NVENC (and probably other hardware encoders) #1557](https://github.com/jellyfin/jellyfin/issues/1557) Hey Felix, thanks for the quick response. I hope I've provided enough debug info here, let me know if anything else would help. I do try to direct play when possible, I stumbled into this issue when intentionally forcing transcodes when trying to validate my transcoding configuration for my server. I was assuming it was just misconfiguration on my part which I spent a long time trying to resolve. It seems that at the moment there is no way to configure JF to resolve the linked issue right? Thanks again!
OVERLORD commented 2026-02-07 01:40:02 +03:00
Author
Owner
Copy Link

@felix920506 commented on GitHub (Dec 7, 2023):

There is a "workaround" that can be annoying, which is to manually set the quality to a lower setting (such as 30mbps) in the player every time you play something. This might not work on some devices though.

From the standpoint of the code, it is "working as intended", which is to use a ~70% higher bitrate than source when converting HEVC to H264. Some hardware (Such as Intel Arc GPUs) is able to handle this kind of heavy load on the media engine. However this may not be the case for lower end devices. Under this situation, transcoding might outright fail on some devices while others will simply run at a slower (less than real time) speed.

@felix920506 commented on GitHub (Dec 7, 2023): There is a "workaround" that can be annoying, which is to manually set the quality to a lower setting (such as 30mbps) in the player every time you play something. This might not work on some devices though. From the standpoint of the code, it is "working as intended", which is to use a ~70% higher bitrate than source when converting HEVC to H264. Some hardware (Such as Intel Arc GPUs) is able to handle this kind of heavy load on the media engine. However this may not be the case for lower end devices. Under this situation, transcoding might outright fail on some devices while others will simply run at a slower (less than real time) speed.
OVERLORD commented 2026-02-07 01:40:04 +03:00
Author
Owner
Copy Link

@sevenrats commented on GitHub (Dec 8, 2023):

Hey, thanks for this report. This is not a bug. Please request support in the forum or the chat spaces. Thanks!

@sevenrats commented on GitHub (Dec 8, 2023): Hey, thanks for this report. This is not a bug. Please request support in the forum or the chat spaces. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
EFjellyfin.db
area:database
awaiting-feedback
backend
blocked
breaking change: web api
bug
build
ci
confirmed
discussion needed
dotnet future
downstream
duplicate
enhancement
feature
future
github-actions
good first issue
hdr
help wanted
invalid
investigation
librarydb
live-tv
lyrics
media playback
music
needs testing
nuget
performance
platform
pull-request
Mirrored from GitHub Pull Request
 question
regression
release critical
requires-web
roadmap
security
security
stale
support
syncplay
ui & ux
upstream
wontfix
No Label media playback
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#5296
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?