<br><div><span class="gmail_quote">On 11/28/06, <b class="gmail_sendername">Tom Lichti</b> <<a href="mailto:tom@redpepperracing.com">tom@redpepperracing.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
nik gibson wrote:<br>> I thought I had a working mythtv box and now I see TONS of the<br>> following in the logs. This is killing me, first firewire, then<br>> xvmc, then xorg crashing, now these errors... Does anyone know what
<br>> they are and what could be causing them?<br>><br>> Thanks<br>><br>> stream: start_time: 52385.566 duration: 3586.944 bitrate=3098 kb/s<br>> 2006-11-26 05:00:02.547 AFD: Opened codec 0xa084090, id(MPEG2VIDEO) type(Video)
<br>> 2006-11-26 05:00:02.560 AFD: Opened codec 0xa150030, id(AC3) type(Audio)<br>> [mpeg2video @ 0x230a264]invalid mb type in P Frame at 24 14<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 5 15<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 18 18
<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 19 17<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 3 18<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 8 20<br>> [mpeg2video @ 0x230a264]slice mismatch<br>> [mpeg2video @ 0x230a264]slice mismatch
<br>> [mpeg2video @ 0x230a264]slice mismatch<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 5 23<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 18 24<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 3 25<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 12 26
<br>> [mpeg2video @ 0x230a264]mb incr damaged<br>> [mpeg2video @ 0x230a264]ac-tex damaged at 6 28<br>> [mpeg2video @ 0x230a264]end mismatch left=1303 5A0D0F<br>></blockquote><div><br>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. <br>
<br>
watching the video was kind of like looking at the tv through a kaleidoscope... real pixelated and crappy. <br><br>here's a sample from my log:<br>[mpeg2video @ 0x2aaaac523050]ac-tex damaged at 1 9<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 13 9
<br>[mpeg2video @ 0x2aaaac523050]invalid mb type in P Frame at 5 10<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 7 11<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 3 12<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 5 13
<br>[mpeg2video @ 0x2aaaac523050]ac-tex damaged at 5 14<br>[mpeg2video @ 0x2aaaac523050]ac-tex damaged at 5 15<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 22 16<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 19 17
<br>[mpeg2video @ 0x2aaaac523050]ac-tex damaged at 2 18<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 19 19<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 17 20<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 6 21
<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 10 22<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 5 23<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 20 24<br>[mpeg2video @ 0x2aaaac523050]ac-tex damaged at 7 25
<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 14 26<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 2 27<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 4 28<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 5 29
<br>2006-11-19 14:13:38.020 NVP: prebuffering pause<br>[mpeg2video @ 0x2aaaac523050]skipped MB in I frame at 13 13<br>[mpeg2video @ 0x2aaaac523050]00 motion_type at 30 26<br>[mpeg2video @ 0x2aaaac523050]mb incr damaged<br>
<br>
</div><br></div>