My patch is only useful when trying to tune a transponder using some
of the XXX_AUTO settings. For instance FEC_AUTO instead of FEC_2_3.
In this case dib3000mc is clever enough to figure out which FEC_ to
use to get a correct tuning.
IMHO, in your case, I'm afraid but it should make no difference.
On 11/23/06, José Oliver Segura <primijos@xxxxxxxxx> wrote:
Hi Mario,
I'd like to ask you a question regarding the dib3000mc patch: I
have almost no idea of dvb (thus, SEQ, ***_AUTO, etc, sounds strange
to me :)) , but I have a WinTV nova-t stick, that works OK under
windows and has some problems (lots of "ber" and some "unc" with a
signal of about 7000/8000) under linux (and it uses dib300mc module),
and I was wondering if the modifcations you are proposing with your
patch could help (I mean: does it improve signal reception in someway?
[I'm assuming ber/unc are due to signal reception, which maybe is too
much assumption?])
The behaviour of the stick with linux is very strange (sadly:
windows works perfect with hauppaugge drivers). Under Linux, I've
found that for these channels for what I get a high number of ber/unc
(thus: impossible to watch tv), if I tune (tzap) to another specific
channel (a channel that has a signal between a000-a200, ber=0, unc=0),
and then I try to zap back to the channel with high ber/unc, these
values are 0 (or almost) so, I can watch that channel... but... after
some time (minutes?), the numbers start to get higher, and back again
to "unwatchable" TV :)
As I told, I have no idea about what _guard, seq, etc. mean,
sorry if this question is completely silly
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
