Samsung TVs transcoding issue

Plex Players Smart TVs
,
21

@GG30

Thanks for the updated logs.

I can see the buffering, about 5 minutes into the movie, but I cannot tell why it is happening.

Question:
How is the TV connected to the network - wired Ethernet or Wi-Fi?
If Wi-Fi, is it on a 2.4 GHz channel or 5 GHz channel?

From information in one of your earlier posts, you can see that the initial bitrate of the video is in excess of 150 Mbps:
requiredBandwidths="152240,139170,100953,74328,70703,67574,56194,44025"

If the TV is connected via wired Ethernet, that explains the buffering, as the TV Ethernet port is limited to 100 Mbps.

If on Wi-Fi, 2.4 GHz (802.11n) does not have the bandwidth to handle 150 Mbps. The TV needs to be on a 5 GHz channel with a strong signal.

From Plex Media Server.log:

Plex makes playback decision: Direct Stream video; transcode audio (dts not supported by Samsung); direct stream external Bulgarian SRT subtitles.

Dec 15, 2022 21:17:41.051 [42980] DEBUG - [Req#154/Transcode] Streaming Resource: Reached Decision id=3787 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=11978 part=(id=11996 decision=transcode container=mp4 protocol=dash streams=(Video=(id=27098 decision=copy width=3840 height=2160) Audio=(id=27099 decision=transcode bitrate=774 encoder=aac_mf channels=6 rate=48000) Subtitle=(id=27094 decision=copy languageCode=bul location=sidecar))))

Playback Starts:
Dec 15, 2022 21:17:44.194 [42980] DEBUG - [Req#1a6] Client [80djvtsbcvmye9wgkuk93lej] reporting timeline state playing, progress of 0/8005351ms for guid=, playbackTime=55ms ratingKey=3787 url=, key=/library/metadata/3787, containerKey=, metadataId=3787, source=

Buffering starts:
Dec 15, 2022 21:22:54.523 [42980] DEBUG - [Req#7ad] Client [80djvtsbcvmye9wgkuk93lej] reporting timeline state buffering, progress of 309779/8005351ms for guid=, playbackTime=310410ms ratingKey=3787 url=, key=/library/metadata/3787, containerKey=, metadataId=3787, source=

Client stopped playback:

Dec 15, 2022 21:26:04.613 [43772] DEBUG - [Req#ac9] Client [80djvtsbcvmye9wgkuk93lej] reporting timeline state stopped, progress of 309779/8005351ms for guid=, playbackTime=310410ms ratingKey=3787 url=, key=/library/metadata/3787, containerKey=, metadataId=3787, source=
...
Dec 15, 2022 21:26:04.694 [43772] DEBUG - [Req#ac9] Streaming Resource: Terminated session 0645F7B8:80djvtsbcvmye9wgkuk93lej with reason Client stopped playback.
22

That’s correct, it’s only a short episode to show you the issue.
I tried many times, it’s definitely not an issue with the file.

This error happens with every single video file.
Very short or very long, it always happens before the video ends: playback error.

But like I said before, this must be an issue that is subtitle related.
It ONLY happens when the burn subtitles option is on ‘automatic’.

(There are more topics where other users report this exact same issue)

23

Hello,
thank you for your feedback.
The video file bitrate is 34.86Mbs not over 150.
I am using Wi-FI5Ghz and my internet speed connection is over 300Mbps (tested on TV)
Also as I said before the issue is present only with subtitles if I disable them - there is no problem.
If you want I can upload logs without subtitles or even try a different file with high bitrate?
I understand that the issue is hard to catch and I appreciate your efforts.

25

I get that, but is it 10 mins? These episodes are suppose to be 15 minutes, so you are missing 5 minutes of the video. If your file is bad, then PMS will have trouble playing it. Or if PMS scanned the file while it was still being written, this can happen.

Double check the duration listed for the file to see if it’s correct. If not, try to analyze these files and see if it fixes the duration. Then try playing the file again.

26

Yes, this specific episode is only 10 minutes long.
There is nothing wrong with the videofile.

Screenshot_20221220-191931
Screenshot_20221220-1919311080×651 38.6 KB

But like I said, this issue happens to ALL my videos.

27

Thanks. Just checking since TheTVDB has the runtime for that episode as 13 minutes. Thought maybe there was an issue with your files not being complete.

I don’t see anything specific in your logs, but I’ll keep looking.

1 Like
28

Can you replay that file without subtitles and stop it after 5 minutes and provide new logs. I see something that may be the problem with the subtitles. I’d like to compare when there are no subtitles.

29

Hello again,
unfortunately my Samsung 2022 TV died and I am waiting for the replacement :slight_smile:
I will try it on my 2019 Samsung TV and if the issue is the same I will upload the logs later.

30

Hello,
sorry for the late answer!
So here are the logs with the subtitles and the issue:
Plex Media Server Logs_2023-01-10_15-11-20.zip (586.8 KB)

And here are the logs as you asked, without subtitles and with no issue stopped after 5:30 minutes:

Plex Media Server Logs_2023-01-10_15-22-08.zip (32.3 KB)

Also, as I said before I have a Samsung 2019 TV and the issue is not present there if you like I can upload logs from this one as well.

31

I think the problem may be the same as mine. What I choose now is using an external TV box.

32

I don’t want to spend extra money considering that I have the latest TV and Plex Lifetime.
I believe the issue can be fixed by the Plex staff.

1 Like
33

Same issue reported here, issue was reproduced by plex staff. No fix since…

1 Like
34

I am seriously considering selling my plex pass and my Samsung TV and buy an AndroidTV… Or waiting for Jellyfin Samsung TV app or reinvest in Emby (tested and works flawlessly)… Any choice looks better that staying with Plex+Samsung.

35

Tested it today, no freezing so far. Might have been fixed.

36

Still not fixed for me.

Always starts to buffer followed by “unknown error” near the end of a videofile.
Only happens when using direct stream though. When I disable direct stream
the issue does not take place.

Definitely a subtitle related bug.
No subtitles = no error.

1 Like
37

Yeah, video is 46 minutes long, stops at 45 minutes… I mean, almost good. C’mon!

38

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.