[mythtv-users] [mpeg2video @ 0x230a264]ac-tex damaged at 3 18 errors in mythbackend.log

[nik gibson]

That looks exactly like my log; and some of my videos do look pretty
crappy.  Sorry if this is dumb question but how did you fix it?  I'm
pulling video over firewire from a 3250 cable box, how do I adjust the
signal level?

Thanks

On 11/28/06, Joe Silver <devils.taco at gmail.com> wrote:
>
>
> On 11/28/06, Tom Lichti <tom at redpepperracing.com> wrote:
> > nik gibson wrote:
> > > I thought I had a working mythtv box and now I see TONS of the
> > > following in the logs.   This is killing me, first firewire, then
> > > xvmc, then xorg crashing, now these errors...  Does anyone know what
> > > they are and what could be causing them?
> > >
> > > Thanks
> > >
> > > stream: start_time: 52385.566 duration: 3586.944 bitrate=3098 kb/s
> > > 2006-11-26 05:00:02.547 AFD: Opened codec 0xa084090, id(MPEG2VIDEO)
> type(Video)
> > > 2006-11-26 05:00:02.560 AFD: Opened codec 0xa150030, id(AC3) type(Audio)
> > > [mpeg2video @ 0x230a264]invalid mb type in P Frame at 24 14
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 5 15
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 18 18
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 19 17
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 3 18
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 8 20
> > > [mpeg2video @ 0x230a264]slice mismatch
> > > [mpeg2video @ 0x230a264]slice mismatch
> > > [mpeg2video @ 0x230a264]slice mismatch
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 5 23
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 18 24
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 3 25
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 12 26
> > > [mpeg2video @ 0x230a264]mb incr damaged
> > > [mpeg2video @ 0x230a264]ac-tex damaged at 6 28
> > > [mpeg2video @ 0x230a264]end mismatch left=1303 5A0D0F
> > >
>
> this looks to me like noisy video.  i had lots of these types of problems in
> my frontend log with my hd3000 card in a newly built backend.  when
> recording or displaying video.  This was due to the signal level being too
> low and causing the digital channel to not lock perfectly.
>
>  watching the video was kind of like looking at the tv through a
> kaleidoscope... real pixelated and crappy.
>
> here's a sample from my log:
> [mpeg2video @ 0x2aaaac523050]ac-tex damaged at 1 9
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 13 9
> [mpeg2video @ 0x2aaaac523050]invalid mb type in P Frame at 5 10
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 7 11
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 3 12
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 5 13
> [mpeg2video @ 0x2aaaac523050]ac-tex damaged at 5 14
> [mpeg2video @ 0x2aaaac523050]ac-tex damaged at 5 15
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 22 16
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 19 17
> [mpeg2video @ 0x2aaaac523050]ac-tex damaged at 2 18
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 19 19
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 17 20
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 6 21
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 10 22
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 5 23
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 20 24
> [mpeg2video @ 0x2aaaac523050]ac-tex damaged at 7 25
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 14 26
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 2 27
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 4 28
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 5 29
> 2006-11-19 14:13:38.020 NVP: prebuffering pause
> [mpeg2video @ 0x2aaaac523050]skipped MB in I frame at 13 13
> [mpeg2video @ 0x2aaaac523050]00 motion_type at 30 26
> [mpeg2video @ 0x2aaaac523050]mb incr damaged
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
>