Please test last prerelease of ProgDVB.

ps: Do you use disabled "Use tuner request"?

On v6.61.1 I have "Use Tuner Request" enabled, but it doen't seem to matter. At least I could not find a difference. I tested the prerelease and nothing has changed. You can only recieve anything with "Use Tuner Request" disabled. But I also played with the options in Settings->Options and suddenly the previous black channel showed a picture.

Now it seems to me, that the "refreshing trick" also works in newer versions of ProgDVB. If a channel gets no signal, open Options and change something and everything works after the programm refreshed. I didn't notice it before because in ProgDVB 6.61.1 you just click OK without changing anything and it refreshes but the newer versions require you to change a setting.

I've used the channel list ProgDVB 6.61.1 created, the search in the prerelease still shows no signal on transponders with different polarisation/band. Channel search did work correctly in v6.61.1.

And same problem if you select "Microsoft" mode in same dialog?

Channel switching now works for most channels after I enabled "Lock tuner in every channel changing" and "Send DiSEq commands in every tuner lock", though the problems with channel search remain.

Do you have diseq?
What you do? Only this 2 options?

ps: this mode very slow. I am not recomend.

According to Hauppauge the Nova-HD-S2 card supports DiSEq 1.0 and the Multiswitch to which the card is connected is a Kathrein EXR 2908 which also supports DiSEq.

In fact, everything concerning channel switching only works with DiSEq in ProgDVB. In "TV Sources" I also configured both LNBs for Astra 19,2° and Hotbird 13,0° to be connected to a DiSEq 1.0 switch, because otherwise switching polarisation/bands/satellite was impossible. With DiSEq switch enabled, I could tune in all programms after "refreshing" ProgDVB via the options menu as I said in previous posts. Now with "Lock tuner in every channel changing" and "Send DiSEq commands in every tuner lock" enabled, programm switching works correctly and it isn't much slower than usual (It's also about 3-5 times faster than WinTV). I have not changed any other option except those two.

It seems that DiSEq commands are the only ones that work correctly. I tried also Tone Burst for communicating with the multiswitch and it didn't work although the multiswitch supports it. The multiswitch doesn't have any issues as WinTV and all stand-alone receivers have no problem.

I'm using a TBS6925 now, and I see this 6.85.5 version is very bugged, when using diseqc devices.
I see that Progdvb is not sending correct messages to diseqc 1.0 devices, for example.
It is very easy to do a diseqc devices tree and see the behaviour.

Just see the Progdvengine. log (with logs enabled in Options), to look the messages sent.

For a diseqc 1.0 switch, one should expect this messages when changing to another satellite/Lnb:

Lnb 1 - E0 10 38 F0

Lnb 2 - E0 10 38 F4

Lnb 3 - E0 10 38 F8

Lnb 4 - E0 10 30 FC, but...

It's a shame Progdvb doesnt do a serious and deffinitive debbuging on the many many issues concerning Diseqc (and tunning, too) .

I checked the Log files and here's what I found based on the settings "TV Sources":

1) DiSEqC 1.0 switch: the log shows no DiSEqC commands on channel switch (different polarisation/band)
2) DiSEqC 1.1 switch: the log shows comands E0 10 39 Fx, however my multiswitch requires E0 10 38 Fx commands
3) DiSEqC 1.0 switch & "Send DiSEq commands in every tuner lock" the right E0 10 38 Fx commands are sent on every channel switch

After enabling "Send DiSEq commands in every tuner lock" but now disabling "Lock tuner in every channel changing", all channels work, channel search works too and everything is perfect.

I´will try to make clear what I said above, and permit you test if Progdvb is sending the correct diseqc messages.
1- Supose you have a diseqc 1.0 switch (4 inputs, 1 output).
2 - In input 1, you have a universal ku LNB(1).
3 - In input 2, you have a universal ku LNB(2).
4 - using version 6.85 of Progdvb, or any you like, configure the diseqc tree in device options, and do following tests:

5 - chose a V, low band channel of LNB(1), and see in the logs the sent message:
it should be E0 10 38 F0, according to Eutelsat especifications;

6 - choose a H, low band channel of LNB(1) and see the sent message:
it should be E0 10 38 F2;

7 - choose a V, low band channel of LNB(2), and see message sent:
it should be E0 10 38 F4;

8 - choose a H, low band channel of LNB(2) and see message:
it should be E0 10 38 F6.

The other H/V + low/high combinations you can find on the diseqc specifications.

Is your Progdvb version sending the expected messages as above?

marec wrote:I'm using a TBS6925 now, and I see this 6.85.5 version is very bugged, when using diseqc devices.
I see that Progdvb is not sending correct messages to diseqc 1.0 devices, for example.
It is very easy to do a diseqc devices tree and see the behaviour.

Just see the Progdvengine. log (with logs enabled in Options), to look the messages sent.

For a diseqc 1.0 switch, one should expect this messages when changing to another satellite/Lnb:

Lnb 1 - E0 10 38 F0

Lnb 2 - E0 10 38 F4

Lnb 3 - E0 10 38 F8

Lnb 4 - E0 10 30 FC, but...

It's a shame Progdvb doesnt do a serious and deffinitive debbuging on the many many issues concerning Diseqc (and tunning, too) .

But what bug?

ps: Is it multiswitch request diseqc command for every set channel? May be need addition option for that in ProgDVB interface.

What bug?
INCORRECT DISEQC MESSAGES SENT.
Do some tests with version 6.85.5, as every version can have different issues.
An I dont use multswitchs, only cheap 4 inputs diseqc 1.0 switchs and sometimes cheap 8 input diseqc 1.1 switchs.

Command looks good and no any problem on my PC or on other users.
What command not correct and why?

It seems that Progdvb team is always busy and doesnt have time to do tests .
Maybe somebody else do the tests I proposed above and kindlly report the diseqc messages he got in the logs, to help us? (with version 6.85.5, please).

and so. What problem with log?

Lnb 1 - E0 10 38 F0

Lnb 2 - E0 10 38 F4

Lnb 3 - E0 10 38 F8

Lnb 4 - E0 10 30 FC, but...

Logs are ok. The diseqc messages are wrong.
Dont go by the auto/manual transponders search. They are ok in version 6.85.5.
Go through the Chanell Lists. It doesnt matter the model of the card used.
I hope somebody else try this for us, to end this.