Hello all. I have the all-in-one FlyDVB Trio PCI card and I am using the ProgDVB v5.10 standard. The card works properly with analog and DVB-T TV with LifeView's DTV software. But of course I want to use ProgDVB for DVB-T and DVB-S. My problem is that I can't see picture (only black and no sound) with ProgDVB! Strangely the CPU usage of my AthlonXP 2600+ is >40% but the screen remains black (the channels are found normally after a scan). I understood that maybe there is a display problem, so I decided to try a capture. Indeed, the .mpg file plays normally, so the program receives correctly the channel's signal, but for an unknown reason, it can't display it.

I thought that maybe my old VGA was the problem, a GeForce2 MX-400 (64 MB). It has the recent drivers 93.71 and AGP 4x is enabled. Honestly, I don't believe that this is the source of the problem, because i) I have used an even older card (MX-200) with ProgDVB/SkyStar HD and no problem, ii) the LifeView DTV software can display DVB-T channels flawlessly. So the card has the abilities to display the signal.

I have selected from the ProgDVB's device list the device "BDA 713x BDA DVBT Tuner". I have tried with every available renderer, but always the same result: black screen while CPU is around 40% (and no sound also). Generally, I am using .xgr files and of course the excellent ffdshow, but the strange is that when I am switching on a channel, I don't see even the haali splitter icon in the system tray!

I think that the program can't even "forward" the signal to the splitter, but why? As I said, I have some experience with ProgDVB in another system with SkyStar HD, but here I don't understand anything. Do I use the wrong device maybe? If yes, which I should choose? Is it a VGA problem? If yes, why I could with an MX-200 and additionally why the sound is also absent? Is it a filters issue? Please help me if you can. Thanks.

As you also don't have sound, this must be codec / graph related, or a general DirectShow problem.

However, you should try to make a custom graph for your system.

Hello Juergen and thank you for your answer.

As you also don't have sound, this must be codec / graph related, or a general DirectShow problem. However, you should try to make a custom graph for your system.

I have all the necessary codecs installed (ffdshow) and an mpeg-2 file creates a full graph in GraphEdit. Also my DirectShow system seems to works normally. Anyway, I always take care not to install many codecs in my system and I have also tried to use an xgr file. The same xgr file works now with ProgDVB v4.85 (read below).

I have made some more tests and I got the feeling that my card works excellent with ProgDVB v4.85.3. I believe that maybe there is something wrong with engine 2.0.

I have another OS installed in my system with almost no programs installed. I read somewhere that there are some problems when Nero 7 is present, so I decided to give it a try. Also, I selected the ProgDVB 4.x version to see if has something to give me. Indeed, in that second WinXP system, I saw that the card was playing flawlessly! That time I selected during the installation "BDA compatible..." and not "LifeView FlyDVB" as the device. Also I selected the option "Install MPEG-2 decoder".

I immediately returned to my main OS and decided to uninstall and re-install the ProgDVB v5.10, following the same steps. Unfortunately, the card continued to not work. I thought to install at the same time (but in another folder) the ProgDVB v4.85. Indeed, the card is co-operating correctly with any renderer and can display the channels with ease (using Elecard or ffdshow). Now I use an xgr file, but I don't understand why the included (in filter graph) haali splitter is not used...

Conclusions:
1. The ProgDVB v4.85 with engine 1.x seems to be more compatible. I will try tomorrow the version 4.86 with engine 2.x to see if it causes any problems.
2. Are there any incompatibilities with ProgDVB v5.x and Nero 7, due to filters conflicts?
3. Do I have any major reasons to insist on ProgDVB v5.x?

harriscs wrote: 1. The ProgDVB v4.85 with engine 1.x seems to be more compatible. I will try tomorrow the version 4.86 with engine 2.x to see if it causes any problems.

Good idea.

2. Are there any incompatibilities with ProgDVB v5.x and Nero 7, due to filters conflicts?

Not generrally, I suppose, as it's not likely to really be a rare combination. But Nero also comes with codecs, even depending on it's configuration, and some codec incompatibilities are possible.

3. Do I have any major reasons to insist on ProgDVB v5.x?

Not yet, as you don't have to insist on test versions, at all.
They are supposed to be extra buggy and some of them even incomplete.
Work in progress

Hello all. I came to the conclusion that only the engine 1.x is compatible with my card. I had exactly the same behaviour with v4.86 as with v5.10, ie high CPU usage and no audio/video preview. Obviously, the card is incompatible with versions of ProgDVB which are based on engine 2.x. I hope that someone can verify it.

Personally, I believe that the problem is mainly in the LifeView's BDA driver, because I am also having problems with other functions (eg analog TV has problems with VirtualDub, analog recording is also problematic with all programs, even with DTV). It's old driver (08/2005) and needs to be updated, but the card works normally with the "LifeView DTV" software. I have sent a relative e-mail to the LifeView's support.

Now I am using two instances of the same ProgDVB version (4.85), installed in different folders, where at the first interface I have enabled the DVB-T interface of the card, while at the second I have enabled the DVB-S interface. It's the only reliable solution I have found.

If someone has the same card, it would be great to share his knowledge with us. Thanks!