Hi there,

I got myself a Hauppauge HVR-4000 card a couple of weeks ago and have been testing a bit with ProgDVB when I can find the time to do it.

With the two latest versions ProgDVB5.12.7Pro.exe and v5.12.9 I can't scan the satellite position 1West (Thor). I can scan, 5East, 13East, 19.2East and 28.2East just fine. It works just fine with v5.12.6...

When I start the scan then ProgDVB (the scanner) just sloooooooowwwwwssss down and just updating the window takes several seconds.

If I scan one transponder at a time it seems like it's working.

Any ideas why?

PS. I only have 2 days left to test the Pro versions. Any way to extend this a bit? I just don't feel like buying a program that's not working, yet!

[quote="Elector"]
I can scan, 5East, 13East, 19.2East and 28.2East just fine.
[/quote]

Ok, just fine might be a bit too positive/optimistic.

I first made a clean install of ProgDVB, set up my card and configged the DiSEqC.

Then I scanned 5E, 13E and then when I tried to scan 19.2E ProgDVB crashed and I had to kill the process because it didn't end/die by itself. When I restarted ProgDVB I could scan 19.2E.

Next I tried 28.2E and ProgDVB just kept crashing the second I started the scan. After several kill/restarts I finally got it to scan 28.2E. Don't know why it kept crashing and now suddenly started scanning, maybe it's a timing issue? The last time I started the scan as soon as I could, and didn't wait for the first channel to decode (some random FTA channel on 5E).

But at least I got all but 1W scanned.

Is it 5.12.9 ? It must stable work with 4000 card. I am test it many...

Do you have crash only in 28 and 19 only or on all satelittes?

I think I've narrowed the crashes down to the Elecard TV channel graph/driver.

It turns out that if ProgDVB starts and it get so far that I can see the video/image, then it will crash if I change to another channel or if I chose "Close video window".

When I changed the TV Channel graph to ffdshow then it works just fine, well except the audio starting to stutter after a few seconds and then completely disappearing but that's probably just related to the elecard audio driver, I'll have to look into that later.


But my problem with scanning 1W still remains. I have had it try to scan for 15-20 minutes, still stuck at 00:00 elapsed and remaining and nothing scanned.

[quote="Elector"]But my problem with scanning 1W still remains. I have had it try to scan for 15-20 minutes, still stuck at 00:00 elapsed and remaining and nothing scanned.[/quote]


Still got that problem. But I got it narrowed down now.

It looks like the scan stalls on L/R polarization.

I tried making a transponder ini-file with the following entries (plus the other standard stuff but no need to type those here)

[DVB]
0=1
1=4180,L,21050,34;ERTU

it stalls right away and wont scan at all.

If I make a ini with

[DVB]
0=5
1=10987,V,5632,34
2=11006,V,6111,34
3=11093,H,19191,78
4=11094,V,5632,34
5=4180,L,21050,34;ERTU

It scans 1-4 just fine, but when it get to 5 it stalls.

and with

[DVB]
0=4
1=10987,V,5632,34
2=11006,V,6111,34
3=11093,H,19191,78
4=11094,V,5632,34

It all works just fine. Well, it doesn't find any channels because there are none on those transponders/SR/fec, but it does try to scan the transponders.


This has been tested with v5.12.10Std since the Pro version doesn't work anymore (trial period is up ).