progdvb.com

will prog work whit Hauppauge! WinTV-HVR4000

I am also having problems with my WinTV-HVR4000 card.
I am using the ProvDVB elecard edition.
(but have tried the normal version as well)

When I look for devices in the device settings list, no BDA DVB-S options show up.

Only some BDA devices for DVB-T show up, but I cannot use them for DVB-S.

I tried to use the MyTheather program, this one does correctly find both the BDA for DVB-S as well as the BDA for DVB-T, which is correct as the HVR-4000 has both a DVB-S as well as a DVB-T receiver on the card.
(next to an analog tv-receiver as well)

I do prefer the ProgDVB program to the MyTheather so hopefully will the issues be solved.

Uno

if you don´t have a bda (dvb-s) device :

save this as ´bda.reg´ and execute it to get the missing devices....





Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\42]
@="{B64016F3-C9A2-4066-96F0-BD9563314726}"
"Name"="TT-DVB-S"
"Description"="DVB-S Tuning Space Entry"
"Network Type"="{FA4B375A-45B4-4D45-8440-263957B11623}"
"Frequency Mapping"="ex:2d,00,31,0"
"System Type"=dword:00000002
"Network ID"=dword:ffffffff
"High Oscillator Frequency"=dword:00a1be40
"Low Oscillator Frequency"=dword:0094c5f0
"LNB Switch Frequency"=dword:00b28720
"Input Range"="ex:2d,00,31,0"
"Spectral Inversion"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\42\Default Locator]
@="{1DF7D126-4050-47F0-A7CF-4C4CA9241333}"
"Frequency"=dword:00b7e238
"InnerFECMethod"=dword:ffffffff
"InnerFECRate"=dword:ffffffff
"OuterFECMethod"=dword:ffffffff
"OuterFECRate"=dword:ffffffff
"ModulationType"=dword:00000014
"SymbolRate"=dword:00006b6c
"Polarisation"=dword:00000002
"OrbitalPosition"=dword:00000000
"Azimuth"=dword:ffffffff
"Elevation"=dword:ffffffff
"WestPosition"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\43]
@="{C6B14B32-76AA-4A86-A7AC-5C79AAF58DA7}"
"Name"="TT-DVB-C"
"Description"="DVB-C Tuning Space Entry"
"Network Type"="{DC0C0FE7-0485-4266-B93F-68FBF80ED834}"
"Frequency Mapping"="ex:2d,00,31,0"
"System Type"=dword:00000000
"Network ID"=dword:ffffffff
"Spectral Inversion"=dword:00000003

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\43\Default Locator]
@="{C531D9FD-9685-4028-8B68-6E1232079F1E}"
"Frequency"=dword:00060310
"InnerFECMethod"=dword:ffffffff
"InnerFECRate"=dword:ffffffff
"OuterFECMethod"=dword:ffffffff
"OuterFECRate"=dword:ffffffff
"ModulationType"=dword:00000003
"SymbolRate"=dword:00001af4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\44]
@="{C6B14B32-76AA-4A86-A7AC-5C79AAF58DA7}"
"Name"="TT-DVB-T"
"Description"="DVB-T Tuning Space Entry"
"Network Type"="{216C62DF-6D7F-4E9A-8571-05F14EDB766A}"
"Frequency Mapping"="ex:2d,00,31,0"
"System Type"=dword:00000001
"Network ID"=dword:ffffffff

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\44\Default Locator]
@="{9CD64701-BDF3-4D14-8E03-F12983D86664}"
"Frequency"=dword:000b0450
"InnerFECMethod"=dword:ffffffff
"InnerFECRate"=dword:ffffffff
"OuterFECMethod"=dword:ffffffff
"OuterFECRate"=dword:ffffffff
"ModulationType"=dword:ffffffff
"SymbolRate"=dword:00000000
"Bandwidth"=dword:ffffffff
"LPInnerFECMethod"=dword:ffffffff
"LPInnerFECRate"=dword:ffffffff
"HierarchyAlpha"=dword:ffffffff
"GuardInterval"=dword:ffffffff
"TransmissionMode"=dword:ffffffff
"OtherFrequencyInUse"=dword:00000000

I now added the registry keys as per your bda.reg entries.

This now gives me the following set of BDA type entries:

{BDA} Local DVB-T Digital Antenna
{BDA} Prog DVB-T Tuning-Space
{BDA} DVB-S Tuning Space Entry
{BDA} DVB-C Tuning Space Entry
{BDA} DVB-T Tuning Space Entry

When I tried to select and start the "{BDA} DVB-S Tuning Space Entry", the "{BDA} Local DVB-T Digital Antenna" also got selected and started.

(And I cannot stop the DVB-T Digital Antenna entry.)

