Hauppauge Nova-T-500 tune missing channel 2 from one device (1 Viewer)

[VidarParry]

Hi all,

I suspect this is a hardware problem in my Hauppauge Nova-T-500, so I thought I'd run this quickly by the wealth of experience on this forum before I go and buy a replacement card!

When tuning device 0, it gets to channel 2 and times out. All other channels tune and work OK.

Tuning device 1 finds the same channels as Device 0, plus the 3 channels on channel 2.

I'm assuming that there is a fault in device 0 on the Hauppage card to do with channel 2.

Is this a reasonable assumption, or could something else be causing this issue?

Cheers
...Steve

PS Great work with MP1 guys - far far better than 0.2.3)

 

[Paranoid Delusion]

Uninstall the drivers, then try reseating the card in the pci slot and then reinstall the drivers.

I think i would delete the database when uninstalling TVServer, and you should be using TVServer + client from svn 19069 to overcome the decompose error, and of course install the mediaportal part of the release first, before the tvserver client plugin gets installed.

 

[VidarParry]

Thanks Ray.

Will try and get some time tomorrow to try this out and report!

Cheers
...Steve

 

[VidarParry]

Hi Ray,

Uninstalled drivers, reseated card, installed latest drivers.

Then I re-scanned both tuners and the same problem occurred.

Attached are the TV Server logs from the latest tune attempt - Channel 2 says no signal and loss me the three channel 9 stations on that tuner.

Any help appreciated.

Cheers
...Steve

 

[Paranoid Delusion]

Hi Steve

Are you running xp on this m\c, have you got the dvbfix installed, thats the only other thing i know of that can affect scanning, besides Aerial\cable issues.

 

[VidarParry]

Hi Ray,
Yes, I have the dvbfix installed. I'm running XP SP3.

As the t-500 has a single antenna input and the other tuner on the same card is working for tp2, I'm still thinking it's a hardware fault in the T-500 card.

Cheers
...Steve

 

[VidarParry]

Hi all,

I'm delighted to say that althought this problem exhibited itself RC3 (and RC3 SVNs), it finally works fine in RC4

So it seems something in MP software was the cause all along.

BTW, RC4 has been the MOST RELIABLE version I have seen to date - well done guys and gals!!

Cheers
...Steve