Server Version#: 1.40.0.7775
Player Version#: 1.85.0.4071-21128b56
When playing media on my homeserver on the latest build of Plex on Windows the subtitles will not show. Testing has been conducted and I discovered that VLC and android playback the subtitles just fine, just the windows client does not seem to show the subtitles at all.
This is across my whole server for all members.
We are talking about 3 different languages, all not working. Dutch, English and Japanese.
Player Version#: 1.85.0.4071-21128b56
Subtitle type?
Working with PGS & VOBSUB embedded and SRT external subtitles on my Win10 PC.
Hello Ford,
To give extra information, the subtitles are SRT these:
Don’t Worry Darling (2022) {imdb-tt10731256} [Bluray-1080p][AC3 5.1][x264]-BHDStudio.en.srt (100.2 KB)
Same issue for:
Don’t Worry Darling (2022) {imdb-tt10731256} [Bluray-1080p][AC3 5.1][x264]-BHDStudio.ja.srt (89.7 KB)
I have cleared the Cache within Localappdata, no result.
I have reinstalled the app (and removing localappdata/program files), no result.
This problem seems to only happen with SRT subs thus far.
The files look OK. They’re in UTF-8 format.
Given all the extra information, there may be something in the file name causing a problem.
As a test, try placing all the extra info inside one square bracket.
After renaming, you’ll need to re-scan the library and possibly refresh the metadata.
/movies
../Don't Worry Darling (2022)
..../Don't Worry Darling (2022) {imdb-tt10731256} [Bluray-1080p.AC3 5.1.x264-BHDStudio].ext
..../Don't Worry Darling (2022) {imdb-tt10731256} [Bluray-1080p.AC3 5.1.x264-BHDStudio].en.srt
..../Don't Worry Darling (2022) {imdb-tt10731256} [Bluray-1080p.AC3 5.1.x264-BHDStudio].ja.srt
If that does not work, the strip it to the bare minimum:
/movies
../Don't Worry Darling (2022)
..../Don't Worry Darling (2022).ext <-- ext = mkv/mp4/etc
..../Don't Worry Darling (2022).en.srt
..../Don't Worry Darling (2022).ja.srt
Also, I uploaded dutch subs manually and they also don’t work:
Hi Ford,
We follow a strict naming convention, which does not cause issues for over 2000 people. I’ve been doing this for 2 years, I’m which the naming has not changed. I do want to note that none of the subs are working on WINDOWS ONLY. All the other platforms it streams just fine. Tomorrow I will playback a few, because almost all newly added media is starting to show this issue, and provide the logs.
I’m at a loss what this could be, the subs are recognized, otherwise I wouldn’t be able to choose the, right?
I will also try renaming, although I’m skeptical of this. This is spreading through my server and is affecting more and more new media, seemingly out of nowhere.
A friend who is on the following version can playback successfully! All other people who can’t are on my version.
Edit: Just saw your post re: working with v1.30.1. Not sure what has changed, but at least that’s a place to start looking.
Edit 2: I downloaded and renamed the subtitle to match a TV episode on my system. It plays fine using Plex for Windows 1.85.0. The subtitles appear on-screen as expected.
I misunderstood. When you said “don’t show,” I thought you meant they did not appear as a choice instead of “do not appear onscreen after selecting.”
That’s why I suggested renaming. I thought there might be something in the file name that was tripping up Plex for Windows.
I’m not sure why they do not appear on screen.
Hopefully somebody has some other ideas of why they will not appear.
I have looked into the logs and the following is reported when starting a movie where the subs are not being displayed on the screen:
Jan 20, 2024 12:41:48.746 [23216882735928] DEBUG - WebSocket: Performing handshake from origin file://
Jan 20, 2024 12:41:48.746 [23216882735928] DEBUG - Beginning read from WebSocket
Jan 20, 2024 12:41:48.749 [23216852482872] DEBUG - Request: [172.18.0.8:53914 (Subnet)] GET /activities (23 live) #d40d4 GZIP Signed-in Token (Quafley) (VegaPC)
Jan 20, 2024 12:41:48.749 [23217255168824] DEBUG - Completed: [172.18.0.8:53914] 200 GET /activities (23 live) #d40d4 GZIP 0ms 321 bytes
Jan 20, 2024 12:41:48.752 [23216854592312] DEBUG - We're going to try to auto-select an audio stream for account 1.
Jan 20, 2024 12:41:48.752 [23216854592312] DEBUG - Selecting best audio stream for part ID 219241 (language: ja)
Jan 20, 2024 12:41:48.752 [23216854592312] DEBUG - We're going to try to auto-select a subtitle.
Jan 20, 2024 12:41:48.752 [23216854592312] DEBUG - Selected a foreign audio track:
Jan 20, 2024 12:41:48.752 [23216854592312] DEBUG - Subtitles: Found a candidate subtitle language [en] for a foreign film
Jan 20, 2024 12:41:48.752 [23216854592312] DEBUG - Audio Stream: 684911, Subtitle Stream: 684913
seems to work just fine.
Internal subtitles seem to work without any issue, external subtitles seem to not play.
Alright! I have some news!
I’ve tested previous versions of plex:
I also noticed that when I switched subtitles on version 1.83, it would reload the playback. It doesn’t do that on version 1.85 or 1.84
I’ve tested multiple movies on version 1.85 with internal and external subs. for ALL the external subs failed. Internals subs worked. When switching to 1.83 it worked fine.
Do the external subtitles start to work if you set the video bitrate to some low value?
Let me test this real quick.
I also read the newest PMS update (14 days ago) the problems didn’t happen before this. I see the database has been restructured, and 2 things have happened in regards to subtitles. I will confirm if people are having this issue with older server versions as well.
hm, yes you’re right, it does start to play when the transcode to a low quality…???
I merely switched the quality from original to a transcode and it started to play it. It DID reload the stream, which it does NOT do when switching subs. Which it did on older version (1.83)
Would it perhaps be a thing to try and rollback the PMS?
In order to roll back a database to an older version than 1.31.2 you would first need to downgrade to 1.31.2 (up to 1.32.8) and then downgrade from that version afterwards.
Sorry, I don’t see externally linked pictures.
Try removing the domain name from your server. Avoid using a custom domain name, particularly in the local network. Unless you also have a fitting, publicly trusted security certificate pinned to that domain name.
You should also check your router/DNS resolver if it performs “DNS rebinding protection”. If you can, put in an exception from that protection for the domain plex.direct.
Hi Otto,
I checked this and this has been unchanged for literal months. The only thing that has changed is my plex client and server (updates). I also checked what you mentioned.
