[MPlayer-users] mencoder, x264 and freeze
Alexander Roalter
alex at roalter.it
Sun Nov 15 18:37:14 CET 2009
On 11/12/2009 11:54 PM, Alexander Roalter wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I recently got a new SVN version of mplayer, which needed a fresh git
> pull of x264 (which is now libx264.so.79).
>
> After building mencoder, and running the following line, mencoder runs
> for about 10 minutes or a bit more, then stops and does nothing, CPU
> usage is at 0%, ps ax shows 'Sl+' or 'Sl' as status, nothing else. I
> cannot press Ctrl+C, only killing it (with SIGKILL) will terminate
> mencoder, SIGTERM (and of course SIGINT) does nothing.
>
> I use the following line:
>
> 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
>
>
> (the 2nd pass would look like this, if it ever came to this:)
> 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
>
> Two days earlier, I was able to compress a movie this way (I'm doing it
> exactly this way for now more than two years), but on the end of the 2nd
> pass I got a segmentation error (which now I cannot reproduce since it
> freezes on the first pass).
>
> So my question is, if someone experienced something similar with
> encoding, and/or if my used options are somewhat outdated and therefore
> causing the problem...
>
> On my machine I was usually able to attain a speed of ~230 fps on the
> first pass and ~120fps on the 2nd pass, but now I only get 180fps on the
> first pass...
>
> - --
> Cheers,
> Alex
A follow-up to the problem: I still get the freezes with recent mplayer
and x264.
If I use only one thread (instead of 8), I don't get the freezes, but I
also get only a fraction of the speed: 1st pass 80fps, 2nd pass 40fps :(
--
Cheers,
Alex
More information about the MPlayer-users
mailing list