Do you have logs or information about diseqc commands?

ps: Now hardware diseq logger and have logs from cable.

I found the problem .
The diseqc information is stored in the channel list database, not in the diseqc tree .
So, if you do a change in the diseqc tree you must delete and cant use the old channel list.
I removed the old channel list, did a new scan, and now the diseqc messages are ok!

So: when changediseqc devices configuration, you must remove afected channel lists from database, and rescan satellites again. Thats not optional, have to do, or there will be problems.

Sorry about all the noise , but that was not obvious to me (and for many, I guess)

ProgDVB store links to nodes of TV Sources in channel list. You can change this links in channel properties (for group of channels also).

But I am not sure about good support of multiswitch and modern hauppuage. Gambit please ask me if still any problems.

Prog, I dont know anything about multswitchs, but as we are in a so productive discussion, I will ask you for fixing an old bug of diseqc.
Its about cascade devices.
The problem in short is: the diseqc tree sequence is not regard when sending the diseqc messages. It seems that the more distant devices (from the receiver) are beeing called first. Thats an absurd.

Let´s do an example tree:

Dvbcard -> diseqc 1.0 switch -> diseqc 1.1 switch -> LNB.

The logic messages should be:
E0 10 38 Fx -> E0 10 39 Fx.

But Progdvb sents the message to more distant switch first:
E0 10 39 Fx -> E0 10 38 Fx.

The absurd of this is: if the more distant switch is not yet powered, how it will respond to the message sent to it?
Only the near device will respond correct in this way, the more distant ones will stuck in their default position (port1 of each, normally).

So, obey the diseqc tree design (chain of devices from near to distant) when sending messages to get correct operation of them.

marec: Please post of new thread. You messages very interesting but not about Hauppuage.

ProgDVB is working fine. However I have a feature request concerning multiswitches. In the Logs I saw that if you use a Diseqc switch tree in "TV sources", it only sents Diseqc commands for satellite switching. I assume that H/V and low/high switching are done by 18/14V and 22k-signal, which doesn't seem to work properly on the HD-S2. But I also read here (unfortunately only in German) that:

Many DiSEqC multiswitches can be completely controlles via DiSEqC (not only sat-position but also the selection of the IF level [V/H high/low]). Many devices ignore the usual switching criteria (LNB voltage, 22k signal) after receiving such [DiSEqC] commands until the next reset.

I would suggest adding an option of completely control the multiswitch via DiSEqC (sending commands on satellite, V/H and high/low switching) to the selection in the "Add Switch" dialog instead of only sending a command on satellite switching.

In fact, I'm doing just that at the moment, because "Send DiSEqC commands in every tuner lock" forces ProgDVB to send DiSEqC-commands on every channel switch, which means that V/H high/low switching is done via DiSEqC.

But I can just leave this option enabled and you don't have to do anything. I just thought that it unnecessary to send DiSEqC commands on every channel switching.

Occasion when to send diseqc messages is something long time confusing in Progdvb.

To my understand, "send diseqc messages every tuner lock " is mandatory, not subject to user option.

A tuner lock will occur allong every transponder change, obviously. And just before that tuner lock, must come a diseqc message. For "multiswitchs" with simple band/polarization LNBs, or "Diseqc LNBs" that message is fundamental. For using universal LNB it doesnt do any effect.

I guess there may have only two options to the user, just to try fight bad dvb cards or bad switchs issues:

1- Lock tuner in every CHANNEL change (for card/codecs issues)

2- Send diseqc commands in every CHANNEL changing (for problematic switchs)

Well, as English people say, "thats just my two cents..."

"multiswitches can be completely controlles via DiSEqC"==" Send diseq commands for every in every tuner lock"?

Gambit just complained that Progdvb is not always sending diseqc messages when changing transponders.
It is the same a explained above. Sending diseqc messages when changing transponders is a must, not a user option .

Prog, I thougt a little more of the problem, and have a suggestion:

If you implement as standard to send diseqc messages every tuner lock ( i. e. always when changing frequency/polarization), then the only necessary option will be:

"Lock tuner in every channel change".

This will simplify use of Progdvb and its coding, a little.
Users may only use this option if they have problems in their instalation, because channel changing will be slightly slower.

What you think?

I got a little bit confused, sorry Prog, but I agree with marec that it would be more user-friedly if the "Send DiSEqC commands in every tuner lock" option would be automatically enabled when using a DiSEqC switch in the "TV sources" tree and only to be manually disabled if there are any problems with DiSEqC. Controlling the switch completely via DiSEqC is the preferred way today (at least my multiswitch's manual states that) and maybe it prevents some trouble for people with their multiswitches (and their Hauppauge cards ).

For me the problem is solved. (Maybe the tread title should state that?) I thank you for your support.

PS: Just purchased ProgDVB

(c) add support of this type of multiswitch.

Gambit: Please try uncheck options and add change diseq type to multiswitch in TV Source. It is better (more fast) then old way.

I installed the pre-release version and can confirm that everything works perfect with the new Multiswitch option. ("Send DiSEqC commands in every tuner lock" unchecked, as you said)

Good. Please ask me if any problems. Not many user have this device.

It's great! Just works!
But if you want more futures (LAN streaming is my preferred one) u should try DVB Dream.