Samsung SmartTV. Playback interrupts and lags

[SamES 1057]

But are you using that old wifi bridge?

[WingDog 16]

8 hours ago, SamES said:

But are you using that old wifi bridge?

12 hours ago, WingDog said:

this device is already off.

no I'm not. Vonets Wifi bridge is powered-off, disconnected and trashed.

there is no any network device connected to TV model UE50AU7002UXRU.

 

 

 

 

[brothom 177]

I have to admit, my Samsung Smart TV is also acting different from my other devices (Chromecast / Browser and app) taking much longer to load initially (taking about 5 seconds to load from timestamp 0) whilst the browser and app are almost instant.

The Samsung Smart TV app also seems more prone to buffering than the other platforms. Maybe the buffer size is much smaller? Regardless, buffering takes much longer on the tv app than other devices even when the network is barely busy. 

What I did notice is that when there's a lot of drive activity this issue seems more apparent .

The logs don't offer any insight either because it's like nothing happens from the Emby side of things. Emby reports:

2025-07-29 20:23:38.701 Info Server: http/1.1 Response 204 to ‌‍‍192.168.2.4‌. Time: 2ms. POST http://‌‍‍192.168.2.200‌/emby/Sessions/Playing/Progress

[TV start buffering] So I start checking out the server, but I can't find anything wrong after about 5 minutes.
Go back to the TV and press play which shows up in the logs:

2025-07-29 20:28:04.645 Info Server: http/1.1 POST http://‌‍‍192.168.2.200‌/emby/Sessions/Playing/Progress

So the logs just seem to jump the gap. I'll check the other logs as well. It's not like any other process seems to be stalling or choking the system either.

I did find this tho: 

2025-07-29 20:11:44.229 Info SubtitleEncoder: ProcessRun 'ffmpeg-subtitle_convert' Execute: XXXX\AppData\Roaming\Emby-Server\system\ffmpeg.exe -loglevel +timing -y -sub_charenc:s:0 utf-8 -i "XXXX.srt" -map 0:0 -vn -an -c:s:0 webvtt "XXXX\AppData\Roaming\Emby-Server\programdata\cache\temp\1cfad60074db4a5c9beabbabc1fdef01.vtt"
2025-07-29 20:11:45.238 Info SubtitleEncoder: ProcessRun 'ffmpeg-subtitle_convert' Process exited with code 0 - Succeeded

Eventhough taking a hot second, waiting for this to load together with requesting the conversion, waiting for that and the tv to process the vtt when loaded might explain the slightly long wait when initially loading media.

It kind of suprises me that my TV doesn't seem to support .srt files and a conversion to vtt is required.

This conversion can also just take place on the client side because srt and vtt are both text formats and I've also a written a converter for myself some time ago if any devs are interested.

Edited July 30, 2025 by brothom

[WingDog 16]

hi there!

 

While I was waiting for Wi-Fi bridge delivery, I decided to take a look into something like HTTP-based speed test and found this one

https://openspeedtest.com/ -it's very easy to use HTML5-based on-premise speedtest which doesn't require own client like iperf.

so I started the server-side at my home server (Intel GE NIC) and used Samsung Browser at TV and got this:

 

this is TV's internal Wi-Fi.

Despite these results, it was impossible to watch Snatch in directplay mode with a 96Mbps bitrate - Emby regularly spun a blue circle for 2-3 seconds each.

yesterday Buddy 6 SE was delivered.

well, I have to say, that my TV has only fastethernet port =(

this is test via Buddy

so the result was predictable.

but be that as it may, watching the Snatch has become much better and now it's not a blue circle, but just a half-second lag. Of course, it's still impossible to watch, but the experience was bought for only $100. now it's limit of FE port.

 

conclusion:
the problem most likely lies in the TV's Wi-Fi adapter buffer, its driver or the features of the Tizen OS.
it's a pity, of course, that instead of just a software debug, we caught it by sorting through the customer's hardware, but nevertheless.
we can close the topic here - I can do further hardware sorting myself and without the participation of developers.

P.S. in the next topic I will write about the terrible search and result selection function, perhaps it will be possible to do without replacing the hardware.

 

Edited August 8, 2025 by WingDog