<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><BR><DIV><DIV>On 13 Feb 2007, at 05:03, John Welch wrote:</DIV><BLOCKQUOTE type="cite"><DIV><DIV><SPAN class="Apple-style-span"><FONT class="Apple-style-span" color="#000000">... </FONT></SPAN></DIV></DIV></BLOCKQUOTE><BLOCKQUOTE type="cite"><DIV><DIV><SPAN class="Apple-style-span">The funny thing is when the recording is going bad I don't see anything special in the logs, but when the commercial flagging processing the recording I get literally thousands and thousands of messages in the log. Here's just a real small sample: <BR>[mpeg2video @ 0x4dc9c4]invalid cbp at 73 10<BR>[mpeg2video @ 0x4dc9c4]Warning MVs not available<BR>[mpeg2video @ 0x4dc9c4]ac-tex damaged at 38 56<BR>[mpeg2video @ 0x4dc9c4]Warning MVs not available<BR>[mpeg2video @ 0x4dc9c4]current_picture not initalized <BR>2007-02-12 18:33:36.669 AFD Error: Unknown decoding error<BR>[mpeg2video @ 0x4dc9c4]current_picture not initalized<BR>2007-02-12 18:33:37.520 AFD Error: Unknown decoding error<BR>[mpeg2video @ 0x4dc9c4]mb incr damaged <BR>[mpeg2video @ 0x4dc9c4]Warning MVs not available<BR></SPAN></DIV></DIV></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV>This is because you've recorded the jitter & corruption, so the commercial flagging processing is seeing it the same way your eyes do.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Stroller.</DIV><DIV><BR><BR></DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR></BODY></HTML>