New ATSC messages.

I believe these are new messages when view ATSC channels.  I
have been
receiving the "a52" errors for some time, but the
mpeg2video messages
are new.  I have tried to compile with --enable-profile (and
hand
compiled the snow and h264 (without -p) in the libavcodecs
due to
register pressure).

Are the streams interesting to anyone?

I have changed the azap code to open in RDONLY mode and
according to
the output, the ber is zero and the channels are locked.  It
appears
my CPU is a bottle neck, but the top display never shows
full cpu
usage.

Thanks,
Bill Pringlemeir.

[mpeg2video  0x876edd0]invalid mb type in B Frame at 68 48
[mpeg2video  0x876edd0]Warning MVs not available
[mpeg2video  0x876edd0]concealing 120 DC, 120 AC, 120 MV errors
[mpeg2video  0x876edd0]00 motion_type at 66 45
[mpeg2video  0x876edd0]concealing 120 DC, 120 AC, 120 MV errors
a52: CRC check failed!  
[mpeg2video  0x876edd0]concealing 120 DC, 120 AC, 120 MV errors
a52: CRC check failed!  
a52: error at resampling
a52: CRC check failed!  
a52: error at resampling


           ************************************************
           **** Your system is too SLOW to play this!  ****
           ************************************************

[mpeg2video  0x876edd0]00 motion_type at 75 10
[mpeg2video  0x876edd0]invalid mb type in P Frame at 2 8
[mpeg2video  0x876edd0]invalid mb type in P Frame at 1 9
[mpeg2video  0x876edd0]00 motion_type at 5 10
[mpeg2video  0x876edd0]00 motion_type at 3 11
[mpeg2video  0x876edd0]mb incr damaged
[mpeg2video  0x876edd0]00 motion_type at 51 13
[mpeg2video  0x876edd0]mb incr damaged
[mpeg2video  0x876edd0]00 motion_type at 6 15
[mpeg2video  0x876edd0]mb incr damaged
[mpeg2video  0x876edd0]00 motion_type at 69 17
[mpeg2video  0x876edd0]mb incr damaged
[mpeg2video  0x876edd0]00 motion_type at 44 19
[mpeg2video  0x876edd0]mb incr damaged
[mpeg2video  0x876edd0]00 motion_type at 76 21
[mpeg2video  0x876edd0]00 motion_type at 17 22
[mpeg2video  0x876edd0]00 motion_type at 10 23
[mpeg2video  0x876edd0]mb incr damaged
[mpeg2video  0x876edd0]00 motion_type at 15 25
[mpeg2video  0x876edd0]mb incr damaged
[mpeg2video  0x876edd0]00 motion_type at 3 27
[mpeg2video  0x876edd0]00 motion_type at 10 28
[mpeg2video  0x876edd0]00 motion_type at 7 29
[mpeg2video  0x876edd0]00 motion_type at 7 30
[mpeg2video  0x876edd0]invalid mb type in P Frame at 21 31
[mpeg2video  0x876edd0]00 motion_type at 10 32

_______________________________________________
MPlayer-dvb mailing list
MPlayer-dvbmplayerhq.hu
http://lists.mplayerhq.hu/mailman/listinfo/mplayer-dvb

Il Sunday 09 December 2007 04:24:30 Bill Pringlemeir ha
scritto:
> I believe these are new messages when view ATSC
channels.  I have
> been receiving the "a52" errors for some
time, but the mpeg2video
> messages are new.  I have tried to compile with
--enable-profile
> (and hand compiled the snow and h264 (without -p) in
the
> libavcodecs due to register pressure).
>
> Are the streams interesting to anyone?

yes, post them to incoming/ please

>
> I have changed the azap code to open in RDONLY mode and
according
> to the output, the ber is zero and the channels are
locked.  It
> appears my CPU is a bottle neck, but the top display
never shows
> full cpu usage.
>
> Thanks,
> Bill Pringlemeir.
>

I suspect simply bad reception
_______________________________________________
MPlayer-dvb mailing list
MPlayer-dvbmplayerhq.hu
http://lists.mplayerhq.hu/mailman/listinfo/mplayer-dvb