mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Transcoding issues after upgrading Jellyfin to 10.10.1 #6444
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 @namankanakiya on GitHub (Nov 9, 2024).
This issue respects the following points:
Description of the bug
After upgrading to version 10.10.1, I've been running into transcoding issues. Any time the server needs to transcode (as is usually the case when there are files with subtitles), the video has artifacts, doubled subtitles, sometimes freezes (while the audio continues to play), is out of sync, sometimes repeats the audio
Reproduction steps
Play any video that causes transcoding
What is the current bug behavior?
Video has artifacts, doubled subtitles, sometimes freezes (while the audio continues to play), is out of sync, sometimes repeats the audio
What is the expected correct behavior?
Plays smoothly
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.10.1
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
No response
Relevant screenshots or videos
Additional information
ffmpegLog.txt
@namankanakiya commented on GitHub (Nov 11, 2024):
This ended up being an issue with the backing NAS - I noticed from the logs above:
Element at 0x57e99ec ending at 0xe484722 exceeds containing master element ending at 0x58439c6Looking that up, it seemed like the file itself was corrupted. I did a a ffprobe to see if it was so:
ffprobe -v error "filename"This came back with the same errors that I saw in the log, confirming the theory.
My setup involved copying the file from one folder into the jellyfin folder - I noticed that I could play the original file with no issues, but the copied file had issues. Subsequently, I did a
sha256sum to check if both were the same - it turned out that copying the file was somehow corrupting the copied files - the hashes were different.After debugging the NAS, applying some updates etc, got back to normal behavior!