HDHR channel scanning

[sub]

Do a scan and post the config.exe.log and config.exe-native.log and we'll see if anything stands out.

The usual reason for a HDHR user not picking up any channels is firewall software getting in the way. The HDHR installer adds firewall expections for commonly used apps like its own player, or WMP, but not GB-PVR... so it's at the mercy of whether your firewall allows data from your HDHR to GB-PVR.

[rangerdave]

Its not that it doesn't pick up any channels. It finds them just fine. If I go into the scan then hit stop on 2 of 19 or 3 of 19, it finds dozens of channels. It just won't get all the way through a scan.

Like I said, I have the windows firewall disabled (I added config and the pvrx2 exe's to the exceptions anyways and that had no effect). The fact that it finds some of the channels lets me to believe this isn't the case. I have a network monitor running and it looks like network transfer still occurs after the "freeze", however I have let it sit in frozen state for 6 hours and it never comes out of it. I have tried every possible thing I can think of. With Windows Media Center 7, it just works with no fuss. I can also use all the HDHR software and watch tv without problems.

Here are the logs of me doing the entire setup for the HDHR Tuner 0, along with screenshot of the interface so you can see what I see. Anything you can do to help would be appreciated. I really want to use this software instead of the Windows stuff.

Thanks

Ranger

[sub]

I can only guess there is something in one of your broadcaster's streams that GB-PVR doesnt like.

Does it always stopp at the same progress point in the scan?

[rangerdave]

I can only guess there is something in one of your broadcaster's streams that GB-PVR doesnt like.

Does it always stopp at the same progress point in the scan?

Sub,

Nope, it is not stopping consistently in the same spot.

New customer to the HDHR and to GB-PVR, and I seem to have fallen into this mess. Win7 64bit and a new HDHR dual tuner hooked to Comcast Cable for QAM. I cannot scan channels, so essentially I can't do anything. Gets to 6 of 19 (i've seen it get as high as 12 of 19, or as low as 4 of 19) and it freezes.

I have never seen it get above 12 though. And as I said, I have tried adjusting the scan times in the config file as well, that seems to do nothing but make it take longer.

Any other diagnostics I can run? This whole thread seems to be about people having the same problem as me. So, this doesn't seem like something new, just new for me since I just bought the equipment. If you want to give me some code with extra logging to run, i'm more than willing to help and work with you for a solution.

Ranger

[sub]

I would normally offer to give you patches to help pinpoint the cause, but unfortunately thats not possible at this stage. My development environment for the next build is no longer compatible with 1.4.7 (due to compiler version change, changes to interfaces etc), so unfortunately I'm not able to do much until the next release is out.

[rangerdave]

I just tried to do a manual scan with each frequency from the qam.ini file. The first two worked just fine, when I got to the third one, I got the config program stuck in a loop. It just keep putting the same channel in the box, hundreds of times. Plus I got some exceptions in the logs.

I've attached them.

So, if I can't get a patch, do you have a beta of the new version or something I could test and that you are able to make patches for? I'm all for helping you make this software as robust as possible.

Ranger

[sub]

So, if I can't get a patch, do you have a beta of the new version or something I could test and that you are able to make patches for? I'm all for helping you make this software as robust as possible.

Sorry, unfortunately I cant do that right. Its bad timing, since I'm not ready to distribute pre-release builds any wider at this stage.

[rangerdave]

Bummer.

Any thoughts on the looping issue and the new logs?

When roughly should I check back for the new release, are we talking a couple weeks, or a couple months, or like 6 months or more?

Thanks

Ranger

[sub]

Any thoughts on the looping issue and the new logs?

The cause isnt immediately obvious in the logs. I can see the general area the problem is occurring in the logs, but not the specific problem.

What cable frequency set do you have selected in your capture source settings? It looks like it could be to do with the .ini file of frequencies.

When roughly should I check back for the new release, are we talking a couple weeks, or a couple months, or like 6 months or more?

I'm hoping for 'couple of weeks'.

[rangerdave]

Here is my qam.ini file generated by the HDHR. It is set to the Standard Cable Frequencies, which from what I tell pull the 19 frequencies from that file. That is what I read on the install directions for the using GBPVR with the HDHR.

The third frequency on that list is the one that caused the looping condition.

Thanks again for your time.

Ranger