HDHomeRun Prime: errors with one NIC, no live tv or recording with two NICs

[JeffDwork]

With my HDHR Primes connected to my home LAN, I have intolerable error rates - hdhomerun_config reports network errors (dropped packets), recorded video freezes, audio freezes, stutters, repeats. This happens at least 2 or 3 times per hour and often more. I've tried everything - new nic, change settings, disable/uninstall firewall - nothing helps. Weird thing is that it worked perfectly from April 2013 through Sept when the truncated recordings made me give up on nPVR. When I reinstalled everything a few weeks back, the errors started.

Now I have two nics. One goes to the home LAN, the other just to the HDHR Primes through a switch. Errors are gone according to hdhomerun_config. With the HDHomeRun QuickTV I get video and audio no problem and the file from "hdhomerun_config save" plays perfectly. When I run NextPVR with either live tv or recording, I get nothing. HDHomeRun Config GUI shows that the tuner has been set to the right channel and nPVR status shows the tuner active, but there's no network traffic. I've tried openDHCP server so the primes have ip addresses and I've tried removing the switch and directly connecting the HDHR Prime to the nic. Still no good.

Help! I really like NextPVR. I've donated to the project and I will again if I can get it to work for me.

Thanks,
Jeff

My configuration:
ASUS m4a87t, Athlon II x2 250, Realtek 8111E (to LAN), Intel EXPI9301CT (to HDHR Primes)
Windows 7 SP1 current updates
NextPVR 3.1.1 R1a
two HDHomeRun Primes
Netgear switches: GS108E, GS108, GS605NA

[mvallevand]

Post your log, maybe NextPVR isn't selecting the correct card. Adding the new cards changes the firewall rules too.

Martin

[JeffDwork]

Thanks, the log tells the story. (It's not the firewall - Windows firewall is disabled, both private and public, no 3rd party firewall.)

The magic line is:
2014-02-23 17:00:11.587 [DEBUG][14] Executing: C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe 131736EA set /tuner2/target rtp://192.168.137.44:36312

The problem is that 192.168.137.44 is the IP address of the LAN interface. The interface connected to the HDHR Prime is 169.254.0.2. Running wireshark on that interface shows that HDHomeRun QuickTV does:
/tuner0/target rtp://169.254.0.2:53379
while nPVR does:
/tuner2/target rtp://192.168.137.44:36312

I see three solutions:
1) Best: get Silicondust to enhance 'hdhomerun_config discover' to report interface IP address along with device IP address. I will report this to them.

2) Worst (but maybe easiest): add 'hostIP' item to config.xml

3) Can be done without help from Silicondust:
hdhomerun_config discover
arp -a
For each HDHR IP address, find the interface.

$50 donation if this can be fixed in the next 7 days. I really don't want to have to struggle with mythtv.

Thanks,
Jeff

[mvallevand]

Make sure you are running all the r1a patches and and try making the xml file http://forums.nextpvr.com/showthread.php...post467720 (not using the attached patch)

Martin

[sub]

I must admit - it's hard to ignore $50

I've sent you a PM.

[mikeh49]

Here comes Premium/Concierge support!

[JeffDwork]

Hey, it's not like it's only for me - everybody gets the benefit. I like this program. I want it to succeed. I'm fortunate to be able to give some to support it, but I've got to be able to use it. I'm surprised that I seem to be the only one with network errors - I expected it to be more common.

Silicondust tech support pointed me at the correct solution: match the IP address of the tuner to the list of IP/netmasks of the available interfaces to find the correct one.

Jeff