HDHomeRun: Have received 0 byte from rtp source

[calande]

Hello,

I was having frequent "Have received 0 byte from rtp source" error messages on my NextPVR Docker container (Linux arm32v7). I use a SiliconDust HDHomeRun tuner.

I decided to install NextPVR on my Linux x64 desktop computer. I still have this error message, recordings are either aborted or don't start altogether. EPG updates are disabled. I'm able to tune in and record from this DVB-T tuner seamlessly using DVBViewer, on a Windows 11 computer (never had any recording aborted).

Do you know how we could troubleshoot this problem?

Thank you.

[mvallevand]

No logs no problem. Do you know if the issue generally occur if there are multiple being used? If so there is a positive change for UDP and RTP Linux processing in the next version.

Martin

[calande]

Thank you Martin.  I just uploaded the logs here. The error shows up at this line:

Code:

2026-01-25 21:05:32.031 [DEBUG][113] Have received 0 bytes from rtp source

Do you know if the issue generally occur if there are multiple being used?

I haven't noticed, however, in today's error, NextPVR was trying to connect to the tuner, while another DVB client was watching TV on this tuner (but it is a dual tuner, both clients were requesting the same TV channel, and one tuner was unused when tuning in).

[mvallevand]

That probably isn't the same thing, I expect just a tuning or networking issue outside of NextPVR's control.

Martin

[BrettB]

I haven't noticed, however, in today's error, NextPVR was trying to connect to the tuner, while another DVB client was watching TV on this tuner (but it is a dual tuner, both clients were requesting the same TV channel, and one tuner was unused when tuning in).

When you say "another DVB client was watching TV on this tuner", do you mean something completely outside of NextPVR? If so, then this would be expected behavior. If you set up and enable a tuner in NextPVR, then it expects to be able to use that tuner any time that it isn't already using it for something else. If it tries to use a tuner, but the tuner is being used by some other system, then NextPVR obviously won't receive any data from the tuner.

[mvallevand]

Good call Brett I just confirmed that RTP in HDHR model on the legacy tuners being stateless wpn't return an error on the connect, the newer HTTP models would fail over to the unused tuner.

Martin

[calande]

When you say "another DVB client was watching TV on this tuner", do you mean something completely outside of NextPVR?

Yes (DVBViewer).

If so, then this would be expected behavior. If you set up and enable a tuner in NextPVR, then it expects to be able to use that tuner any time that it isn't already using it for something else. If it tries to use a tuner, but the tuner is being used by some other system, then NextPVR obviously won't receive any data from the tuner.

Yes... I thought this would always work, as this tuner is a dual model (I sometimes use both tuners at the same time without problem). I did a few more tests here and didn't notice any repeatable pattern: sometimes the scheduled recording works as expected, sometimes it doesn't (regardless of other DVB clients using the other available tuner or not).

[calande]

the newer HTTP models would fail over to the unused tuner

Thank you Martin. I took a look at the config.xml file, as I'm searching for a possible setting to enable, so that NextPVR switches over to the second DVB-T tuner available, in case the first one doesn't send any data. Do you know if this is possible?

[mvallevand]

To give tuner1 priority over tuner0 you can use the web device settings page and use the arrows on the right to move them up or down. Also in config.xml change this to false to use the same priority

<ReversePriorityForLiveTV>false</ReversePriorityForLiveTV>

I expect the next version of NextPVR will address this based on testing here. The better option is to use networked clients to one NextPVR backend.

Martin

[calande]

Thanks Martin for the information. I'm trying a new strategy here: I'm compartmentalizing both tuners of my HDHomeRun Dual:
1°) I disabled tuner 0 and kept tuner 1 enabled, in NextPVR's device list
2°) I kept enabled tuner 0 and disabled tuner 1, in other DVB-T clients (i.e. DVBViewer, HDHomeRun's Android TV app)
All EPG is updated manually, and strictly from XMLTV (no OTA DVB EPG).
Let's see if this works better. So far, so good, no recording aborted.