-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Issue]: Transcoding job killed before playback starts. #11640
Comments
Hi, it seems like your issue report has the following item(s) that need to be addressed:
This is an automated message, currently under testing. Please file an issue here if you encounter any problems. |
Full logs were too long for the template, attached here: |
Summarized timeline:
|
It seems that if the job type is not jellyfin/MediaBrowser.MediaEncoding/Transcoding/TranscodeManager.cs Lines 150 to 155 in 69d4886
Is it timing out just before the ping? If the timeout is 10s is it timing out as the ping is in flight? If the ping interval is 10s the timeout should probably be at least 20s, I would go with 60-120s. If the timeout should stay 10s the ping interval should probably be brought down to 1 or 2s. |
Possibly related issues: |
#11643 resolves the timeout issue which is the main problem mentioned. However it still didn't start playing even when the transcoding completed. But I guess that is another bug. |
Please describe your bug
When playing a transcoded video on a chromecast the ffmpeg process is killed before the video starts playing.
Reproduction Steps
Jellyfin Version
10.9.0
if other:
10.9.1
Environment
Jellyfin logs
FFmpeg logs
Please attach any browser or client logs here
No response
Please attach any screenshots here
TV screen stays black.
Code of Conduct
The text was updated successfully, but these errors were encountered: