Page 1 of 1

Problem with ffdshow audio in radio stations.

Posted: Fri Sep 14, 2007 4:44 pm
by harriscs
Hello all. I use ProgDVB v4.85.3 with my LifeView FlyDVB Trio PCI card and I have every DirectShow option set in the first empty field of the drop-down list. As I understood, this option means that the program will obey to the DirectShow system priorities. I have enabled the ffdshow MP1, MP2 audio decoder (along with many others) and when I am switching on a radio station, I see that the blue ffdshow's icon loads in the system tray, the recording is normal but the sound is absent during preview! I don't understand why... I tried both with mp3lib and libmad.

I am using ffdshow tryouts rev1471 (09/09/2007) and the strange is that the audio part is excellent in the TV channels. I think that most TV channels are using the same audio format with radio stations, "MPEG-1 Audio layer 2". What is happening? Thanks.

PS: If I disable ffdshow decoder, then the filter "MPEG Audio decoder" comes to power and the sound of the radio stations is normal. But I prefer ffdshow, because of the support in the Winamp DSP plugins which greatly improve the audio quality.

Posted: Sun Sep 16, 2007 11:28 pm
by Juergen
Perhaps ffdshow can't handle radio (audio without video along). Others have already reported similar.
However, you can set another codec for radio only.

In fact, the DVB audio standard is the same for radio and TV.

Posted: Fri Sep 21, 2007 10:17 am
by harriscs
Hi again. The only solution I found is to create a filter graph with both "MPEG Audio decoder" and ffdshow, where the last format "uncompressed" is enabled ("all supported"). That way the audio is actually decoded by the MPEG Audio filter and then comes through ffdshow just for using the Winamp DSP plugin (Enhancer). So now I have both normal preview sound and DSP effects.

Generally, I like the simplest solution with minimum filters, but in that case I don't have a choice. I hope that the great ffdshow will fix this strange bug with radio stations in the future versions. It seems that the problem is in the filter itself. Thanks.