Server Version#: 1.28.1.6104 >> (Synology DS1019+ with DSM 7.1-42661 Update 3)
Player Version#: 9.6.3.34515 >> (Nvidia Shield with Android TV 9.1.0 [33.2.0.125])
Hello everybody,
Error description:
When I hit the play button of a movie or an episode of a series, Plex automatically selects the correct forced SRT subtitle in German for me. If I use my Nvidia Shield , FireTV-Stick or my Android phone for the playback, the loading circle runs infinitely long and the background just remains black.
The Plex Web Player in Firefox or Chrome for example, works normal.
Workaround:
Immediately after disabling the subtitle, the media playback starts as usual. After that I can turn the same subtitle file on again and now it works, even with forced German SRT subtitles enabled.
This failure does not only happen when Plex tries to transcode media. It sometimes happens with the original source files in direct play, too.
Please take a look at the collected server logs below.
Can´t believe it´s that easy. I already spent so much time to fix this. After disabling the auto-adjust option on client-side, the problem is gone. Thanks a lot!
Are there any plans to fix the auto-adjust option? So far, I can´t find the original post.
Using PMS Server # 1.28.1.6104
Android TV Client # 9.6.3
Client is setup with optical pass-through with AC3 and DTS selected since my TV only has 2.0 PCM output from the HDMI port. Reminder that is the is a bug that converts SRT subs to ASS subs when there is audio transcoding happening.
There was an old bug but that was resolved a long time ago. This is still needed in some cases or we lose sync between the audio and subtitle, but I would need to check a specific playback to see.
Let me know what else I can provide!
How about the android logs after reproducing the issue.
That is correct, there is a 4k file for local play and an optimized 1080p file for remote play.
This has never been an issue before. I would use the 1080p file for the “Watch Together” feature for family that is not living with me while I watch the 4K at home. Worked so nicely until until about 3ish weeks ago. Then I had to start disabling subtitles to continue to do that.
The optimized file information isn’t shown in the XML you provided. Also, see how the 4k version is listed as having EAC3 audio. That also doesn’t match the xml you provided.
@MovieFan.Plex , I maybe off here, but this seemed odd to me in the logs…
Aug 24, 2022 23:16:54.465 [25336] DEBUG - [Req#284f70/Transcode] Streaming Resource: Reached Decision id=94054 codes=(General=1001,Direct play not available; Conversion OK. Direct Play=3000,App cannot direct play this item. Direct play is disabled. Transcode=1001,Direct play not available; Conversion OK.) media=(id=212871 part=(id=214700 decision=transcode container=mkv protocol=hls streams=(Video=(id=473904 decision=copy width=3840 height=1920) Audio=(id=473905 decision=transcode bitrate=640 encoder=ac3 channels=6 rate=48000) Subtitle=(id=473907 decision=transcode bitrate=2147483647 encoder=ass languageCode=eng location=embedded))))
Would that “expected bitrate” cause issues with the buffering?
Aug 25, 2022 12:53:32.786 [39680] DEBUG - [Req#2dbf0a/Transcode] Streaming Resource: Reached Decision id=94054 codes=(General=1001,Direct play not available; Conversion OK. Direct Play=3000,App cannot direct play this item. Direct play is disabled. Transcode=1001,Direct play not available; Conversion OK.) media=(id=212871 part=(id=214700 decision=transcode container=mkv protocol=hls streams=(Video=(id=473904 decision=copy width=3840 height=1920) Audio=(id=473905 decision=transcode bitrate=640 encoder=ac3 channels=6 rate=48000) Subtitle=(id=473907 decision=transcode bitrate=2147483647 encoder=ass languageCode=eng location=embedded))))
