Loren Merritt wrote: > On Tue, 17 Nov 2009, Alexander Roalter wrote: >> when looking for something similar, I get the following thread: >> http://mailman.videolan.org/pipermail/x264-devel/2009-September/006338.html >> In which for multi-threaded encoding >> param.i_sync_lookahead = 0; >> is suggested... Apparently, mencoder should do the same. (?) > > param.i_sync_lookahead = 0 was suggested as a way to reduce latency, not > to fix anything. > >> Pos:8332.8s 199800f (99%) 68.03fps Trem: 0min 634mb A-V:0.018 [513:119] >> x264 [error]: Incomplete MB-tree stats file.0min 634mb A-V:0.013 [511:120] >> x264_encoder_encode failed > > Are you using any mencoder options that could cause different numbers of > frames in each pass? hm, I don't know if that is the case, the command line is the following: mencoder infile -o outfile -oac mp3lame -lameopts abr=128 -ovc x264 -x264encopts bitrate=512:pass=1:turbo=1:threads=8 -vf $scale -srate 44100 -ofps 24 and mencoder infile -o outfile -oac mp3lame -lameopts abr=128 -ovc x264 -x264encopts bitrate=512:subq=6:partitions=all:8x8dct:me=umh:frameref=5:pass=2:threads=8 -vf $scale -srate 44100 -ofps 24 I see that the forcing of 24 fps causes frames to be dropped, but in theory this should be equal on both the first and the 2nd pass. > >> Oh, and BTW, I used to reach 120fps on the 2nd pass with identical >> settings, now I only reach 70... > > Identical commandline, or identical x264 settings? > see above -- cheers, Alex
