-
-
Notifications
You must be signed in to change notification settings - Fork 68
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
subtitles bug #267
Comments
I was able to reproduce this 1:1. If I extract the ASS subtitles and add the subtitles again with MKVToolNix, remove the old ones and create the file again, the subtitles work in the browser and on the LG TV with the app from the LG Store. It is apparently the same error as the one I linked to. |
It broke for me ever since I updated the server to version 10.10 |
Don't know if I'm writing in the right place, maybe this should be under jellyfin-ffmpeg.
|
As I wrote above, the problem is solved by manually extracting the ASS subtitles and adding them without changing them with the MKVTool and recreating the file. For a large collection, this would mean, in my case, several 10,000 files that would have to be edited manually although it was once fixed and worked. With the update to version 10 this was broken again. To be honest, I have no desire to edit 10,000+ files manually as there is obviously another way. If this is the wrong section, I would ask you to move this so that the error can be addressed. Thank you |
Hello,
something has been changed in the last updates. Two years ago I had the problem that ASS subtitles were not displayed in the browser and on my LG OLED. But they did in the desktop app. When I then extracted the subtitles with gMKVExtractGUI and remuxed them with MKVToolNix, it suddenly worked. Then something was changed during an update and the subtitles worked normally. Now files with subtitles created with HandBrake no longer work without extracting the subtitles and recreating the file.
What has happened?
Here is the old post: #143
The fix was this: jellyfin/jellyfin#9344
But now it's back?!
The text was updated successfully, but these errors were encountered: