Failed to lock a signal

[roy]

Very good, thank you.

And thanks ttfitz for helping figure that out.

Now if comcast would stop copy protecting channels. I recorded "Raiders of the Lost Ark" the other night, which is rarely on, only to find a blank recording, and see now that the channel is flagged copy once. Arrrgh!! They are pretty good at fixing it when I contact them, but what a pita.

[ttfitz]

Very good, thank you.

And thanks ttfitz for helping figure that out.

It was a good group effort (of course with the bulk from our fearless leader), wasn't it? A good community here, I have found.

Now if comcast would stop copy protecting channels. I recorded "Raiders of the Lost Ark" the other night, which is rarely on, only to find a blank recording, and see now that the channel is flagged copy once. Arrrgh!! They are pretty good at fixing it when I contact them, but what a pita.

Are you having channels which weren't flagged showing up as flagged, or just keep running into new ones? When I first got this capture device and got my cablecard working, I knew about the policy, so I went through the channels to determine which ones had the flag set wrong, and contacted Comcast to get them fixed. Unfortunately, I wasn't aware that the Encore channels weren't supposed to be "copy freely", and reported the half that weren't, among those channels. So they fixed all the regular channels to "copy freely", but set all the Encore to "copy once" - including the HD channel that had been unprotected! If I had only known...

[roy]

Are you having channels which weren't flagged showing up as flagged, or just keep running into new ones?

After seeing this one channel flagged, I went through and found 5 or so more that were copy-once, which were not like that the last time I went through them all.

[Wakalaka]

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.

Did this patch make it into 2.4.3 release? I haven't done this extensive debug like y'all have done, but I have the same symptoms. However, most of my recordings are not back to back. I have Kaspersky Internet Security and moved NDigitalHost.exe to Trusted.

http://forums.nextpvr.com/showthread.php...post434528

[sub]

Yes, as far as I know this is included.

If you can post the logs next time the problem happens, I'll check it out.

[ttfitz]

Did this patch make it into 2.4.3 release? I haven't done this extensive debug like y'all have done, but I have the same symptoms. However, most of my recordings are not back to back. I have Kaspersky Internet Security and moved NDigitalHost.exe to Trusted.

http://forums.nextpvr.com/showthread.php...post434528

I just looked at my logs, and the change in port numbers does appear to be in the latest version - I'm getting ports in the 36316 range.

[roy]

I am seeing "failed to lock a signal" failures again. One time I think on 3/28, now tonight "Make it or break it" and "The Daily Show" failed. I notice that the tuner light is not lit while nPVR shows the tuner in use. Logs attached.

[roy]

I had more problems last night with the DCR2650 locking up, but not affecting other tuners. Seems like similar symptoms as before. How can I check which ports other services are using, to see if they conflict with the tuner ports?

[sub]

From memory you can run:

netstat -an | find /i "listening"

[roy]

From memory you can run: netstat -an | find /i "listening"

Thanks, that does it, I'll try it at home tonight.

Also, from previous post when you provided the patch:

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.

What was the set of ports specified with the patch?
Might it have changed upon update to 2.4.3, causing my problem?
I just noticed this info so I'll look into it tonight also.

Thanks