Recording terminated early

[Stanno]

Hi all,
I am using an HDHomeRun Quatro (device IDs 25-28) and had something happen last evening that I don't understand.  I had three programs set to record:
Prog A : 20:00-21:00 on BBC 4
Prog B : 21:00-22:00 on BBC 1
Prog C : 21:00-22:00 on BBC 2
All set with 4 minutes pre- and post-padding.
Prog A was terminated early, at 20:56 when Progs B and C started, instead of 21:04.
I keep a daily back-up of npvr.db3 and, when I looked back, both Progs A and B were assigned to tuner 25 so I can see why Prog A terminated but why were they assigned to the same tuner when there were others spare?
Any help/advice appreciated.
I have not attached logs as they all start at 1:00am this morning, after this all happened.
Thanks,
Stanno

[BrettB]

Hi all,
I am using an HDHomeRun Quatro (device IDs 25-28) and had something happen last evening that I don't understand.  I had three programs set to record:
Prog A : 20:00-21:00 on BBC 4
Prog B : 21:00-22:00 on BBC 1
Prog C : 21:00-22:00 on BBC 2
All set with 4 minutes pre- and post-padding.
Prog A was terminated early, at 20:56 when Progs B and C started, instead of 21:04.
I keep a daily back-up of npvr.db3 and, when I looked back, both Progs A and B were assigned to tuner 25 so I can see why Prog A terminated but why were they assigned to the same tuner when there were others spare?
Any help/advice appreciated.
I have not attached logs as they all start at 1:00am this morning, after this all happened.
Thanks,
Stanno

The initial tuner "assignment" does not take into account pre- or post-padding because those are optional. However, just because Prog B was initially assigned to tuner 25 doesn't mean that it will actually use tuner 25 for recording. The way that NextPVR works is when it hits the pre-padding start time, it will first check to see if the initially assigned tuner is available. If not, then it will check all of the other tuners that have that include that channel to see if any of them are available for the actual recording time. If so, then it will "move" the recording to one of the other available tuners. You should see all of this activity (checking the various tuners) in the Nrecord.log file.

Without logs, we can only guess--we don't even know what O/S you're running the server on. You also didn't tell us what tuner Prog C was initially assigned to. Based upon what you describe, I would think that the channel for Prog B is either only available on tuner 25 or it is only available on tuner 25 and one other tuner which is the one that Prog C was initially assigned to (probably tuner 26). When you configured you HDHR tuners, did you set them all up and configure them first on tuner 25 and then accept NextPVR's offer to copy that configuration to the other 3 HDHR tuners? If you "scanned" each one separately, even though the channels may look the same (i.e. same channel number, same call sign, etc.), internally they are different and not interchangeable.

[ElihuRozen]

Any help/advice appreciated.
I have not attached logs as they all start at 1:00am this morning, after this all happened.
Thanks,
Stanno

When a new log is started, the previous log is renamed with a ".1" and the previous one to that is renamed from ".1" to ".2", etc.  When you use the button in the web interface to get the logs, in addition to flushing anything waiting to be logged to the log, it zips up everything in your logs directory, including the ".1", ".2" and ".3" files.

TLDR - you should use the button in the web interface to get the logs & post that zip file it produces.

[Stanno]

Thanks BrettB, apologies for omitting OS information, it's Win 10.

Prog C was assigned to 26. All tuners have the same stations, and yes, the configuration was copied across by NPVR.

I have looked at the current npvr.db3 and there are some interesting anomalies. With the HDHR, the start time is usually spot on so I would have expected to see it stored as 20:56:00 for Progs B and C but it is 20:56:42. The end time for Prog A is odd, it's 20:56:43.0042719 and I have had to manually correct these strange dates in the past or it throws up an error. The tuner is shown as 25 for both Progs A and B and 26 for Prog C.

Stanno

[Stanno]

Thanks ElihuRozen, but I checked the .1, .2 and .3 files as well, they all started after last evening's recordings.

Stanno

[mvallevand]

Always attach the zipped logs anyway, it is not just nrecord we look at.

BTW this is not a new issue, there are other posts like this.

Martin

[BrettB]

Thanks BrettB, apologies for omitting OS information, it's Win 10.

Prog C was assigned to 26.  All tuners have the same stations, and yes, the configuration was copied across by NPVR.

I have looked at the current npvr.db3 and there are some interesting anomalies.  With the HDHR, the start time is usually spot on so I would have expected to see it stored as 20:56:00 for Progs B and C but it is 20:56:42.  The end time for Prog A is odd, it's 20:56:43.0042719 and I have had to manually correct these strange dates in the past or it throws up an error.  The tuner is shown as 25 for both Progs A and B and 26 for Prog C.

Stanno

OK. You still didn't include any logs, so we're still having to totally guess here. (Even if the main Nrecord.log.* files don't go back far enough, it is still important to include a set of the .zip logs generated from the web app. There are other files which may have more history and seeing current logs will often tell us things like what O/S, what device types, you EPG source, etc.) Which of the HDHR device types are you using in NextPVR? The "HDHR" ones or the "ATSC/DVB-T" ones? These behave differently, so it is critical to know which type you are using.

Also, were there any other recordings that began before 22:00?

[Stanno]

Hi all,

My apologies, mea culpa on the logs, I misread the dates.  Logs attached, this problem looks like it is covered by nrecord.log.2.

There were no other recordings around that time, just Progs A, B and C.

HDHR device type is HDHR.

Stanno

[Stanno]

Just in case it helps, here ared the HDHR log entries:
20211222-19:56:00 Tuner: tuner0 tuning 9 BBC FOUR (t8dvbt:514MHz-4544)
20211222-19:56:01 Tuner: tuner0 streaming http to 192.168.1.235:56276
20211222-20:56:41 Tuner: tuner0 http stream ended (remote closed)
20211222-20:56:42 Tuner: tuner0 tuning 1 BBC ONE W Mid (t8dvbt:514MHz-4165)
20211222-20:56:42 Tuner: tuner0 streaming http to 192.168.1.235:56349
20211222-20:56:43 Tuner: tuner1 tuning 2 BBC TWO (t8dvbt:514MHz-4287)
20211222-20:56:43 Tuner: tuner1 streaming http to 192.168.1.235:56351
20211222-22:04:01 Tuner: tuner0 http stream ended (remote closed)
20211222-22:04:01 Tuner: tuner1 http stream ended (remote closed)

Stanno

[mvallevand]

Thanks. It might be worth providing the zipped HDHR log from http://192.168.1.130. The source of the problem is a failed tuner request to your HDHR

Code:

2021-12-22 20:56:00.393    [DEBUG][9]    Requesting: http://192.168.1.130:5004/tuner2/v1
2021-12-22 20:56:21.492    [DEBUG][9]    Failed to start recording on allocated device (47537:D:\NPVR\The Girl Before\The Girl Before.S01E04.ts): 'A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.'

and then there does appear to be a "bug" in second chance recording comes up, as NextPVR steals the tuner from "Yes Minister"

2021-12-22 20:56:21.518 [DEBUG][9] Stopping stream (5) from previous frequency: 5

Martin