Jump to content

Hauppauge 950Q not scanning frequencies


clemeb01

Recommended Posts

Hello,

I purchased DVBViewer Pro on September 8th to watch and record ATSC channels in the USA. I like this program much better than WinTV, which is what was bundled with my Hauppauge 950Q usb tuner stick.

 

I'm using: Windows 8.1 64bit operating system

6 GB memory

EVGA nForce i730 motherboard

Intel E5300 dual core 2.6GHz processor

EVGA GT520 graphics adapter

Hauppauge 950Q usb tuner

 

I am current with all windows updates. The graphics card has the latest driver. The Hauppauge 950Q is using the latest driver from the Hauppauge website.

 

My problem is that when I use the America ATSC.ini transponder list and scan for channels there are no channels discovered. I know there are 27 channels that are scattered on 10 different frequencies. This happens if the tuner has not been used with any other software during this run cycle or the tuner has just been unplugged and plugged back in. If, for example, I start WinTV and tune to one of the channels on 563 MHz and then exit the program. I'll check task manager to make sure there are no WinTV processes still running. I start DVBViewer and do a scan with the America ATSC.ini transponder list, it will find the channels associated with 563 MHz on every frequency in the transponder list. I made an accurate channel list by using my knowledge of the frequencies of the local channels and setting each frequency in WinTV and then scanning that frequency in DVBViewer. I also made a local transponder list. My channel list is called Home TV and my local transponder list is called Kansas City. I have included both with this message. In summary, I must change frequencies with a separate program from DVBViewer and then use DVBViewer. DVBViewer can change between channels that are on the same frequency. I have tried transedit and the channel scanner that is built into DVBViewer. When I tried to not use direct tuning or use standard tuning and started to scan it would say hardware could not be found or hardware could not be initialized. My hardware is found by both DVBViewer and Transedit. I do have to change tuner type from cable to ATSC.

 

I have successfully got this hardware to work with WinTV ver. 7, Easy HDTV, PotPlayer, NextPVR and VLC for Linux. I couldn't get VLC for Windows to work with this hardware.

 

Any help would be greatly appreciated.

 

 

Home TV.ini

Kansas City.ini

support.zip

Link to comment
If, for example, I start WinTV and tune to one of the channels on 563 MHz and then exit the program. (...) I start DVBViewer and do a scan with the America ATSC.ini transponder list, it will find the channels associated with 563 MHz on every frequency in the transponder list.

 

Looks like the hardware / driver doesn't accept DVBViewer tuning commands (though they are standard BDA commands). So it just stays in the state that has been set by WinTV.

 

My hardware is found by both DVBViewer and Transedit. I do have to change tuner type from cable to ATSC.

 

Just to make sure: The tuner is detected as Cable (= European DVB-C), not as ATSC, and you have to correct it manually? :blink:

Link to comment

Thanks for the quick reply! The device is detected as "WinTV HVR-950 BDA Tuner" in both DVBViewer and TransEdit. In

DVBViewer, I delete the "WinTV HVR-950 BDA Tuner" entry and press "Scan Devices", it detects "WinTV HVR-950 BDA Tuner" with the tuner type set to cable. In TransEdit, I unplug the device, delete the TransEdit.ini file from "C:\ProgramData\CMUV\DVBViewer" and start TransEdit. I go to the hardware settings, plug the device back in and it detects

"WinTV HVR-950 BDA Tuner" with tuner type set to ATSC. The Compatibility Check Tool detects it as

Unknown-DVB-C and gives it a green checkmark. I also forgot to mention in my previous post that I:

 

1. tried a fresh installation of Windows 8.1 with only DVBViewer installed. My scans came up empty in DVBViewer.

 

2. tried the 1.75 MHz offset, eg. for 563 MHz, I scanned both 561.25 MHz and 564.75 MHz. The scans were empty.

 

Thank you again for your help.

Link to comment

Sorry, I'm late... a lot of other things to do.

 

The device resp. its driver seems to have some proprietary properties :), and to be true I doubt that we can make it work without advice from Hauppauge. As far as I can see you've already tried everything that makes sense. Nevertheless we can try to find out a bit more.

 

Please store the attached TransEdit test version in the DVBViewer installation directory. It is a restricted version. Some functions are disabled, but scanning works. It performs extensive logging of the detection and device initialization process.

 

Launch the test version and perform Settings -> Hardware -> Detect Devices. Then try to scan a transponder (doesn't matter which one) and close TransEdit. After that there should be a file TransEdit_Test.txt in the configuration folder (see Info menu). Please attach it here.

TransEdit_Test_4_0_7_11.zip

Link to comment

Thank you so much for your reply! During the weekend, I decided the 950Q was not going to work for me. I bought a HDHomeRun Dual that was on sale at a local store. It works with your software wonderfully. I do like DVBViewer very much.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...