Does anyone know what these errors in the mythbackend.log mean when I'm
doing commflagging of HD recordings from my Avermedia A180 HD card from QAM

[mpeg2video @ 0x2ae584]invalid mb type in P Frame at 3 59
[mpeg2video @ 0x2ae584]00 motion_type at 1 60
[mpeg2video @ 0x2ae584]ac-tex damaged at 18 61
[mpeg2video @ 0x2ae584]00 motion_type at 1 62
[mpeg2video @ 0x2ae584]00 motion_type at 7 63
[mpeg2video @ 0x2ae584]00 motion_type at 11 64
[mpeg2video @ 0x2ae584]00 motion_type at 11 65
[mpeg2video @ 0x2ae584]00 motion_type at 1 66
[mpeg2video @ 0x2ae584]00 motion_type at 24 67
[mpeg2video @ 0x2ae584]ac-tex damaged at 13 54
[mpeg2video @ 0x2ae584]invalid mb type in P Frame at 16 55
[mpeg2video @ 0x2ae584]00 motion_type at 8 56
[mpeg2video @ 0x2ae584]00 motion_type at 1 57
[mpeg2video @ 0x2ae584]invalid mb type in P Frame at 2 58
[mpeg2video @ 0x2ae584]00 motion_type at 1 59
[mpeg2video @ 0x2ae584]00 motion_type at 5 60
[mpeg2video @ 0x2ae584]00 motion_type at 12 61
[mpeg2video @ 0x2ae584]ac-tex damaged at 5 62
[mpeg2video @ 0x2ae584]invalid mb type in P Frame at 8 63
[mpeg2video @ 0x2ae584]ac-tex damaged at 0 64
[mpeg2video @ 0x2ae584]00 motion_type at 7 65
[mpeg2video @ 0x2ae584]00 motion_type at 21 66
[mpeg2video @ 0x2ae584]00 motion_type at 2 67
[mpeg2video @ 0x2ae584]ac-tex damaged at 0 64
[mpeg2video @ 0x2ae584]ac-tex damaged at 0 65
[mpeg2video @ 0x2ae584]ac-tex damaged at 0 66
[mpeg2video @ 0x2ae584]ac-tex damaged at 0 67

It seems that they indicate problems in the file but the playback is
fine without issues.  I'm wondering if there is something to do to
suppress these if they are trivial or fix the source if they are not.

Kevin
_______________________________________________
mythtv-users mailing list
mythtv-users@myth...
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users