mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Direct streaming really slow, transcoding keeps stopping #3248
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 @ekaprayugo on GitHub (Sep 16, 2021).
I noticed that when I play something from my iPhone, it takes very long for it to start (~1-2 minutes), sometimes it doesn't even start at all.
From what I can see in the log, looks like it's trying to transcode audio (eac3->aac)
In jellyfin log, looks like something keeps stopping the ffmpeg process:
full log is attached below.
Eventually though, it runs successfully and then the video starts playing fine, until I skip forward, and it triggers the same death loop again.
I also tried playing the video from an Android phone, and it has exact same issue.
Any suggestions?
Media Info of the file
Logs
FFmpeg Logs
FFmpeg log is generated for everytime new
ffmpegprocess starts, this is just one of the log where it is stopped early.Server System:
Client System (please complete the following information):
@Artiume commented on GitHub (Sep 25, 2021):
I'm going to go on the assumption that it's specific to eac3 5.1, check other formats just to be sure. The eac3 5.1 audio has Atmos metadata. Can you see if you can reproduce the issue on an eac3 5.1 file without Atmos. Also check eac3 stereo.
@jellyfin-bot commented on GitHub (Jan 31, 2022):
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 master branch, 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.