[bmfesta2009]

So I have had this issue since upgrading to the newer MythTV PVR for MythTV 0.27. The issue is that the stream will play for some period of time and then freezes. The period of time is generally greater than 10 minutes and less than 30 minutes If I press stop, return to the guide and watch the same channel again it begins playing without flaw for the next period of time. I'm dealing with the issue but am curious for help.

I have 3 devices, 2 are running the new PVR add-on, 1 without flaw on wireless, and 1 with. The one without flaw is wireless over a media bridge, so the connection is using the standard Ethernet driver.

Here is my environment for the device with the problem:

End Point Device: Raspberry Pi Model B
Network Card: D-Link DWA-180 Wireless AC1000 Dual Band Adapter [300Mbps (2.4GHz)/650Mbps (5GHz)]
Operating System: OpenElec 4.95.5
PVR Add On: MythTV PVR Client 1.9.25
Access Point: Linksys EA-6500 AC1750 Dual Band router [450 + 1300 Mbps]
Back End OS: Mythbuntu 14.4 LTS - MythTV 0.27

The key lines that are identified during every failure in the log are:

Code:

18:32:53 1661.893555 T:2736534592  NOTICE: AddOnLog: MythTV PVR Client: (CPPMyth)ReadResponse: socket(0x9e183ac8) timed out (0)
18:33:03 1671.931396 T:2736534592  NOTICE: AddOnLog: MythTV PVR Client: (CPPMyth)ReadResponse: socket(0x9e183ac8) timed out (1)
18:33:13 1681.972168 T:2736534592  NOTICE: AddOnLog: MythTV PVR Client: (CPPMyth)ReadResponse: socket(0x9e183ac8) timed out (2)
18:33:23 1692.018188 T:2736534592  NOTICE: AddOnLog: MythTV PVR Client: (CPPMyth)ReadResponse: socket(0x9e183ac8) timed out (3)
18:33:33 1702.066895 T:2736534592  NOTICE: AddOnLog: MythTV PVR Client: (CPPMyth)ReadResponse: socket(0x9e183ac8) timed out (4)
18:33:43 1712.116821 T:2736534592  NOTICE: AddOnLog: MythTV PVR Client: (CPPMyth)ReadResponse: socket(0x9e183ac8) timed out (5)

All help is appreciated

I couldn't find a way to upload the log file so I'm hoping this link works for you: kodi.log

[janbar]

Often it is quite complex to run more than one device at same time throw wifi network. Try to use an other wifi channel if your router allow it. Avoiding interference etc... Here seems your device loose connection. To confirm root cause is wifi, try first with cable connection.

[janbar]

Regarding you log file, your device was never connected !! I propose you to setup the ip address of your backend instead Its friendly name.

[bmfesta2009]

I appreciate the response. The wireless network isn't the issue (other than possibly the network driver) as that is a dedicated access point for that device (there are other access points in use for the remainder of the network) and the tests were performed while only that end point was running. The device was connected clearly as I was watching TV on it. I have used both friendly name and IP address, neither showed differences.

I have seen some improvement by changing the clock speed and voltage as well as changing the start buffer time for live TV. Today I was able to go 45 minutes of constant playback before it lost audio/video sync. Please keep the advice coming.

[nickr]

Can you run a temporary ethernet wire and see if there is a difference?