On Fri, May 13, 2011 at 03:47:47PM +0530, Aditya Game Programmer wrote: > [mpeg @ 19140050] max_analyze_duration reached //-- what causes > this and how do i prevent this?
does plain ffmpeg also produce this warning ? and you can tune the max_analyze_duration parameter in AVFormatContext > > Input #0, mpeg, from 'tv5.mpg': > Duration: 00:02:58.72, start: 0.500000, bitrate: 4162 kb/s > Stream #0.0[0x1c0]: Audio: mp2, 48000 Hz, stereo, s16, 64 kb/s > Stream #0.1[0x1e0]: Video: mpeg2video (Main), yuv420p, 720x576 [PAR 16:15 > DA > R 4:3], 15000 kb/s, 25 fps, 25 tbr, 90k tbn, 50 tbc > Output #0, avi, to 'output.avi': > Stream #0.0: Audio: mp2, 48000 Hz, 2 channels, 64 kb/s > Stream #0.1: Video: mpeg4, yuv420p, 720x576 [PAR 16:15 DAR 4:3], q=2-31, > 150 > 00 kb/s, 90k tbn, 50 tbc > > [mpeg2video @ 1915FE30] ac-tex damaged at 33 22 //--what is ac-tex? its AC coefficient errors in texture that is 8x8 dct coding. if your stream is not damaged or truncated theres something wrong with what is input to the decoder > how to prevent damage or correct the damaged ac-tex ? > prevent its damage > [mpeg2video @ 1915FE30] Warning MVs not available //-- what are mv's ? Motion Vectors > [mpeg2video @ 1915FE30] concealing 90 DC, 90 AC, 90 MV errors //-- > what exactly is happening here ? As above, its some problem with the data that is feed to avcodec_decode_video*() [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB No great genius has ever existed without some touch of madness. -- Aristotle
signature.asc
Description: Digital signature
_______________________________________________ libav-api mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-api
