Michael Niedermayer <[EMAIL PROTECTED]> added the comment: On Sat, Sep 13, 2008 at 04:01:51PM +0000, Ramiro Polla wrote: > > Ramiro Polla <[EMAIL PROTECTED]> added the comment: > > I tried with a bunch of combinations resulting up to: > ./configure --disable-mmx --disable-optimizations --enable-gpl > --enable-swscale > --enable-pthreads > > with ffmpeg options up to: > ./ffmpeg_g -y -f image2 -vcodec pgmyuv -i tests/vsynth1/%02d.pgm -an -vcodec > mpeg4 -me_method zero -mbcmp zero -intra -subcmp zero -cmp zero -precmp zero > -skipcmp zero -ildctcmp zero -flags +qscale -threads 2 > ./tests/data/a-mpeg4-thread.avi > > (I edited utils.c to allow -flags +qscale again for video encoding)
uhm there is no -flags +qscale > > This still makes it fail randomly. I don't know how to set "no ratecontrol". its -qscale 2 > > Seeing that the revision that triggers the bug has been found, isn't it easier > to analyze that diff to see what it did wrong? (I wasn't able to do that > since I > don't know much about mpegvideo's internals and all the threading code) Well, first the error does not always occur (here its rather rarely occuring with svn head ... thus its disapearance in a revission may, but does not have to mean the revission is at fault. If you think its the revission, then maybe you could cut that diff down a little to determine which part of it exactly affects it. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Let us carefully observe those good qualities wherein our enemies excel us and endeavor to excel them, by avoiding what is faulty, and imitating what is excellent in them. -- Plutarch ______________________________________________________ FFmpeg issue tracker <[EMAIL PROTECTED]> <https://roundup.mplayerhq.hu/roundup/ffmpeg/issue517> ______________________________________________________
