LG UJ65 + PMS on FreeBSD jail + Ubiquiti AP = buffering issues

smart-tv

#1

Hi all

So I have the 2017 LG UJ65 TV running the Plex app. The PMS is running in a separate jail on FreeNAS, and I have a Ubiquiti UAC Pro AP doing wifi.

The TV is connected to a 5Ghz 802.11n/ac network on it's own hidden SSID. For some reason, some things that stream just buffer constantly and other items don't. It varies for time of day, and video media item to video media item.

Most video media is now in H.264 encoding with AAC audio inside an MKV container. It all appears to be using Direct Play instead of streaming. The FreeNAS box has a lot of power to give if it needs to transcode.

The TV is configured to hard power off, as I was having RAM issues with apps and this was the only way I found you can flush the RAM. However turning it off and on again doesn't always make a difference and this buffering issue can happen even if the TV has been switched off for long periods of time.

It don't think it's the wireless network. Most of the time that channel and network is empty and free. By most of the time I mean there is only 2 devices that connect using AC 5Ghz one being the TV, everything else uses 2.4Ghz. And... if I use one of the AppleTV's connected to the projector or the TV upstairs and play the same content, it's fine. That said, the projector is hardwired and the upstairs is much closer to the AP.

I think... it's the TV. Though I have also noticed that if I play an item on another device in the house (PC, AppleTV, iPad) and go back and watch it again on the LG TV it seems not to buffer at all as though the PMS has cached the content or something. That or the FreeNAS instance has...

Any suggestion's folks?


#2

No replies?
I’ve found these two problems from the logs:

“Jan 07, 2018 20:13:49.385 [0x80ab00400] VERBOSE - We didn’t receive any data from IP Address of the LGTV:36242 in time, dropping connection.”

“Jan 07, 2018 20:13:54.177 [0x80c853500] ERROR - Unable to find client profile for device; platform=webOS, platformVersion=04.70.04, device=, model=”

Sounds like a timeout issue from the wifi perhaps?


#3

I’ve been reading the logs…
So my TV is a lot higher resolution than most of the content that is streamed to it. Would the fact that it upscaling content be why it might buffer substantially?

Some log data

Jan 12, 2018 21:11:50.124 [0x80ab00400] VERBOSE - [IDLE] Removing (1->0) work item http_download - /player/proxy/poll?deviceClass=pc&protocolVersion=1&protocolCapabilities=timeline%2Cplayback%2Cnavigation%2Cmirror%2Cplayqueues&timeout=1&X-Plex-No-Cache=15157626890513842&X-Plex-Client-Identifier=z6piibay0ucsdcxrvqk92f7t&X-Plex-Device-Screen-Resolution=1920x1080&X-Plex-Version=3.13.7&X-Plex-Product=Plex%20for%20LG&X-Plex-Platform=webOS&X-Plex-Platform-Version=04.70.04&X-Plex-Token=xxxxxxxxxxxxxxxxxxxx Jan 12, 2018 21:11:50.124 [0x80ab00400] VERBOSE - [IDLE] Server is now idle Jan 12, 2018 21:11:53.758 [0x80ab00900] VERBOSE - We didn't receive any data from 192.168.1.128:50916 in time, dropping connection. Jan 12, 2018 21:11:54.144 [0x80b474d00] DEBUG - [CompanionProxy] player z6piibay0ucsdcxrvqk92f7t was last refreshed 10 seconds ago Jan 12, 2018 21:11:54.145 [0x80ab00400] VERBOSE - WebSocket: processed 1 frame(s) Jan 12, 2018 21:11:54.208 [0x80ab00900] VERBOSE - We didn't receive any data from 192.168.1.128:50918 in time, dropping connection. Jan 12, 2018 21:11:54.208 [0x80ab00400] VERBOSE - We didn't receive any data from 192.168.1.128:50922 in time, dropping connection. Jan 12, 2018 21:11:56.403 [0x80ab00400] VERBOSE - WebSocket: processed 1 frame(s) Jan 12, 2018 21:11:58.774 [0x80ab00400] VERBOSE - We didn't receive any data from 192.168.1.39:60658 in time, dropping connection. Jan 12, 2018 21:11:58.774 [0x80ab00900] VERBOSE - We didn't receive any data from 192.168.1.39:60660 in time, dropping connection. Jan 12, 2018 21:11:58.774 [0x80ab00900] VERBOSE - We didn't receive any data from 192.168.1.39:60656 in time, dropping connection. Jan 12, 2018 21:11:58.774 [0x80ab00900] VERBOSE - We didn't receive any data from 192.168.1.39:60655 in time, dropping connection. Jan 12, 2018 21:11:58.796 [0x80ab00400] VERBOSE - We didn't receive any data from 192.168.1.39:60659 in time, dropping connection. Jan 12, 2018 21:11:58.873 [0x80ab00900] VERBOSE - We didn't receive any data from 192.168.1.39:60657 in time, dropping connection. Jan 12, 2018 21:12:03.445 [0x80ab00900] VERBOSE - We didn't receive any data from 192.168.1.128:50920 in time, dropping connection. Jan 12, 2018 21:12:04.154 [0x80afa4b00] DEBUG - [CompanionProxy] player z6piibay0ucsdcxrvqk92f7t was last refreshed 20 seconds ago Jan 12, 2018 21:12:04.155 [0x80ab00900] VERBOSE - WebSocket: processed 1 frame(s) Jan 12, 2018 21:12:06.409 [0x80ab00900] VERBOSE - WebSocket: processed 1 frame(s) Jan 12, 2018 21:12:07.305 [0x80ab00400] DEBUG - WebSocket: client initiated close Jan 12, 2018 21:12:07.305 [0x80ab00400] VERBOSE - WebSocket: processed 0 frame(s) Jan 12, 2018 21:12:07.305 [0x80ab00400] DEBUG - handleStreamRead code 335544539: short read Jan 12, 2018 21:12:07.305 [0x80ab00400] DEBUG - NotificationStream: Removing because of error Jan 12, 2018 21:12:09.949 [0x80ab00900] VERBOSE - We didn't receive any data from 192.168.1.128:50914 in time, dropping connection.