mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
10.10.0 latest build. QSV transcoding fails #6262
Reference in New Issue
Block a user
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?
Originally created by @soultaco83 on GitHub (Sep 12, 2024).
This issue respects the following points:
Description of the bug
I have just completed building the lastest version of jellyfin for version 10.10.0.
Since this lastest pull I am unable to use the QSV transcoding option. All video files that require transcoding fail.
To note: Remux and direct are fine. Just the transcodes
I am also unable to select None as my Hardware acceleration choice as I get the following message on save:
There was an error processing the request. Please try again later.
As of the build I have that last commit was
751e12e5b5I am able to proceed without issue via Vappi and selecting /dev/dri/renderD128 as my render device
Reproduction steps
1: Navigate to Dashboard
2: select Playback>Transcoding
3: If already on Intel Quicksync press save
4: Attempt a video transcode.
What is the current bug behavior?
Transcode fails with
Playback Error
Playback failed due to a fatal player error.
What is the expected correct behavior?
Video to transcode without failure
Jellyfin Server version
Master
Specify commit id
751e12e5b5Specify unstable release number
No response
Specify version number
No response
Specify the build version
Build version Release
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
Network console from chrome on save of none.log
Unable to save none
Relevant screenshots or videos
error when saving none

Error on qsv transcoding

Additional information
FFmpeg.Transcode-2024-09-11_22-29-03_66a0bbdce663c8d85e2ac7ba7d6481fa_1c0968db.log
FFmpeg.Transcode-2024-09-11_22-29-03_66a0bbdce663c8d85e2ac7ba7d6481fa_a0578372.log
FFmpeg.Transcode-2024-09-11_22-29-03_66a0bbdce663c8d85e2ac7ba7d6481fa_ee8ea73d.log
log_20240911.log
Network console from chrome on save of none.log
@gnattu commented on GitHub (Sep 12, 2024):
This is just unstable being unstable. The config issue is that the server major (breaking) change that requires the web to change accordingly not being merged yet, your ffmpeg failure is that the pipeline is generating wrong cli, needs investigation
@nyanmisaka commented on GitHub (Sep 12, 2024):
As a workaround, select veryfast instead of Auto in Dashboard->Playback->Preset.
@soultaco83 commented on GitHub (Sep 12, 2024):
@gnattu Thanks I figured it was just it being weird
@nyanmisaka I can confirm setting it from auto to Veryfast for now resolves the transcoding issue