Page 1 of 1

Some bugs and questions!

Posted: Fri Mar 27, 2009 10:31 pm
by mkleber
Hello folks, I have a new and fresh prof red DVB-S2 7300.
It cames witha a dreamdvb, but progdv should looks better, so I download the trial, so I don´t know if some "bugs" are real bugs or if some kind of limitation that dissapears when you buy a key.

First bug: a permanent vertical stripe "pink" on the right side of the screen, it appears when you watch, when you record or even in PIP.

Second bug: I can´t change the parameters to save the file to .ts, for example, I would like to set it to 320x240 (screen size), maybe a little whorst sound quality and video, because i have to record lots of proggies, so i have no space in hard disk.

Third bug: I lives near an airport, so many times some planes flies near from here and stop the signal... In other receptors the signal comes fasters, but in progdvb the last time it happens take longers thatn 30 secs, so i have to change the channel and came back. Here the real problem is that sometimes im not in Pc, so I leave the Pc recvording and go to work....

So is it all buggies or just limitations? or maybe some configurations trciks?

Thank you, nice software, but i have no idea how to use it perfect

Posted: Sat Mar 28, 2009 1:10 am
by Juergen
1) Not to be solved by that key. Supposingly some weird codec issue.

2) Realtime transcoding requires a really huge CPU, costs a lot of quality but does NOT bring a lot of file size savings. Specially downscaling won't, as the complexity of the signals does not drop that much.
Plus, proper recompression should be done multi-pass, but no way to get at least half that good results on-the-fly...
Forget it, as really large hard disks are quite cheap these days. And professional studio hardware encoders are far better than what we've got in software.

3) There's no way to restore missing signal sequences above some certain degree. Signal outages like that result in permanent losses. Bad luck, nothing to be done about this, except of dropping such damaged GOPs with tools like PVAStrumento.
Differences between DVB applications may come from different tolerance against packets coming in late (or never...). And then, handling of AGC / AFT circuitry may lead to different re-locking timings. For many tuners, some driver features are not documented and can't really get handled the best possible way by 3rd party software. Things get even more complicated, if a DVB application tries to support a huge number of tuner devices.
However, recordings will get damaged anyway.