Client Freezing watching Live TV in SD

[AceFlyert63]

Hello Graham,

Hadn't seen that yet. Not quiet the same issue, but was worth a try. I found a 20141210 version of the software, uninstalled HDHomeRun, rebooted, and then installed version 20141210. Went to a client and selected live TV and started watching "Mr. Ed". Took about 15 seconds before he picture froze. So still no love...

Was just wondering - I currently only have the HDHomeRun software on the NextPVR machine acting as my server. Should I have this software on the clients as well?

[Graham]

Should I have this software on the clients as well?

Nope. All communication with the tuner is from the server.

I have just looked at the client logs that you posted earlier and I see ...

2015-10-15 19:30:33.570 [DEBUG][1] GetServerStatus() returns:
<Status>
<Device oid="20" identifier="Silicondust HDHomeRun Tuner 1019C932-0:1">
</Device>
<Device oid="24" identifier="Silicondust HDHomeRun Tuner 101B218C-0:1">
</Device>
<Device oid="22" identifier="Silicondust HDHomeRun Tuner 1019C932-1:1">
</Device>
<Device oid="26" identifier="Silicondust HDHomeRun Tuner 101B218C-1:1">
</Device>

You should not have any tuner device configured on the client. And, therefore, you should not have any channels configured on the client because there is no tuner for the channels to be "attached to". The only channels that you see in the TV Guide on the client should be the channels defined on the server on the tuner that is defined on the server.

[ccihon]

According to the forum gurus @SiliconDust, firmware is not downgradeable or allowed - they claim issues w/r to CableLabs.

This policy may be true for Cablecard units like the Prime - I thought the OP was using a Dual QAM/ATSC device. I own both and have been able to downgrade them regardless. I know when they rolled out upgrades a few months back it caused my Dual to enter a reboot loop and the Prime was creating unreliable streams, so I returned to the previously working firmware combo and left well enough alone.

To the OP - there is no reason to have or benefit from having the HDHomerun software on the clients, unless, of course, you want to use that software from the client to either watch the streams directly etc. Your server machine will handle all the scan and tune functions and will pass the live or recorded streams to the clients.

[ccihon]

Hello Graham,

Hadn't seen that yet. Not quiet the same issue, but was worth a try. I found a 20141210 version of the software, uninstalled HDHomeRun, rebooted, and then installed version 20141210. Went to a client and selected live TV and started watching "Mr. Ed". Took about 15 seconds before he picture froze. So still no love...

Was just wondering - I currently only have the HDHomeRun software on the NextPVR machine acting as my server. Should I have this software on the clients as well?

Did you also select something other than "NPVR" for the BDA choice? As I mentioned, my dual is running a slightly earlier version than the one you mention, and I know I reverted for a reason. Before, using any version of the software where the setting choice in the Silicondust software was "NPVR" I would get lots of hangs and freezes, especially from specific channels. I have also verified the stream size when toggling between "NPVR" and "Other" setting being significantly different, with the "Other" stream occupying significantly more bandwidth. Just checked - the setting is under the Application tab for my software and I successfully use "Other - ATSC/QAM"

[AceFlyert63]

@ ccihon : Yes, in setting up the HDHomeRun sw after reinstalling it on the server PC, I did choose "Other" for BDA. Did not seem to make any difference w/my problem. I haven't had time to try any of the other BDA options, though I hold little hope that will solve my issue.

@ Graham : Are you saying that from the client log entry there is tuner SW found on the client? I did upgrade a couple of my client machines from Win7/WMC to Win10/NPVR (some were fresh installs), so maybe I missed uninstalling the HDHomeRun SW... I'll go back and check and delete it if found to see if it helps...

I had to replace a power supply on one of my clients, and so used that excuse to purchased an SSD as well. I plan to reinstall Windows from scratch this weekend when I install the PSU & SSD disk. Then I think I'll setup NPVR as a server on this PC and point my other client PC towards this newly setup machine, to see if I still have the same problem. Maybe something is corrupted with the NPVR sw on the current server machine?

Thank you both for your input and assistance!

/Todd

[NumberFive]

Hi,

Just to add my two cents to this. I'm still having client freezes on live TV.

I normally just use NextPVR on the server on the main TV, and use VLC for streaming to other PCs, but I have been wanting to set up a proper client on and off for years. Whilst Kodi works okay, I find it very unintuitive compared to NextPVR so once in a while I try NextPVR client again.

Since upgrading to Windows 10, I've noticed from the network utilisation that the client machine is still getting a stream from the server, but it has frozen on a frame and ceases rendering. This leads me to believe the problem is on the client side and not the server.

[NumberFive]

Testing my suspicions that this is related to the buffer on the client under running, I started a live TV stream and then rewound 30s on chasing playback. Has been running for hours now.

I think a fix for this might be to have a longer buffer on the client side, but I'm not sure how this is configured.

[NumberFive]

Just an update, I've experimented with all the different decoders I have available and all exhibit the same behaviour, so can rule that out as a fix.

If I tune to a channel on the client, it will fail after a few minutes (or tens of minutes). If however I tune to a channel and immediately skip backwards, the channel is stable indefinitely. This can be achieved with even 4 ~ 5 seconds chasing playback buffer.

Furthermore, if I tune to a channel, skip back a few seconds, then skip forward so that the client is chasing about 1 seconds behind real-time, it works indefinitely.

Would it be possible to have a configurable buffer on the client, perhaps nominally set to 1 second?

[sub]

If I tune to a channel on the client, it will fail after a few minutes (or tens of minutes).

If you create a c:\temp, and set the following registry keys, then reproduce the problem, and post the logs created c:\temp, I'll see if anything stands out.

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\NPVR
LogClientStream=1 (DWORD)
LogSlipFile=1 (DWORD)

[NumberFive]

Hi sub,

Thank you, here's the logs.

I see the error: "Failed to write all data to ring. Argh!!!" First seen at 17:48:42.139 in stream.txt.