-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Hardware acceleration with PGS subtitles hangs indefinitely #3028
Comments
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. |
Oh nooooo don't close it 😭 |
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. |
I am not aware that this is fixed; please leave open. |
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. |
Not fixed yet. |
I get the same error although I'm not using a raspi. Using the latest Jellyfin docker on Unraid with gpu acceleration on. |
Not an issue. The processor of RPI4 cannot handle subtitle burn-in. |
Sorry, but what do you mean, it "cannot handle" it? |
Software based subtitle burn-in is a cpu intensive task even for x86, the cpu of Pi4 is not fast enough to do it on the fly. |
Can the GPU perform this? |
GPU scaling filter hasn’t been implemented yet, not to mention the GPU overlay filter. |
Describe the bug
I think there are 2 issues here, but I'll just post the info I know and let you decide! :)
Initiated from this reddit thread which has a little more background.
Hardware-accelerated encoding of a stream with PGS subtitles hangs indefinitely on Raspberry Pi 4. After disabling subtitles, stream works fine, but there's still an error in the logs either way (appears a couple times):
System (please complete the following information):
To Reproduce
Expected behavior
The video should play, I suppose. And from that reddit thread, the other commenter helping me said that the "unspecified size" logs should not happen either, like a bug that was thought to have been fixed already. That might be a separate issue, not sure.
Logs
See logs from both a working stream (no subs) and non-working stream (with subs) here: https://gist.github.com/mholt/1511cf85f8ca983bdd6ddd93ba430e07
Screenshots
n/a
Additional context
When subs are enabled, it's just a black screen forever, and the web UI kinda freezes and I have to reload it to go back.
Let me know what other information you need!
The text was updated successfully, but these errors were encountered: