I have come across a weird problem with subtitles on the Nvidia Shield. Here is what’s happening:
I have a media file that is in Swedish. It also includes “Swedish Forced (ASS)” subtitles. Since I cannot understand Swedish, I have located “English (SRT)” subtitles. Then I have tested them on my Windows Plex Player and everything works just fine. However, when I wanted to watch the show on my TV using the Nvidia Shield, it continues to show me “Swedish Forced (ASS)” subtitles instead.
I am puzzled and did some more testing. On the Nvidia, I can only get “Off” and “Swedish Forced (ASS)” subtitles to work. All other options, simply show “Swedish Forced (ASS)” subtitles instead.
I am guessing that this is a device specific bug unless I am missing something.
Did you use the search option to find that English subtitle? If so, these are only available for you to use. Make sure you are using the same Plex account on your Shield. It’s working for me.
It that’s not the issue, I’m going to need more details.
However, this is different. I have physically uploaded the additional subtitles to the same directory using the following format.
<TITLE>.mkv
<TITLE>.en.srt
Plex also shows the downloaded subtitle for selection on Windows and Nvidia Shield. It just never shows the selected SRT subtitles on the Nvidia Shield and just shows the embedded one instead.
Please let me know if you need additional details.
Media Info-Subtitle Problem.xml.txt (3.2 KB)
You can find the XML file for the video attached to this message, but I won’t be able to send the other file before the evening. Also had to change the extension to allow uploading.
I see where the player first wants the Eng subtitle track then suddenly switched to the Swe track. I don’t know why it’s doing that. I’ll have to check with the devs, but thanks for the log.
Might be related then. I mainly want to confirm that your subtitle file can run on another platform. This makes sure that there is no problem with SRT file itself I think.
Maybe you can gather some log files. This would allow @anon18523487 to determine if this is indeed the same issue. Otherwise, it might make sense to open another thread to keep track of both issues.