Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: DVB Newbie



Hi all,

I was just wondering how things were progressing on this problem..

Ive just reinstalled my machine after moving house and with the latest cvs
snapshots of the linux-tv driver, dvbtune, dvbstream and libdvb I cannot
get dvbstream to work using my old script. From the first frame rendered
by mplayer (which has not been upgraded, it runs on a laptop) the image is
corrupt with squeeking audio. Very different to my last experience at my
old address about 3 months ago.

Anyway, I have tried using tzap to tune and cat dvr0 to get the ts stream
out and it does indeed work much better.. however, and this has been the
problem more or less from day one when I get my Nova-t last year, the
longer I leave the card running the greater the number of errors that will
occur until (after about 5 minutes) mplayer will die

Running dvbtune -m occasionally shows blockerrors of +1 for the first line
when starting, but other than that its constant at zero..:

Signal=11051, Verror=491, SNR=53199dB, BlockErrors=0, (S|L|C|V|SY|)
Signal=11051, Verror=494, SNR=53713dB, BlockErrors=0, (S|L|C|V|SY|)

As I copied those lines, mplayer was flickering and "squeeking" quite
impressively! Ive seen errors caused in the stream when BlockErrors is not
zero, but now its constantly zero yet these errors become more and more
frequant as the minutes pass..

I seem to be in the same boat and was wondering.. ah mplayer just died..

@@@ libmpeg2 returned from sig11... (bad file?) @@@
A:18448.2 V:18448.2 A-V:  0.051 ct: -0.023  4127/4127  13% 15%  6.4% 0 0 0%
Broken frame at 0x3CCF30
A:18448.5 V:18449.1 A-V: -0.596 ct: -0.052  4151/4151  13% 15%  6.4% 0 0 0%
Successfully enabled DPMS

.. was wondering if anyone had any idea why the card seems to gain
errors.. If it was a signal strenth problem surely it would be from the
moment mplayer started.. not good for 3 or 4 minutes, bad for another 2
then fatal 2 or 3 after that?  Is this something to do with the tuner?
possibly wondering off "lock"?

Here's the first few lines from when tzap is started
# ./tzap -r CHANNEL4
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
tuning to 481833333 Hz
status 0d | signal 2b2b | snr d2d2 | ber 0000ffff | unc 0000000b |
status 1f | signal 2b2b | snr d0d0 | ber 000001f7 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 2b2b | snr cece | ber 000001f4 | unc 00000000 | FE_HAS_LOCK
status 1f | signal 2b2b | snr d1d1 | ber 000001f1 | unc 00000000 | FE_HAS_LOCK


I was wondering if there was something I could tweak or look at. Could it
be faulty hardware? i'm using a standard Nova-t and really haven't had
sustaineed luck with it. It works for periods then these errors creep in..

Any help would be greatly appreciated

Cheers

cp

On 8 Jun 2003, --[ UxBoD ]-- wrote:

> > Okay getting a little better now - but I have noticed that when mplayer bails on me
> > this is what is showing :
> >
> > @@@ libmpeg2 returned from sig11... (bad file?) @@@40  10%  5%  0.8% 0 0 9%%
> >
> > Any idea what causes this? would a dedicated MPEG card help this?
>
> > --
> >
> > // --[ UxBoD ]-- // 2.4.20-gentoo-r5 // Pentium(R) 4 CPU 2.53GHz //
> > // gpg --keyserver wwwkeys.pgp.net --recv-keys 56ED1CB5 //
> >
>




-- 
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe linux-dvb" as subject.



Home | Main Index | Thread Index