2024-04-23, 05:11 PM
(This post was last modified: 2024-04-23, 05:20 PM by besenwesen. Edited 2 times in total.)
The 'docker logs $containername' command returns nothing useful. Are there debug logs or something more verbose that is stored in the container?
When clicking "Media Info" in the media overview, it does not show the subtitle information (in contrast to the video that shows the subtitles), even after rescanning.
The subtitle codec you are referring to is called 'ass'. I therefore used mov_text. ffmpeg does not allow 'transcoding' a subtitle codec into a container that does not support it. At least the ffmpeg version i am using.
When clicking "Media Info" in the media overview, it does not show the subtitle information (in contrast to the video that shows the subtitles), even after rescanning.
(2024-04-23, 05:07 PM)FactoriedMyAuth Wrote: Does this only happen with your .mp4 files?
I ran into a similar issue when I started transcoding my files. If you are doing a transcode from a .mkv container with embeded subtitles to a .mp4 container, the subtitle type matters. I don't remember what the type is called that most blu-rays and 4k movies use, but it's incompatible with the .mp4 container.
You will either end up transcoding and having the subtitles forcibly baked into the video or not there at all. If you transcode and add an external .srt subtitle file (and set it to not forced), it will be selectable in your final video.
The subtitle codec you are referring to is called 'ass'. I therefore used mov_text. ffmpeg does not allow 'transcoding' a subtitle codec into a container that does not support it. At least the ffmpeg version i am using.