[XviD-devel] B-frames encoding code committed

[Dirk Knop]

Hi,

Edouard Gomez wrote:

>Same error  here, i've  run the encoder  in a  gdb session and  it has
>located the function.
>
>*Program received signal SIGSEGV, Segmentation fault.
>*0x43fa57ce in sad16bi_xmm () from /usr/local/lib/libxvidcore.so
>
>I looked at the function and the  asm code matches the one you gave in
>your report (file src/motion/x86_asm/sad_xmm.asm).
>
>I'm  currently  doing a  finer  debugging  looking  for the  erroneous
>pointer passed to sadbi_xmm.
>  
>
Another observation:

Seems to be related to colour space somehow.
Some user over at doom9 pointed out that this doesn't happen with avi 
for him, just when he uses avisynth files (avi's usually get 
postprocessing in vdub [if e.g. captured from tv], while avisynth files 
usually are in YUV colour space and get a "fast recompression").
I captured 2950 frames from TV and did the clip with postprocessing 
activated (thus vdub sends RGB data to the codec) - no crash occured(!). 
When using this without postprocessing and letting vdub send YUV data 
(hm... i use YUV2 with 4/1/1 subsampling, maybe that's another problem) 
vdub just crashed without any trails again.

Maybe this helps to pinpoint the problem.

Regards,
Dirk