mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-03-01 03:16:51 +03:00
FFMPEG transcoding error + workaround #680
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 @platinum55 on GitHub (May 10, 2019).
Describe the bug
Some mkv files fail to transcode/stream because of this bug:
https://trac.ffmpeg.org/ticket/6472
Jellyfin just stalls in the loading screen because of the ffmpeg process exits with returncode 1.
I tried the workaround which is posted in the ffmpeg tracker "-max_muxing_queue_size 198" - which is working, transcode runs!
Please implement this parameter until the ffmpeg bug is fixed
System:
@johnvick commented on GitHub (Jun 23, 2019):
Can you please explain how to do this? It looks like it may solve my problem. Thanks.
@platinum55 commented on GitHub (Jun 23, 2019):
how to do what? I requested something here
@johnvick commented on GitHub (Jun 23, 2019):
How do you implement the workaround -max_muxing_queue_size 198?
I can't see any way to input these command line parameters. I'm trying to get transcoding to work but it stops with ffmpeg error 1.
@platinum55 commented on GitHub (Jun 23, 2019):
I dont know, thats why I asked here. You need to modify to source I guess.
@stale[bot] commented on GitHub (Sep 25, 2019):
Issues go stale after 90d of inactivity. Mark the issue as fresh by adding a comment or commit. Stale issues close after an additional 14d of inactivity. If this issue is safe to close now please do so. If you have any questions you can reach us on Matrix or Social Media.
@platinum55 commented on GitHub (Oct 14, 2019):
this bug still exists in version 10.4.0 - maybe we can just detect the error message from ffmpeg:
Too many packets buffered for output stream 0:0. Conversion failed!and then start the encode with the option "-max_muxing_queue_size 198"
@stale[bot] commented on GitHub (Feb 12, 2020):
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or nightlies, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.
This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.
@ManuLinares commented on GitHub (Aug 24, 2020):
This issue is still happening. I dont know where to add "-max_muxing_queue_size 1024"
@jeremyj commented on GitHub (Nov 27, 2020):
same here
@pxlvoid commented on GitHub (Jan 31, 2022):
same problem
@cvium commented on GitHub (Jan 31, 2022):
This issue has been closed for almost 2 years... Please don't necro post. Also https://github.com/jellyfin/jellyfin/pull/3976 and https://github.com/jellyfin/jellyfin-web/pull/1842