I use V 5.15.03 and the PID recorder service to record dvb-t as a ts-file. The recorder won't let me chose to record all pids so I have to decide whether I record the ac3 or the standart pid. But sometimes I don't know if the tv-show will be broadcasted in ac3 or not, so if it's not broadcasted ...
When I try to uninstall a version 4 (below 4.88.x) and install a newer 4 version with a Freecom USB BDA Stick, the new installed 4 crashes immediately at the first start. If I install a version 5 parallel or if a version 5 was previously installed, version 4 works fine. Anyone knows why ...
ProgDVB 5 (5.12.02 and 5.12.06) doesn't find any of the 3 DVB-T channels at 198,5 MHz with a Freecom USB Stick BDA device. I guess, it's because of the xxx,5, cause it shows me to search just "198 MHz" in the channel search dialogue. Version 4 finds it, but unfortunately is very unstable on my ...
I use a Freecom DVB-T stick with progDVB 4.85.3. I record in TS format using the PID Recorder and clean it with PVAstrumeto. Even if Level and Quality here is always at 100 % PVAstrumento keeps to find 1-2 errors per movie and I have a short glitch in sound and a few blocks in the picture ...
Thanks! You made my day! Let me ask you a last question. I use ProgDVB just for recordning, not for viewing. If I record a TS stream via the PID recorder (works fine) do the settings under Settings -> Audio and video options -> DirectShow -> Default graphs have any effect on the recorded stream, or ...
>.pva records only make sense with cards that have mpeg-2 >hardwaredecoder...
Oh, I see, so, even if pva seems to work in v5 it makes no sense cause my card has no hardwaredecoder? Even if ProgDVB doesn't support TS, is that the same issue (just make sense with hardwaredecoder)? I thought, in pva ...
I use a Freecom DVB-T USB Stick as a BDA device (newest drivers) with ProgDVB 4.xx (tried different versions) on an Athlon 64 3200, 1024MB system. Recordings in *.mpeg work, but when I try to record in *.pva, I get glitches in sound and a distored picture. This doesn't happen with ProgDVB 5 ...