mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
ffmpeg breaks when playing video with external subs on Roku client #3932
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 @helpimnotdrowning on GitHub (Jun 15, 2022).
Media Info of the file
Video:
Audio:
Subtitles:
Logs
FFmpeg Logs
Server System (please complete the following information):
Client System (please complete the following information):
Additional
Is almost definitley related to #7580.
I discovered that changing the
-map 2:0to-map 1:0in the ffmpeg command and running it manually completes succesfully. I think that jellyfin thinks the audio stream is stream 2 because it thinks that the subtitles are stream 1 even though they are passed via a filter? (I have all subs burned in for therokuuser because no video plays when it has soft subs, "an unexpected error occured" (or something like that), but that's a different issue I should make later.)This issue does not affect the web client or offical Android client.
I noticed that even though my server had updated to 10.8.0, the bundled ffmpeg version was still the same (not updated to 5.0.1, I updated it manually yesterday by unzipping the 5.0.1-5 windows release from https://github.com/jellyfin/jellyfin-ffmpeg into the server directory). Could this mean that only some files/parts of jellyfin were updated, and others (like the file patched in #7580) weren't, causing the server to report version 10.8.0 even though some files were (probably) stuck in write-lock limbo (or something like that) and not updated alongside everything else?
@nyanmisaka commented on GitHub (Jun 15, 2022):
Should be fixed by the PR linked above.
@helpimnotdrowning commented on GitHub (Jun 15, 2022):
I fixed it by running the 10.8.0 stable installer. Even thought the webui said it was running version 10.8.0, it seems like it wasn't actually 10.8.0 (maybe it was one of the unstable builds?).
(also, I was under the assumption there was an auto-updater (I probably misread something), but after looking into it more it seems there never was one in the first place.)
@nyanmisaka commented on GitHub (Jun 15, 2022):
Thanks anyway. The #7580 is only a partial fix but it should cover most cases.