Also if I try to setup the Settings->Diseqc menu, I now get a small box with the heading: Transponder list options, with a drop down menu, where default "All Region - All Channels" is selected. The drop down otherwise allows me to choose between different countries like: England, Finland etc.

So it still somehow looks like ProgDVB is mixing the DVB-T receiver with the DVB-S receiver on the same card and mixes it together.

Uno

Looks like I might have solved the problem, I went into regedit and deleted the "{BDA} Local DVB-T Digital Antenna" entry, the next time I started the program, I got the select LNB and Diseq dialogue, looks like it might work now. I will test some more.

Uno

I was now able to start watching some TV channels, but there are still some problems.

1. After having added my diseq and my two LNB, I go to the "menu scan for channels". When I try to activate the menu showing my deseq, should this give the option of my two LNB's, 1W and 5E.
Most of the time ProgDvb hangs and uses 100% CPU when it should display those two options of LNB's. Sometime it displays them and I can scan for channels.

2. Not finding channels on LNB2. First LNB in position 1 is 1W the second LNB is at 5E. When I manage to sucessfully select 5E and scan for channels, it never finds anything at 5E, always come up empty.
1W is OK.

3. Not finding S2 HD channels. When scanning for channels automatically or even doing it manually on a specific transponder, the receiver does not pick up any of the S2 HD signals.
I'm trying this at 1W, 11434 V and at 1W, 12380V both should have DVB-S2 signals.

Uno

ProgDVB cannot control DiSEqC on BDA devices for now.
This would require special support from the manufacturer and occasionally microsoft, not available for free(ware).

Also some necessary special DVB-S2 controls aren't available from the SDK ProgDVB bases on.

So we would surely have to wait, until the necessary knowledge occasionally get's public, to patch either ProgDVB or a BDA device file...

Thanks for the replies.

I guess that the the HVR-4000 is currently only (partly) supported under the BDA driver, does this mean that ProvDbv will only what BDA provides or are you working on getting ProgDvb to run with some kind of native Hauppauge drivers as well?

Or does Hauppauge not release any alternative drivers or SDKs?
I'm not sure what the Linux world would do in this case.

So if I wish to watch HD-S2 tv is the only card you curently support is the new Technotrend or are there other options?

Uno

SiLencer wrote:if you don´t have a bda (dvb-s) device :

save this as ´bda.reg´ and execute it to get the missing devices....

"Spectral Inversion"=dword:00000002

I would suggest to set the "Spectral Inversion"=dword:00000002 to "Spectral Inversion"=dword:00000001.
This setting sets the Spectral Inversion to "Automatic" instead of "Inverted".
If "Inverted" is selected, some frequencies/channels maybe miss.

Greetings
Tom

Delete "Local DVB-T Digital Antenna", that was the Information where i need

There is a bug in DVBProg Device selector, i delete the Registry Entry and now my HVR-4000 works


The dba.reg is not need....

Ps: HDTV: Astra HD works

Here the Registry Entry to delete:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\7]
@="{C6B14B32-76AA-4A86-A7AC-5C79AAF58DA7}"
"Name"="DVB-T"
"Description"="Local DVB-T Digital Antenna"
"Network Type"="{216C62DF-6D7F-4e9a-8571-05F14EDB766A}"
"System Type"=dword:00000001
"Network ID"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tuning Spaces\7\Default Locator]
@="{9CD64701-BDF3-4D14-8E03-F12983D86664}"
"Frequency"=dword:ffffffff
"InnerFECMethod"=dword:ffffffff
"InnerFECRate"=dword:ffffffff
"OuterFECMethod"=dword:ffffffff
"OuterFECRate"=dword:ffffffff
"ModulationType"=dword:ffffffff
"SymbolRate"=dword:ffffffff
"Bandwidth"=dword:ffffffff
"LPInnerFECMethod"=dword:ffffffff
"LPInnerFECRate"=dword:ffffffff
"HierarchyAlpha"=dword:ffffffff
"GuardInterval"=dword:ffffffff
"TransmissionMode"=dword:ffffffff
"OtherFrequencyInUse"=dword:ffffffff

The BDA-problem with this card seems to have been solved with the latest version of ProgDVB.

Now the next issue (at least for me) is the lack of proper diseqc-support in just about every dvb-program there is, because of those crappy BDA-drivers.

Has anyone gotten this card to work with an "advanced" diseqc setup with ANY application at all?

What would you need to improve the support for the HVR-4000 in ProgDVB? I read some other place that there's the possibility of putting something together if we can get the raw diseqc commands the card uses from Hauppauge. Is that information correct?

My problems aside, great program, keep up the excellent work!

(Status now is it detects the card properly, I think, but I can only scan the first LNB)