@peakbagger said:
I have tried the Always Burn fix and it didn’t help for me. I assume my home server can transcode, but, how would I be able to tell if it wasn’t able to?
The easiest way would be to change the quality during playback down to a level below the current video’s setting. If it was a 1080p video change the quality to 720p. If the video switches down to 720p then your server supports transcoding the video.
Sorry, even at fixed resolutions and with Auto off, the problem occurs. At least with Chrome on the latest Plex Server Beta for Windows.
Skipping forward and back (e.g. Shift + Left or Right Arrow) sometimes “fixes” the problem (for a few minutes), but not always. Sometimes I need to skip again to force Plex to buffer, then the subtitles return. For about 4 minutes… 
I’ve read that UTF-8 SRTs wouldn’t have the problem: not true with most recent Plex Beta and Chrome Web player.
Hey Plex Team, i’m a bit angry here. I can’t believe that you haven’t made enough tests like subtitles before rolling out the last update. I have a plex pass for years now and my app is unsable for a week now. Could you please find a fix for this issue ? Thanks.
@jmckee said:
@PawBroon said:
Always Burn doesn’t do anything to prevent the problem with SRT from happening.
XBox One and Synology, here…Is your server able to transcode video? If not then that would be why always burn doesn’t work as the server needs to transcode the video to burn the subtitles.
It does transcode.
FIXED ! Web Player 3.27.1 (included in Media Server 1.9.6.4429) fixes the problem for the Web Player in Chrome. Thanks @Devs !
Little issue: with 1.9.6.4429, I always have transcode x264 (hw to hw) instead of Direct Streaming for the videos (same videos, same condition were Direct Streamed in 1.8.4)…
… and then again some streams play Direct as before. Go figure… (P.S.: auto quality disabled)
Unfortunately I had to downgrade back to PMS 1.8.4. Indeed most MKVs (usually x.264 / AVC High@4.1 video, 1920x1080, with E-AC3 or AC3 audio, total bitrates tested between 5 and 17 mpbs) needed to be converted using the newest beta. On my 2nd Plex server (laptop) it was decoding x264 (software) to x264 (hw) which means near 100% CPU usage :-(.
Using PMS 1.8.4, the same shows will play DirectStream for the video, and only need to convert the audio into AAC.
I’ve done tests with many different files and the conclusion is that 1.9.6.4429 re-encodes almost all videos, even with all auto quality settings off, forcing to play at original resolution (the videos I tested are stored locally to avoid network issues, the client is the server). The re-encoding happens even with SRTs turned off, so it’s not just a workaround for SRT display (e.g. burning in instead of playing them as sidecar files).
I’ll just wait for a release that plays all AVC (x.264) files through DirectStream again…
@Zillion_ said:
Unfortunately I had to downgrade back to PMS 1.8.4. Indeed most MKVs (usually x.264 / AVC High@4.1 video, 1920x1080, with E-AC3 or AC3 audio, total bitrates tested between 5 and 17 mpbs)
I’ll just wait for a release that plays all AVC (x.264) files through DirectStream again…
Did you remember to reset the subtitle option back to auto? I see you mentioned quality to auto, but not sure if you did the subtitle option as well.
H264 at the levels you posted above should not be transcoding to the Xbox One at all unless you have a quality/bandwidth restriction, burned in subtitles, or have direct play/direct stream disabled. We would need to see the logs in that case to try and determine what is causing the video to transcode as the app should default to H264@5.1. (The eAC3 should transcode now, but that should be independent of the video)
Every release introduces different problems… Newest 1.9.7.4441:
… and back to 1.8.4 again…
@jmckee said:
Did you remember to reset the subtitle option back to auto? I see you mentioned quality to auto, but not sure if you did the subtitle option as well.
I always set this to “image formats only” just to be sure, don’t trust the Automatic setting.
1.9.7.4460: movies don’t get cut after 30 minutes anymore, but now subtitles stop working again after 30 minutes. Repeatedly. Every few minutes.
Come on guys… about time to fix this. Back to 1.9.6 for me…
1.10.0.4516: still losing subtitles, now after about 40 minutes… and back to 1.9.6 for me… again…
1.10.1.4561 resolves all subtitles problems for me on Web Player (Chrome on Windows), IOS and TVOS.
However, another issue appear in recent builds: pausing a show for too long near the end of the episode causes Plex to display Network Error “shaka1001”, close the video player and go back to the episodes list…
Still losing subtitles when skipping forward or back a few times near the end of a TV show episode; still getting Shaka1001 (Network) error when pausing during the last few minutes of a TV show…
PMS 1.11.0.4633, Windows 10 Server & Client (single machine), Web Player on Chrome.
Same problem on Chromecast, losing subs after 15 minutes.
it is terrible. BTW if you have PLEX installed on the SamsungTV the problem does not happen. Only in Chrome works bad for me…
@cartayna said:
it is terrible. BTW if you have PLEX installed on the SamsungTV the problem does not happen. Only in Chrome works bad for me…
same here
Windows Server + PMS 1.10.1.4602 + Chromecast 2
