After installing 5.16.2 i got some new screens in start phase:
1) while starting the settings screen (cards, switch, LNBs) is displayed and has to be closed with CANCEL (if OK it will be redisplayed).
2) while starting an information screen is displayed to install Elecard H264
but in options, direct show, custom only Cyberlink modules are selected.

Any idea how to prevent this displays?

How may I attach screenshots about the display?

1. You must setup all devices in this dialog.
2. ProgDVB try render default graph if selected filters not work.

If you want to post pictures, you have to upload them somewhere else before and place links.

Prog wrote:1. You must setup all devices in this dialog.

Thanks.
How may I find the correct setting? I defined:
713x BDA DVBS Tuner
Switch (22kHz 2 ports)
Astra 19.2 (KU band, power, LOF1 9750, switch 11700, LOF2 10600)
Hotbird 13.0 (KU band, power, LOF1 9750, switch 11700, LOF2 10600)
but the second LNB is not found.

In a working receiver box DiSEqC 22kHz and LNB #1 and LANB #2 is defined.

How may I define the same in ProgDVB?
What is the meaning of parm 'switch 11700' at a 22kHz switch?

Thanks in advance

Ku band is to wide to fit through the LNB cable in one.
That's why the band gets splitted, switched between the parts with 22kHz carrier off (low band) or on (high band).
The switch value determines, up from which frequency the 22kHz tone gets activated.
Default is OK for all European style Universal LNBs, though it could be set to anywhere between 11550 to 11900 MHz without losing transponders, as the part bands do overlap. The transponders between that limits can be tuned in both bands, which way ever works better on your system.

BUT you can only use 22kHz controls on one stage of your system, either for band switching, or for position switching, not both.
So find out what kind your position switch really is of. Normally it would be either Tone Burst (simple) or DiSEqC 1.0, not 22kHz. Else get rid of it...
22kHz position switches simply don't work with Universal LNBs, as the 22kHz continuous carrier can't be on for High Band but off for the first position at the same time. Or off for Low Band but on for the second bird...

Juergen wrote: BUT you can only use 22kHz controls on one stage of your system, either for band switching, or for position switching, not both.
So find out what kind your position switch really is of. Normally it would be either Tone Burst (simple) or DiSEqC 1.0, not 22kHz. Else get rid of it...
22kHz position switches simply don't work with Universal LNBs, as the 22kHz continuous carrier can't be on for High Band but off for the first position at the same time. Or off for Low Band but on for the second bird...

Thanks for your complete technical reply, but i still dont know what to do.
I don't understand the difference of band switching and position switching and how may I can get rid of the switch?
There is no motor attached, but two LNBs each connected with 4 cable to the multiswitch (see profile) and the working receiver (hyundai HSS 730) has 22kHz with LNB #1 Astra and LNB #2 Hotbird defined. 4 devices are attached to the multiswitch. I don't find any addtional info of the "Smart MS 94BK DiseqC Multischalter".
I hope I get a more simple proposal for a configuration.

Obviously this is a multiswitch for the German market.

Such would have four inputs for each satellite.
14 (or 13) / 18 Volts would be used for polarisation switching, 14 Volts for vertical, 18 Volts for Horizontal.
22kHz would be used for band switching, off for Low Band, on for High band.
For each position, don't mix them up...

All this means, each of your Quattro LNBs provides four output ports, that must be connected to the multiswitch properly:
LV to the port with 14 Volts, 0 kHz / 22kHz off
LH to 18 Volts, 0 kHz,
HV to 14 Volts, 22kHz (on)
HH to 18 Volts, 22kHz

If you mixed up the lines in any way, your software would not be able to switch properly. You MUST NOT use 22kHz for satellite switching, as we did in early analogue days, up to fifteen years ago. Else you can't access half of each position these days. Have the Hyundai use DiSEqC for satellite position. If necessary, change LNB lines to the schedule mentioned above, for both LNBs. Verify carefully!


Voltage and 22kHz switching components of your mutiswitch are NOT entered into the LNB / DiSEqC setings, as they behave absolutely identical with Single (Universal) LNBs.

But a multiswitch with eight satellite input ports also includes a DiSEqC switch stage, normally DiSEqC 1.0 or ToneBurst, that must be entered in your LNB / DiSEqC settings, two LNBs connected there to, each to the correct port (first / second position).

Sorry, the above explanations does not help.
I dont find a valid parameter combination for ProgDVB to use both satellits. The following parameter are specified in the moment and are not valid.

[Tuner_0]
ID=5
CableTransponderList=
Caption={BDA} 713x BDA DVBS Tuner
DevID=66FF86C802626461006465766984
[Tuner_0_0]
ID=2
Type=3
[Tuner_0_0_0]
ID=1
ListName=192;0
LOF1=9750000
LOF2=10600000
Switch=11700000
Power=0
Type=0
[Tuner_0_0_1]
ID=1
ListName=130;0
LOF1=9750000
LOF2=10600000
Switch=11700000
Power=0
Type=0

The definitions are prompted at program start. I dont find a valid definition. A start is only possible buy canceling the prompt.
My parallel connected receiver is working with both satellits.

Either the BDA driver, the actual driver for the DVB-S adapter (see signature) or ProgDVB with this parameter are not able to handle the DISEQC 1.0 22kHz definition of my multiswitch.

Does anybody know how to change the above parameter manual or has a tip how to make the configuration run?

Once again, forget about setting up anything for 22KHz.
DiSEqC only.
To control DiSEqC with a BDA device, you have to check the device settings in ProgDVB, to enable a hardware specific patch, as BDA originally does not support DiSEqC at all. Micr0s0ft simply forgot to add DiSEqC to that driver architecture. That's why each hardware concept must have a patch selected.
For many tuners, one of the included patches would work, but for some others, one more may yet be missing...

All three posssible switch definition (simple, 22kHz, Disecq) are not valid, without any message or log.
Why does ProgDVB doesnt show the reason for a wrong device definition?
Where do I find the mentioned patches?
Which modules have to be patched?
Does anybody know the syntax of the above statements in the *.ini file?

In ProgDVB, open Device Options.
There in you can select some hardware concept specific option switch. That's what I've meant by "patches"
And then try "DiSEqC" again. "Simple" might also work for two positions, but "22kHz" surely won't, as this results in a conflict with band switching.

Juergen wrote:In ... Device Options...

Thanks, I tried to change this options, but the parameter will not change each time.
Some time the change will persist.
Do I need a restart after changing the option?

My TV-card has Phillips chips, do you know which of the optional cards use the same chips?

Yes, ProgDVB should be restarted after device option changes, to be sure.
And it may even make sense, to restart the computer each time, as long as you're testing on those. Just to allow the drivers to be reloaded...

No, I don't know the inside of that BDA devices, as I don't have them, and in most cases, details are non-public. No idea, if Prog knows more about this.