Hardware acceleration with PGS subtitles hangs indefinitely #1636

Closed
opened 2026-02-06 21:12:20 +03:00 by OVERLORD · 13 comments
Owner

Originally created by @mholt on GitHub (May 2, 2020).

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):

[matroska,webm @ 0x1b92af0] Stream #5: not enough frames to estimate rate; consider increasing probesize
[matroska,webm @ 0x1b92af0] Could not find codec parameters for stream 3 (Subtitle: hdmv_pgs_subtitle (pgssub)): unspecified size
Consider increasing the value for the 'analyzeduration' and 'probesize' options
  • One issue is that the video doesn't play at all
  • Another issue might be those errors

System (please complete the following information):

  • OS: MacOS (server is running on Linux, Raspbian, Raspberry Pi 4)
  • Virtualization: none
  • Clients: Browser, Android
  • Browser: Firefox 75
  • Jellyfin Version: 10.5.5
  • Playback: Transcode, I think?
  • Installed Plugins: none
  • Reverse Proxy: Caddy
  • Base URL: /
  • Networking: Host? Just a regular LAN
  • Storage: local

To Reproduce

  1. Enable the OMX hardware acceleration on Raspberry Pi
  2. Get a mkv file with PGS subtitles that need to be burned in (I don't really know how this works -- MP4s with soft subs don't have this problem)
  3. Enable a subtitle track before playing
  4. Play the file

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!

Originally created by @mholt on GitHub (May 2, 2020). **Describe the bug** <!-- A clear and concise description of what the bug is. --> 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](https://www.reddit.com/r/jellyfin/comments/g8ox3j/hardware_acceleration_on_raspberry_pi_4_not/for798a/?context=8&depth=9) 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): ``` [matroska,webm @ 0x1b92af0] Stream #5: not enough frames to estimate rate; consider increasing probesize [matroska,webm @ 0x1b92af0] Could not find codec parameters for stream 3 (Subtitle: hdmv_pgs_subtitle (pgssub)): unspecified size Consider increasing the value for the 'analyzeduration' and 'probesize' options ``` - One issue is that the video doesn't play at all - Another issue might be those errors **System (please complete the following information):** - OS: MacOS (server is running on Linux, Raspbian, Raspberry Pi 4) - Virtualization: none - Clients: Browser, Android - Browser: Firefox 75 - Jellyfin Version: 10.5.5 - Playback: Transcode, I think? - Installed Plugins: none - Reverse Proxy: Caddy - Base URL: / - Networking: Host? Just a regular LAN - Storage: local **To Reproduce** <!-- Steps to reproduce the behavior: --> 0. [Enable the OMX hardware acceleration on Raspberry Pi](https://jellyfin.org/docs/general/administration/hardware-acceleration.html#raspberry-pi-3-and-4) 1. Get a mkv file with PGS subtitles that need to be burned in (I don't really know how this works -- MP4s with soft subs don't have this problem) 2. Enable a subtitle track before playing 3. Play the file **Expected behavior** <!-- A clear and concise description of what you expected to happen. --> 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** <!-- Please paste any log errors. --> See logs from both a working stream (no subs) and non-working stream (with subs) here: https://gist.github.com/mholt/1511cf85f8ca983bdd6ddd93ba430e07 **Screenshots** <!-- If applicable, add screenshots to help explain your problem. --> n/a **Additional context** <!-- Add any other context about the problem here. --> 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!
OVERLORD added the bug label 2026-02-06 21:12:20 +03:00
Author
Owner

@stale[bot] commented on GitHub (Aug 30, 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.

@stale[bot] commented on GitHub (Aug 30, 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](https://docs.jellyfin.org/general/getting-help.html).
Author
Owner

@mholt commented on GitHub (Aug 30, 2020):

Oh nooooo don't close it 😭

@mholt commented on GitHub (Aug 30, 2020): Oh nooooo don't close it 😭
Author
Owner

@stale[bot] commented on GitHub (Dec 28, 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.

@stale[bot] commented on GitHub (Dec 28, 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](https://docs.jellyfin.org/general/getting-help.html).
Author
Owner

@mholt commented on GitHub (Dec 28, 2020):

I am not aware that this is fixed; please leave open.

@mholt commented on GitHub (Dec 28, 2020): I am not aware that this is fixed; please leave open.
Author
Owner

@stale[bot] commented on GitHub (Jun 3, 2021):

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.

@stale[bot] commented on GitHub (Jun 3, 2021): 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](https://docs.jellyfin.org/general/getting-help.html).
Author
Owner

@mholt commented on GitHub (Jun 4, 2021):

Not fixed yet.

@mholt commented on GitHub (Jun 4, 2021): Not fixed yet.
Author
Owner

@sparky002 commented on GitHub (Jun 19, 2021):

I get the same error although I'm not using a raspi. Using the latest Jellyfin docker on Unraid with gpu acceleration on.

@sparky002 commented on GitHub (Jun 19, 2021): I get the same error although I'm not using a raspi. Using the latest Jellyfin docker on Unraid with gpu acceleration on.
Author
Owner

@nyanmisaka commented on GitHub (Jun 18, 2022):

Not an issue. The processor of RPI4 cannot handle subtitle burn-in.

@nyanmisaka commented on GitHub (Jun 18, 2022): Not an issue. The processor of RPI4 cannot handle subtitle burn-in.
Author
Owner

@mholt commented on GitHub (Jun 18, 2022):

Sorry, but what do you mean, it "cannot handle" it?

@mholt commented on GitHub (Jun 18, 2022): Sorry, but what do you mean, it "cannot handle" it?
Author
Owner

@nyanmisaka commented on GitHub (Jun 18, 2022):

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.

@nyanmisaka commented on GitHub (Jun 18, 2022): 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.
Author
Owner

@mholt commented on GitHub (Jun 18, 2022):

Can the GPU perform this?

@mholt commented on GitHub (Jun 18, 2022): Can the GPU perform this?
Author
Owner

@nyanmisaka commented on GitHub (Jun 18, 2022):

GPU scaling filter hasn’t been implemented yet, not to mention the GPU overlay filter.
https://github.com/jc-kynesim/rpi-ffmpeg/issues/42

@nyanmisaka commented on GitHub (Jun 18, 2022): GPU scaling filter hasn’t been implemented yet, not to mention the GPU overlay filter. https://github.com/jc-kynesim/rpi-ffmpeg/issues/42
Author
Owner

@EliteElectronic commented on GitHub (Jan 5, 2023):

With hardware acceleration enabled, I found PGS Subtitles ONLY work on the Jellyfin Media Player APP Windows version.
All others does not work! I also tried Jellyfin Media Player APP on Roku DOES NOT work.
Why only Jellyfin Media Player APP Windows version work ??? !!!
My main player is Jellyfin Media Player APP on Roku and all of my movies are Bluray rip with PGS Subtitles.
Jellyfin team, please look into this and make hardware acceleration PGS Subtitles work everywhere !
Thank you !!!

@EliteElectronic commented on GitHub (Jan 5, 2023): With hardware acceleration enabled, I found PGS Subtitles ONLY work on the Jellyfin Media Player APP Windows version. All others does not work! I also tried Jellyfin Media Player APP on Roku DOES NOT work. Why only Jellyfin Media Player APP Windows version work ??? !!! My main player is Jellyfin Media Player APP on Roku and all of my movies are Bluray rip with PGS Subtitles. Jellyfin team, please look into this and make hardware acceleration PGS Subtitles work everywhere ! Thank you !!!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/jellyfin#1636