On Sunday 27 August 2006 18:45, Chris Schanzle wrote:
> On 08/27/2006 02:00 AM, Chris Schanzle wrote:
> > On 08/26/2006 11:23 PM, Chris Schanzle wrote:
> > I have not played back the recordings to verify their integrity.
> > However, when commercial flagging started for the second recording,
> > there were many MPEG2VIDEO error messages in the mythbackend log,
> > which likely means the recording is corrupt:
> >
> > [mpeg2video @ 0x64eca04]ac-tex damaged at 37 22
> > [mpeg2video @ 0x64eca04]Warning MVs not available
> > [mpeg2video @ 0x64eca04]ac-tex damaged at 37 22
> > [mpeg2video @ 0x64eca04]ac-tex damaged at 37 22
> > [mpeg2video @ 0x64eca04]skipped MB in I frame at 7 16
> > [mpeg2video @ 0x64eca04]Warning MVs not available
> > [mpeg2video @ 0x64eca04]ac-tex damaged at 6 5
> > [mpeg2video @ 0x64eca04]ac-tex damaged at 0 0
> > [mpeg2video @ 0x64eca04]mb incr damaged
> > [mpeg2video @ 0x64eca04]invalid cbp at 24 29
> > [mpeg2video @ 0x64eca04]ac-tex damaged at 37 22
> > ....
> > [few dozen similar lines omitted]
> >
> >
> > It would seem if the system is very idle, there are no problems.
> >
> > Below are /var/log/messages and mythbackend messages intermingled:
> >
> > 2006-08-27 01:04:34.045 scheduler: Started recording
> > Aug 27 01:04:42 localhost kernel: ivtv0 warning: DMA err b
> > Aug 27 01:04:42 localhost kernel: ivtv0 warning: ENC: (0) DMA Error
> > 0x0000000b 00020000
> > Aug 27 01:04:42 localhost kernel: ivtv0 warning: offset 0 -> 128
> > Aug 27 01:04:42 localhost kernel: ivtv0 warning: offset 128 -> 0
>
> I confirmed there were errors in the video at this point (~7sec into
> the recording).
>
> Hans, should any corruption still exist with the above messages?
I have seen cases of short-term corruption (for a few frames) but it
should recover. As long as you don't see these messages everything
remains OK, correct? Only afterwards do you have audio issues?
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
