Recording deleted upon restart after stopping active recording

[Lone_Stranger]

While recording a couple of programs, I intentionally shutdown the recording service. I did this in order to implement 3.8.3 this evening. I fully expected to have a "service was restarted" message, with a related loss of a couple minutes of data. I then installed 3.8.3, and restarted the service and NPVR task. Everything worked as expected.

When I restarted NPVR, the recording service restarted the recording, as expected. However, it also deleted the orphan/loose/incomplete initial 27 minute recording. Had that not occurred, I would have been able to watch the complete program (minus the missing 2 minutes that were lost). What I got was a single file that was the final/2nd half of the program with a suffix of "-0".

The program in question was "On The Record with Brit Hume". The failure is described in Nrecord.log.1 at:
2016-09-27 19:27:57.074 [DEBUG][13] - deleting extra recording: E:\Recorded TV\On the Record With Brit Hume\On the Record With Brit Hume_20160927_19002000.ts (9/27/2016 11:00:09 PM)


I believe that it is normal for NPVR to restart a recording, in the event there is a system error or other catastrophic failure. If that is true, then I believe there's a problem. This has been happening since I started playing with NPVR, and I've reported it before. Each time I report it, I'm told that I should not interrupt recordings, but that doesn't make sense to me.

Logs attached....

[sub]

The program in question was "On The Record with Brit Hume". The failure is described in Nrecord.log.1 at:
2016-09-27 19:27:57.074 [DEBUG][13] - deleting extra recording: E:\Recorded TV\On the Record With Brit Hume\On the Record With Brit Hume_20160927_19002000.ts (9/27/2016 11:00:09 PM)

Is this recording set to keep a maximum of 1 recording? That's the only reason you'd get that message above. Restarting the recording service causes a second recording to be created, so it deletes the oldest one to keep to your 1 recording maximum. Easiest fix up the maximum number of recordings, or don't start the recording service during a recording

[Lone_Stranger]

As usual, you're correct and quick to respond. Thank you for that.

Yes, it is set for a single recording, as these are recorded daily, and tend to accumulate when I'm out of town.

I understand the logic, but I would consider two pieces of a single file as one, instead of treating them as separate files. Perhaps files with a suffix (-n) could be skipped? Just a thought. Thanks again.

LS

[sub]

I understand the logic, but I would consider two pieces of a single file as one, instead of treating them as separate files.

Sorry, that's just not the way it works. I can understand why you might want that, but it makes things muck more difficult, so unlikely to be a change I'll make. It's much simpler for the app to treat them as separate recordings.

[johnsonx42]

I had requested awhile back to simply not include in the count of recordings any that has any text in the "Failure Reason" field (like "Recording Service Restarted During Recording"). This doesn't mean you wouldn't delete such a recording or treat it differently in any other respect, you just wouldn't include it when counting them up. So you might have 5 recordings, but 2 of them have text in "Failure Reason" so the program counts only 3.