Recordings before end of schedule

[Cosmo]

Hey first of all, I am so grateful for this program and the active support provided. It's been flawless for me for years.

That said, I'm having an issue with some recordings where they begin but then partway through data just stops being delivered. The service appears to still be running and the log even shows when the tuner gets released at the proper time. Recording id 21757 in my nrecord.log.2 is an example. I think this is only happens with long recordings (>2 hours, just a guess). FWIW I don't think this was an issue in prior versions. Any help is greatly appreciated.

PS I had to delete the npvr.log.3 and web.log.3 which didn't cover the time of interest due to size restrictions.

[mvallevand]

If you still have the recorded file extract the timing.info file from it zip it up and post it. I don't think "more" works to extract it on Windows 10 so you need to try notepad filename:Timing.Info then save that file.

Martin

[Cosmo]

Thanks for the reply. Here's what I got extracting the timing info.

[mvallevand]

That is interesting and doesn't show what I expected but it looks like a 96 minute recording, I thought it might grow in time with zero bytes I am not sure if your 15 minutes of pre-padding and 89 minutes of post padding impact things at all. Sorry I can't help further maybe sub can find something.

Martin

[Cosmo]

Thank you very much for taking the time to look. I'll see if I can replicate it with the next airing (though hopefully not ).

[sub]

How big was the file you ended up with on disk?

[Cosmo]

Here's what I got:
File size : 10.8 GiB
Duration : 1 h 36 min

[sub]

It is a little hard to follow your logs for that recording, because there is other stuff happening at the same time. There is an unexpected gap of a few hours in the logs though, before the recording is eventually stopped. (like the machine had been put to sleep, but it'd normally note that in the logs)

Might be worth trying to do a long recording without the extra stuff happening, and if it still fails, post the logs again so we can take another look.

[johnsonx42]

one wonders why NRecord.log.2 is so short without a proper end, and why there's no NRecord.log.1?

perhaps you have a c:\temp directory, and perhaps there's a crash.mdmp file in there?

or perhaps you have something in the Windows Application Event Log for late on 2/9 or the wee hours of 2/10?

[Cosmo]

Hey so there was a re-air of this same program last evening and I got the exact same result. I also had another recording with that started part way through the other recording that completed fine. The re-air (recording 21840) began at 22:27 and delivered data for ~94 minutes (~00:04) which is the same as last time, but i had minimal padding on it this time, then died out. Again,the log said it stopped at the proper time, 01:33. My other recording (21998) started at 00:15 ran its course successfully. I've attached my logs again along with timing, if any of you have any time to take a look, I'd greatly appreciate it. To Sub's point - I don't know if there was less going on, at the least i wasn't actively watching live tv on any client devices at the time. I did check my windows logs and the computer never went to sleep and I don't see anything that indicates a loss of connectivity. I have a crash.mdmp file, but it's modified date (for whatever that's worth) is from a couple weeks ago and it is not readable to me. I've attached it anyway if it can be of any help.

I probably should have specified this at first but I don't know if it matters - I'm running this on windows server 2012r2.