Page 1 of 1
ProgDVB 5.13.7 sound problem
Posted: Fri Feb 29, 2008 8:31 pm
by redbull86
hi prog
there is still a sound problem on ProgDVB 5.13.7.
when a channel doesn't have sound i go to settings>options and i click the OK button without making any changes the channel now has sound. but i have to do this each time i switch to the channel(s) which has no sound.
Posted: Mon Apr 07, 2008 7:57 am
by aivanise
Hi,
just o confirm that I have the exact same problem with 5.14.3.
tried several video/audio codecs and all have the same problem: no sound or choppy sound when I switch to the channel untill I go to directshow and click Ok without changing anything.
To me it happens for instance with
19.2E N-TV 12188 MHz H pid 12090 169 73 G
but also with other channels
Posted: Mon Apr 07, 2008 11:20 am
by Juergen
No issues with that station (or any similar) over here.
Neither on my Nexus in HW mode, nor when using the media server (home) on it and the client on my second machine...
Can't find anything special on that station, sorry.
Perhaps try to find a better driver for your sound card.
Posted: Mon Apr 07, 2008 3:01 pm
by redbull86
Juergen wrote:No issues with that station (or any similar) over here.
Neither on my Nexus in HW mode, nor when using the media server (home) on it and the client on my second machine...
Can't find anything special on that station, sorry.
Perhaps try to find a better driver for your sound card.
which video render,
which codec pack,
which audio/video codec do you use
and do you use the default settings of progdvb or do you change some settings that may effect in the right way.
P.S. this problem is caused by some channels not every channel causes this problem.
thos channels do effect other channels witch are not working correct. after i click settings>options and i click the ok button without making any changes the channel now works fine (after i click one of the channels witch are causing this problems for the other channels the same problem occurs again.)
Posted: Mon Apr 07, 2008 5:21 pm
by redbull86
P.S. i think it's not caused by the audio card driver because with the same driver there was no problem on previous version of progdvb like version 5.11xx, 5.12xx.
Posted: Sat Apr 12, 2008 1:14 pm
by Yany
Same problem here. Latest ProgDVB 5.x and 4.x. Last working version without this problem for me is 4.85.3.
No matter codec/renderer combination, no matter audio card used. This problem happens on some channels, on some not.
But only if I have selected "default directsound device". If I choose "default waveout device" - everything is fine.
PC - Q6600, ATI HD3870, 8GB RAM, Audigy 2 Plt. EX, Realtek HD audio (onboard), SS HD2. Filters used - Cyberlink Video (PDVD7 and 8 ), ffdshow, elecard, AC3Filter, ffdshow audio, mainconcept, EVR, VMR9, video renderer. Vista64.
Edit: Sound problem not happening with VMR-7 renderer in v.5.14.03 - but switching channels is so slow!
Posted: Sat May 10, 2008 5:21 am
by NetOverflow
I had the same problem, but I found an easy way to solve it:
Just click "Pause" and a few seconds later "Pause" again and the sound works perfectly.
That's the only way I found. If anyone found a better way to solve this problem, please post it here.

Posted: Sat May 10, 2008 8:18 am
by Juergen
As your audio problems only happen on some stations, everyone of you should try to find something systematic behind it.
Prog needs relevant details to try to fix. If he had yet found any similar on the satellites he can get, he surely would already have reacted. But I suppose he can't watch TV 24/7, to look for things like this to happen.
For example, relevant may be audio mode, language(s), audio data rate and alike. Also important, if the stations, coming from or switching to, are changing any IDs during the day, like known from some German local stations, which use another PCR, Video and Audio ID for their local transmissions in the evening.
I don't claim this or anything similar has to be the cause, but perhaps it could be.
Whatever, best would be, if someone found this on a satellite Prog can get at home in Russia.
In any case, Prog needs enough data, to be able to find a bug trace and change code, without damaging anything else...