tuner you were using required for recording error

[Barry10]

When I change channels this happens every time. I unistalled and reinstall the most current version. I have 2 Hauppauge tuner 2500's and it works great on Media Center, but not on Nextpvr. Running windows 8.1. Records great using NextPvr, but live TV is an issue. Attached are the log files.

NextPvr is needed so I can upgrade to windows 10. Seems to be the best of the bunch for TV and Recordings.

[johnsonx42]

yeah, I see it happening in your NRecord.log, every time you change the channel the new live stream handle dies before NextPVR.exe renews it. In the NPVR.log there's a big delay during the stream switch:

Code:

2015-09-15 15:57:06.313    [DEBUG][1]    SwitchToStream@3
2015-09-15 15:57:43.871    [DEBUG][1]    SwitchToStream@4

and

Code:

2015-09-15 16:00:41.170    [DEBUG][1]    SwitchToStream@3
2015-09-15 16:01:02.955    [DEBUG][1]    SwitchToStream@4

~37 seconds in the first case, ~22 seconds the second time... either way, far too long. that should happen in less than a second; nextpvr has to renew the live stream lease every 10 seconds, so by the time it comes back from that long delay, NRecord has given up waiting. the "tuner you were using was required for a recording" error is just the go to response for NextPVR any time it can't renew it's live tv stream... it just assumes it must have been because a recording had to start.

but I have no idea why you get such a long delay between SwitchToStream@3 and @4... sub!!!

[mvallevand]

Another problem are these

2015-09-15 15:57:43.900 [DEBUG][1] GetEventCode() returned: 0x0001

which means End of File no data.

Martin

[Barry10]

It is a strange error. I had this before and believe it or not if I set the following value to 2 the problem does not happen. Sounds like a variable is not getting initialized.

The problem is occurring at the following point in your logs. For some reason these steps are taking 30+ seconds on you machine, where normally they'd take a few milliseconds. In the recording service it thinks "I haven't heard from the client in a very long time, so I'm going to assume it no longer needs the tuner".




2015-07-01 06:49:56.901 [DEBUG][1] SwitchToStream@3
2015-07-01 06:50:34.034 [DEBUG][1] SwitchToStream@4 We've not seen these steps being slow for other users, so I'm not really sure why it would be happening.

Can you create a c:\temp directory, and set HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NPVR\LogSl ipFile=1 (DWORD) in the registry, then reproduce the problem again, post the same logs as before, and the additional c:\temp\reader.log.

[mvallevand]

You should only have that registry value set for debugging not real use. Set it to 0 or remove the key.

Martin

[sdf]

I have the same situation (there's another thread). Sometimes randomly nextpvr stalls on channel change (15-20 secs) and in the logs I see that the long delay is between SwitchToStream@3 and @4.
I have to put LogPSIFile=1, if I understand correctly?
Thank you,
sdf

[Barry10]

Martin I have tried it both ways and like I said it fails every time without the debugging turned on. Kind of makes me think a variable is not getting either passed properly or initialized. My machine is and I-7 4700 with an SSD drive, 8 gig's of memory and is very fast. The files I posted were without the entry in the registry. I also installed Win TV 8 and do not have the issue. Still using Windows Media Center and never have any issuse. NextPvr is a perfect replacement for Media Center if I can get it working properly. I am using and outside Antenna and verified the signal strengths are all good.

Biggest complaint is the log files is very large on my SSD drive, so have to do periodic maintenance.

[Barry10]

As a follow up this is what I get with LogSlipFile = 2. Everything seems to work well.

With LogSlipFile = 1, channel changing is slower. Makes no sense, but I guess =2 is the way it works on my machine.

[johnsonx42]

Just to be sure, you are saying that if you have LogSlipFile=1 OR 2, channel changing works fine, though it's slower with it set to 1, but without LogSlipFile (or set to 0) then channel changing fails due to a long delay between SwitchToStream@3 and @4?

[Barry10]

That is correct, does not make any since to me. Also when you record with settings to LogSlipFile=1 and you change channels with a remote it skips 2 channels.