Plex Player app on Nvidia Shield does not display OTA CBS Network subtitles

Server Version#: MacOs 1.26.1.5798
Player Version#: 9.2.1.32664
OTA TV from HDHomeRun Flex 4K




Problem: The subtitles on the Nvidia Shield android-tv app do not correctly display for live or recorded CBS network shows.

The signal from the HDHomeRun device has 100% signal strength, 100% signal quality, and 100% symbol quality. Image 1 shows the HDHomeRun signal status, Image 2 shows the HDHomeRun app on Nvidia Shield with correct subtitles, Image 3 shows subtitle errors on android tv app 9.2.1.32664, Image 4 shows playback info.

The same error occurs on both Plex LiveTV and DVR recorded TV on CBS television network shows.

The same CBS show subtitles display correctly on the IOS Plex app.

Huh. Isn’t that the closed captioning in your image?

He’s saying that there is closed captioning, but that the text is garbled and laid out wrong for some reason.

Ah. Can you provide a sample? 1 minute will be enough.

m̩̆e̥͛m͚͋ ͓͊Ǹ̢a̹̽ ͉̈́C̲̀B͖̊S̛̭r͕̋ä̝́m̞̿ ̳̄N̨̊ā̤P̻̊r͕̄o̪̚g̯͗m͎͐e͖̎ ͎͠Ć͔B̜̕Ṡ̠P͉̋r͕̉o͓͘g̹͘

I guess it depends what the program was.

I am happy to provide a short video sample from the plex recording (a .TS file) but I am not familiar enough with handbrake to know how to do it and maintain file integrity. Please provide a pointer to some instructions.

The garbled subtitle text is as shown in the images above (“mem Na CBSram NAProgrme CBSProg”), but it only appears when the video is played in the plex android player. I’ve seen other similar subtitle variations on all shows from our Austin TX CBS TV affiliate.

The subtitles are all correct when I play the same DVR TS files with VLC or other plex clients.

Use this guide Generating Sample Files from Media | Plex Support.

Thanks for the instructions. Here’s a clip that exhibits this issue. The subtitles are displayed correctly when viewed in VLC but not in the plex client.
CBS Evening News With Norah O’Donnell (2019) - S2022E-052.zip (22.6 MB)

See the clip below.

This issue has been fixed in recent updates. Not sure which version fixed it, but it seems to work now.