Failed Recording

[scaesare]

Alright.... done.

Will see if that makes a difference...

[mvallevand]

If you can detect a recording that is failing while recording check hdhomerun_config_gui.exe to see what the signal strength is.

Also if it still fails make sure you have the current Silicondust software and firmware and also check that the BDA driver is configured for NextPVR. Otherwise some streams will be bad.

Martin

[scaesare]

I'll check during the recording times and see if I can catch it, and check signal strength, but I've never seen less than 100% on NBC in my area, so hopefully not that.

So nothing on the NextPVR wiki I can find about configuring the BDA Driver, but incidentally, I see there's an updated HDHR installation file on the SiliconDust site and now the install wizard has a setting for NextPVR DBA Compatibility mode. I actually am not sure I ever saw that before... I may have only installed the viewing app. Any other configuration here recommended? There's a DBA Virtual Table Mode.. as well...

That update also contains newer firmware, although the change log doesn;t look like it has much for my model:

- Release for HDHR5 and newer models. The latest firmware for HDHR4 and HDTC is 20230713.
- ATSC3 models: Fix handling of entity-mode segments delivered in dash-tar format (TECH and DEV models).

If there's any docs on this, mind pointing me at it?

Thanks.

[mvallevand]

There has been a BDA setting for NextPVR for a long time, however it was actually not sending the correct ts format so we were recommending other settings. That was corrected a few years ago too.

Most people don't use BDA anymore and use http streaming on the on legacy devices, albeit with the lose of multi-rec. With quad tuners from SD now the norm that isn't much of a lose.

Martin

[scaesare]

Ah ok.

So on the SD config page it says, in No Not Use the HDHR entries in the NextPVR devices setup.

Assume that's correct?

[mvallevand]

That reference was true for v4 only but the issue was addressed as the page partially alludes to at the top. HDHR in NextPVR is preferred by many over ATSC (or QAM) ATSC mode uses BDA and if you use BDA use the current firmware and configure it for NextPVR.

Martin

[scaesare]

OK, not trying to belabor this, I just think I have disconnect in understanding what I think you are suggesting and the NextPVR setup instructions at https://github.com/sub3/NextPVR/wiki/setup-hdhomerun. where it shows just the HDHR device...

My NextPVR installation sees 3 pairs of devices: ATSC, QAM, and HDHR.

My assumption was that I should scan for channels on both the ATSC and QAM device tuners (and I'm copying from device 1 to 2 as you suggest), and that I should leave the HDHR devices blank. Is this corr3ct that I only use HDHR _or_ ATSC/QAM device, but not both?

So it sounds like "many prefer" the HDHR devices instead of ATSC/BDA (and I assume QAM?)

Is there anything that explains the pros/cons of using one over the other, I don't want to tie you up... but do appreciate it.

[mvallevand]

I explained ATSC already BDA supports multi-rec. It is not clear from the wiki but HDHR mode doesn't go through a long scan it copies the HDHR favourites. HDHR mode doesn't need re-scanning as often either unless channels have different major minor numbers. With BDA there are hidden values.

Probably the key strong point for HDHR mode is on non legacy device it is being able to use TCP and not UDP. UDP doesn't guarantee packet delivery or order. For legacy devices it is still UDP.

Martin

[scaesare]

So, if I want to use HDHR mode, I trash the ATSC/QAM entries and just scan for channels on the HDHR devices?

[scaesare]

Well, I did define the HDHR channels only, and left the ATSC/QAM channels blank, and the last couple of recordings worked fine.

I'll see if the problem crops up again... thanks once more for your help.