Recordings fail occasionally.

[JJ202302250834]

I have been using NextPVR since 2018 without any problems. I have a four channel Hauppauge tuner. About two weeks ago I upgraded to version 6.1.1.221106 and ever since about 1 in 4 recordings fails. The failures take on two forms.
1) For some reason in the middle of the recording the channel changes to a different channel. This problem is rare and only happened a couple of times.
2) The recording just stops for no reason what so ever. It appears that this one happens after the pre-pad time expires, right about the time the show actually starts. This happened again yesterday and last night to 'Midsomer Murders'.
Please help

[mvallevand]

It looks like you are doing multiple EPG updates during you recordings which is not supported and is going to cause you problems.

Get SchedulesDirect and do on update a day and you don't need manual recordings either. Get it soon as the price increases next month.

Martin

[JJ202302250834]

Recordings are still terminating prematurely.
1) Completely uninstalled NextPVR version 6.1.1.221106 including user and public profiles.
2) Reinstalled NextPVR version 6.1.1.221106.
3) Turned EPG completely off.
4) Ran a couple of tests which worked fine.
5) Recent recordings indicate recordings completed successfully.
6) Of the four recordings made over night two worked and two failed.
The two recordings that failed, backup and Kolchak` The Night Stalker, appear to end prematurely at the same time.

[mvallevand]

Sub will need to look it appears NextPVR is getting confused with the heavy pre and post padding you have on an manual recording. Perhaps remove the padding and see if the test works better. You probably would not have this issue with Schedules Direct data.

It starts 30 minutes early as expected

Code:

2023-02-25 22:30:00.083    [DEBUG][9]    About to start recording (850 on 21): V:\Rippers\NextPVR\Manual Recordings\Kolchak The Night Stalker_20230225_23000000.ts
2023-02-25 22:30:00.083    [DEBUG][9]    (Recording is due to be stopped at 2/26/2023 12:00 AM)
2023-02-25 22:30:00.731    [DEBUG][9]    <stream>
  <handle>4</handle>
  <reason></reason>
</stream>
....
2023-02-26 00:30:00.080    [DEBUG][9]    Stopping recording (850 on 21). Past end time of recording. 4
2023-02-26 00:30:00.179    [DEBUG][9]    http://localhost:52541/stream/stop?handle=4

Martin

[JJ202302250834]

To test the theory of heavy pre/post padding I made a series of test recordings today with 1 minute pre and post padding. Here is the result.

Title, Recording Time, Actual Time
It’s Alive, 02:12:00, 02:12:03.460
Bad Moon, 02:52:00, 02:52:04.140
Saturday the 14th, 02:42:00, 02:42:03.480
House, 02:32:00, 00:13:00.360 stopped
Scream of Fear, 03:02:00, 02:13:01.060, stopped
The Beast With Five Fingers, 01:52:00, 01:52:03.740
Foreign Correspondent, 03:41:56, 03:41:56.760

As you can see, House and Scream of Fear stopped prematurely.

[mvallevand]

Sub needs to look at multi-rec and manual recordings. I can't figure out how you are scheduling but if you use NextPVR.exe could you try using the web to see if things are different.

Martin

[JJ202302250834]

I set up test recordings for today 2023-02-28 with 1 minute pre/post padding and will see how it goes and let you know. I have attached both the NextPVR.exe and the web schedule. They look the same to me.

[mvallevand]

Seeing the overlap that still looks like 30 minutes of pre and post processing, which is heavy use of mult-rec. In theory it should work but that is what has been causing the early stop. These are all from one channel which may or maybe not be the same test.

Martin