-
-
Notifications
You must be signed in to change notification settings - Fork 472
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
Since 0.17: Player erroring after trying to DirectPlay media with (presumably) unsupported ASS subtitles #3898
Comments
Any ffmpeg logs? |
I included them but they're long so I added a link: |
There was some changes for HEVC, I wonder if that is what's causing the errors. Going to |
Thanks! Here are my settings. |
Note for others seeing this: my workaround for now is to set my default bitrate super low (like below 1mbps for anime) to force transcoding, which then lets me select the subtitles causing them to burn in as expected. I can then turn the bitrate back up. |
i'm pretty sure this was the issue I am facing #3913 Rollback to 0.16.11 client and set player to LibVLC, see if it works for you |
I'm no longer experiencing this since #3916 When a subtitle codec is unsupported, the video is transcoding as expected now. |
Describe the bug
This seems to have started since the 0.17 update.
In the past these were always burned in because the codec isn't supported on my Android TV device (special fonts? I guess?). By the logs it seems like they're trying to direct play now.
As far as I know there isn't a way for me to just choose SRT subs before the media begins playing.
Web and web wrapper clients work fine. This is happening on two different "Chromecast with Google TV" devices.
It also seems that if I start the episode on another device, then resume from the ATV, it works.
Logs
App:
Container:
FFmpeg logs
https://pastebin.com/aQYU2Lb6
Media info of the file
Application version
0.17.3
Device information
Chromecast with Google TV 4K
Android version
Android 13
Jellyfin server version
10.9.9
The text was updated successfully, but these errors were encountered: