Failed to lock a signal

[roy]

I've been trying to get more logs, but netpush.txt gets deleted and restarted during the recording so data is lost. Should it be creating netpush-xxxx.txt as you indicate above, because I don't see it, only netpush.txt

[ttfitz]

Don't know if more data will help or not, but attached are logs for a similar run to Roy's above - 3 pairs of 5 minute back-to-back-to-back recordings, last pair 0 byte files. I also trimmed off the 200+ megabytes of identical errors from the netpush file.

The 0 byte files should have started at 14:30.

[roy]

I can reproduce the 0 byte file problem with live TV. After 4-6 channel changes I'll get a 0 byte file, black screen. Esc back to guide, watch the same channel will almost always get 0 byte file again, esc again, watch same channel again will play properly.

Logs attached show this: watch channel 704, up to 705, 706, 707, then 708 is 0 byte. Try 708 again is 0 byte, try 708 again and it plays.

The netpush.txt file seems to reset itself, so I only get it with data from the final good tuning.

[ttfitz]

I can reproduce the 0 byte file problem with live TV. After 4-6 channel changes I'll get a 0 byte file, black screen. Esc back to guide, watch the same channel will almost always get 0 byte file again, esc again, watch same channel again will play properly.

Logs attached show this: watch channel 704, up to 705, 706, 707, then 708 is 0 byte. Try 708 again is 0 byte, try 708 again and it plays.

Same here, although I found that it doesn't matter if I try to play the same channel that got the 0 byte file or a different one, it still won't play after the first time, but will in a second try.

I noticed that there is a new version of the Silicondust service software available on their website, but I still have these problems with the new version, too, so that didn't help.

[roy]

I also installed the 20111128beta1 firmware recently that I found on the Hauppauge support page and didn't see any change.

[sub]

I can reproduce the 0 byte file problem with live TV. After 4-6 channel changes I'll get a 0 byte file, black screen. Esc back to guide, watch the same channel will almost always get 0 byte file again, esc again, watch same channel again will play properly.

Logs attached show this: watch channel 704, up to 705, 706, 707, then 708 is 0 byte. Try 708 again is 0 byte, try 708 again and it plays.

The netpush.txt file seems to reset itself, so I only get it with data from the final good tuning.

I'm wondering if you might have some other software listening on port 5004, which is the port the app tries to use in this log when it first tries to tune to channel 708. This would lead to the socket bind error and no incoming data.

[ttfitz]

I'm wondering if you might have some other software listening on port 5004, which is the port the app tries to use in this log when it first tries to tune to channel 708. This would lead to the socket bind error and no incoming data.

I think you may have tuned in on the problem (sorry, couldn't help myself). I looked back at my logs, and in all the cases I had handy, it was always port 5004 or 5005 that gave me a 0 byte file. After some digging around, it appeared that WMPNetworkSvc was watching those two ports. I stopped the service, and at least the live TV problem seemed to go away.

I still need to test some more, but I thought I'd post in case Roy wanted to check on the same. Roy, the service name is "Windows Media Player Network Sharing Service."

[ttfitz]

I still need to test some more, but I thought I'd post in case Roy wanted to check on the same. Roy, the service name is "Windows Media Player Network Sharing Service."

It looks like this is where the problem is. I was able to run 5 sets of back-to-back recordings with the WMPNetworkSvc stopped without any problems, including the ones using port 5004 and 5005. I was also able to change live tv without any problems. I then restarted the service, and hit the same problem with when 5004 and 5005 cycled around.

[roy]

Yes!!!! That did it. Live TV and back to back recordings all went properly with that service stopped. Thank you!

[sub]

Here is a patch that moves the port range to a more obscure set of ports, which should hopefully resolve this conflict. It also makes it configurable in the config.xml.