"The tuner you were using was required for a recording. Would you like to switch ..."

[sub]

Created zipped log files from initial config screen, file was created but the program crashed.

What did the crash message say? I can't see an obvious error message in your logs.

Can you post a screenshot of your Settings->Decoders screen?

[jpsa]

Here's another set of logs, this time with 3.6.6.

I started watching at about 09:16, and had three occurrences of "The tuner you were watching was required for a recording..." over the next 5 minutes (I suspect these correspond to the "Stop@0" messages in NPVR.log at 09:18:55.194, 09:20:30.029 and 09:21:50.661). There were then no further occurrences before I stopped viewing deliberately at 09:30:07 to collect the logs.

Cheers,
John

[jpsa]

This problem occurred again this morning. I wonder if it might be related to EPG updates?

NextPVR is set to update the EPG at 02:55, and checking the system event viewer, the PC did wake at that time last night but went back to sleep only 2'30" later. NRecord.log just shows

Code:

2015-12-16 21:02:48.173    [DEBUG][29]    StopStream(3)
2015-12-17 02:55:00.749    [DEBUG][34]    Resuming...
2015-12-17 02:55:01.852    [DEBUG][6]    cycling MVP servers
2015-12-17 02:55:09.956    [DEBUG][9]    Recording service noted the system was resuming...
2015-12-17 02:55:09.956    [DEBUG][9]    No C:\Users\Public\NPVR\Scripts\Wakeup.bat
2015-12-17 02:56:35.020    [DEBUG][10]    Pre EPG Update
2015-12-17 10:39:46.715    [DEBUG][42]    Resuming...

around that time. When I woke the system this morning to watch TV, NRecord.log includes

Code:

2015-12-17 10:40:20.996    [DEBUG][10]    About to update EPG
2015-12-17 10:40:20.996    [DEBUG][10]    Updating EPG...

and then lots of other messages which look as the EPG was being updated.

Maybe there's a problem which means that an EPG update can interfere with live TV watching? Perhaps this is being triggered by the scheduled overnight EPG update not working properly, but only happening when the system is woken fully the following morning?

Only guessing, though!

[sub]

If you got you configured to go to sleep after x minutes of no activity? If so, what number of minutes is that?

[jpsa]

The machine is configured to sleep after 30 minutes of no activity.

[sub]

Normally there is a 90 second sleep between the message that says "Pre EPG Update" and the next message that says "About to update EPG". It looks like you machine is going to sleep in that 90 seconds for some reason.

[jpsa]

That's expected behaviour, isn't it? According to https://msdn.microsoft.com/en-us/library...85%29.aspx Windows only promises to keep the machine awake for 2 minutes after a wake timer, unless there's user interaction or an application calls SetThreadExecutionState.

[sub]

It's never really caused a problem for users in the past. You could try setting <WakeupPreRecordingSeconds>20</WakeupPreRecordingSeconds> in your config.xml

I've modified it for the next release to remove the risk of a machine going to sleep during this period.

[jpsa]

OK, done. I'll let you know what the effect is.
Thanks!

[mvallevand]

That's expected behaviour, isn't it? According to https://msdn.microsoft.com/en-us/library...85%29.aspx Windows only promises to keep the machine awake for 2 minutes after a wake timer, unless there's user interaction or an application calls SetThreadExecutionState.

That can be changed, I upped mine to 5 minutes and things worked for me following Lao Pan's info http://forums.nextpvr.com/showthread.php...post457496

Martin