[MEncoder-users] Issues with FFmpeg mpeg4, B-frames and multithreaded encoding

[mesecam]

Hi everyone,

I've got the same issue over and over using FFmpeg mpeg4.

When trying to encode a regular file using threads option > 1,
bframes, the output file keeps crashing `mplayer' when using the xvid
decoder.
I've tried to play the file in WMP (WinXP) with the xvid decoder, this
time it won't crash but the video is dirty/choppy

$>mplayer -vfm xvid temp.avi

mplayer -vfm xvid temp.avi
MPlayer dev-SVN-r27620-4.2.4 (C) 2000-2008 MPlayer Team
CPU: Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz (Family: 6,
Model: 15, Stepping: 11)
CPUflags:  MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled for x86 CPU with extensions: MMX MMX2 SSE SSE2

Playing temp.avi.
AVI file format detected.
[aviheader] Video stream found, -vid 0
AVI: No audio stream found -> no sound.
Could not determine number of frames (for absolute seek).
VIDEO:  [XVID]  688x384  24bpp  23.976 fps  -17179870.0 kbps
(-2097152.0 kbyte/s)
Clip info:
 Software: MEncoder dev-SVN-r27620-4.2.4
dvdsublang...temp en eng
==========================================================================
Trying to force video codec driver family xvid...
Opening video decoder: [xvid] XviD 1.0 decoder
xvid: using library version 1.1.3 (build xvid-1.1.3)
Selected video codec: [xvid] vfm: xvid (Xvid (MPEG-4))
==========================================================================
Audio: no sound
Starting playback...
VDec: vo config request - 688 x 384 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.78:1 - prescaling to correct movie aspect.
VO: [xv] 688x384 => 688x386 Planar YV12
V:   0.6  14/ 14 30%  2%  0.0% 0 0

MPlayer interrupted by signal 11 in module: decode_video
- MPlayer crashed by bad usage of CPU/FPU/RAM.
  Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
  disassembly. Details in DOCS/HTML/en/bugreports_what.html#bugreports_crash.
- MPlayer crashed. This shouldn't happen.
  It can be a bug in the MPlayer code _or_ in your drivers _or_ in your
  gcc version. If you think it's MPlayer's fault, please read
  DOCS/HTML/en/bugreports.html and follow the instructions there. We can't and
  won't help unless you provide this information when reporting a possible bug.

If it is of any help

Regards
--
Mesecam