NEXTPVR ending some recordings early

[locanda]

Since the latest update, I have some recordings ending early, with no failure notice in the What's New panel.

That is, for instance in the logs, a recording of #5504 Sherlock - The Final Problem - set for 2 hours (17:00 - 19:00). As near as I can tell from my scan of the logs, it ran the correct times. However, the resulting file is approx. only 1 hour, 40 minutes long. Other recordings have been similarly trimmed, although most others still record properly for the entire length.

As a separate issue, recording on a strong channel, I get some reported complete failures (usually 0 bytes). For instance, set 4 sitcoms, each 1/2 hour, one after the other. First records OK, whereas some of the following ones fail. Not due to a weak signal.

Recording is through 2 HD HomeRuns, directly attached to a fast recording computer (Win 8.1 64-bit) via a gigabyte switch. Digital antenna (not cable) connection.

Thanks for any help,


Kevin

[sub]

What do you have the application set to in the HDHR Settings utility? Make sure it's set to Default or Mediaportal, not NextPVR...otherwise you can get the symptons you describe.

[locanda]

What do you have the application set to in the HDHR Settings utility? Make sure it's set to Default or Mediaportal, not NextPVR...otherwise you can get the symptoms you describe.

The Main Application pull-down has always been set to "Other: ATSC/QAM", which I think was according to instructions for earlier versions of NextPVR. There is no Default entry, but I can set it for MediaPortal. HDHomeRun Setup Version 20140604.

[locanda]

After Applying that, I was offered an option to update the HDHomeRun utility. Before I allow that, is that going to lose all my channel settings?

[mvallevand]

Other should be ok with the older firmware but perhaps there are other fixes. It won't impact your NextPVR configuration.

Martin.

[ccihon]

Other should be ok with the older firmware but perhaps there are other fixes. It won't impact your NextPVR configuration.

Martin.

The older config utility and firmware for HDHR listed "Other ATSC/QAM" and that was the desired setting - later versions of firmware, including current, don't offer that choice, but rather "Default" (not the same and not desired for NPVR) and through trial and error, the best choice with latest version is Mediaportal or J River. The default setting seems to generate a stream that causes many failures in playback. Sad thing is that I think the earlier firmware as yours is worked "better" at this, but I was forced to upgrade when my Dual ATSC unit would continuously boot-loop as it was unable to connect to SD with the older version.

At some point, you might think the SiliconDust guys would either create a correct profile for NPVR or remove the erroneous one from their list.

[locanda]

Oh well, hasn't solved the problem yet. I still have to load the newer HDHR Setup software. 2 recordings I ran last night ended short by 36 minutes, but no problem reported on the NextPVR's What's New page. One, "Frequency" set for 1 hour, recorded for 24 minutes, 17 seconds. Another, "Victoria" was set for 2 hours, recorded 1 hour 24 minutes, 17 seconds. Got to wonder if that is a significant #. All other recordings that night seem fine and recorded their complete lengths. I've attached the latest logs. After this next round of recordings, I'll update the HDHR Setup & see if that makes any difference.

[mvallevand]

From one of your bad files can you extract the Timing.Info file and zip and upload it here so we can see when data stopped being deliver To extract

copy filename:Timing.Info Timing.Info

Are all your recordings manual? If so maybe consider getting using Schedules Direct for $2 a month it will save you some time

Martin

[locanda]

Sorry, don't have any Timing.info file in any of the zipped logs, or understand how I would get it out of a .ts (Transport Stream) recording. Yes, all recordings are manually input. I'm not sure I see any value in a Scheduling service. Usually, when data stops being delivered to NextPVR, the What's New tab has a failure notice in red indicating that. It does happen on a couple of marginal channels with a weak signal. The problem I am having occurs on strong signal channels that normally record quite well.

[mvallevand]

Timing.Info is not with the logs, is part of a NextPVR recording stored using Windows ADS. The example I gave shows how to get Timing.Info from the command prompt if you are in the folder with the file.

Martin