HDHomeRun instructions updated.

[whurlston]

Glad you found it useful. I created it because the HDHR uses the center frequencies but I have another tuner that does not. So I had to keep changing the qam.ini file whenever I had to rescan.

[Verus]

I followed the new instructions to enable PID filtering with 1.3.7 (app set to Custom, reg keys modified) and I'm still seeing 38Mbps over my network link. Is there something extra or additional that needs to be done to make this work? Do I need to be using a specific BDA mux as well? I'm using Vista Home Premium SP1 64 bit if that makes a difference.

I'm in the process of getting a sniffer trace to see what's going on as well.

Thanks!

[whurlston]

You should be using the "TS Mux" option. What OS are you running?

[Verus]

I just tried the TS Mux with the same result, the full 38Mbps stream is being sent over the network. I tested with the "Enable Multi-Record support" checkbox checked and unchecked with no difference. I was previously using the ATI MPEG Mux as it provides better audio/video synchronization for me than the TS Mux. OS is Vista Home Premium SP1 64 bit.

[whurlston]

Could be UAC getting in the way. Check for tuner entries in:

Code:

HKEY_CURRENT_USER\Software\Classes\VirtualStore\MACHINE\SOFTWARE\Silicondust\HDHomeRun

If you do, you may need to make the changes there as well.

The Multi-Record option should not matter in regards to filtering.

[smegal]

I installed fresh on 1.3.7 and tried the new instructions using "Custom" in the hdhomerun setup and regedit to modify keys as directed. I can see the channels using VLC but did not have success with finding channels in GBPVR capture setup. It works when I switched in hdhomerun setup to ATSC/Remap (except I lost one channel I can see with VLC that I was able to get before switching to 1.3.7)

I was using latest nonbeta HDhomerun firmware: hdhomerun_atsc_firmware_20081002.bin

WinXP SP2 and also updated to:
hdhomerun_windows_20081002.exe

Should I use the beta HDhomerun firmware?

Also a FYI, when I upgraded my windows software up came a window saying my HDhomerun power supply was defective. I typed in my address and silicondust said they would ship a new power supply. yeah. Suggest others do this in case your HDhomerun power supply is suboptimal.

[Verus]

I installed fresh on 1.3.7 and tried the new instructions using "Custom" in the hdhomerun setup and regedit to modify keys as directed. I can see the channels using VLC but did not have success with finding channels in GBPVR capture setup. It works when I switched in hdhomerun setup to ATSC/Remap (except I lost one channel I can see with VLC that I was able to get before switching to 1.3.7)

You'll need to use a qam.ini file with center frequencies and not the default qam.ini in the ~\GBPVR\BDA\ATSC directory. You can replace it (recommend backing up the original in case your other QAM tuners use it) with the one in the ~\GBPVR\BDA\ATSC\HVR1600 directory or you can use whurlston's qam.ini manager found here and build your own:
http://forums.nextpvr.com/showthread.php?t=38408

That should allow you to find channels in GBPVR with the app set to Custom in the HDHR setup. I'm curious to know if PID filtering works for you after these changes.

[whurlston]

Verus, after looking into it, I see another registry setting that needs changing. When you open HDHomeRun Setup, if you have the Signal Source set to "Digital Antenna" Or "Digital Cable", make sure the application is set to "Custom". You will then have to go back and edit the registry settings mentioned in the instructions.

[Verus]

I looked for the other registry key whurlston suggested, but I don't have that in my registry, maybe because I have UAC disabled. I decided to search my entire registry for my HDHR tuners and found another set of keys with the exact same list of entries. I'm using Vista Home Premium 64bit and it seems to use different registry keys for these HDHR settings. I had to change the following:

Code:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Silicondust\HDHomeRun\Tuners\XXXXXXXX-X

After modifying the BDAPIDFilter and ChannelMapping keys for each tuner, along with changing my BDA Mux to 'TS Mux,' the PID filtering is now working.

Is there any reason why other BDA Muxes don't work? I tried the ATI MPEG Mux and I get a zero byte file and don't see any network traffic. Just curious why the TS Mux is a requirement for this to work.

[whurlston]

Ah, I didn't realize that you were running x64. PID filtering should work with other BDA muxes. TS Mux should only be required for Multi-Record. sub would have to be the one to say definitively thought.