Re: [libdv-dev] Re: libdv for AMD64

[<da...@de...>]

>  I kinda lost you here. Why --disable-asm is important ? It's known to
>  be way slower anyway.

heh, because the latest libdv _release_ will not run with mmx/asm forcibly
enabled on x86-64. The point of Dean's effort was to just to get the
asm/mmx working again.
>> current libdv release. I told him that asm/mmx was disabled due to
>> arch detection at configure. I asked him to try CVS, he did, and
>> reported a huge performance gain, of course.
>
>  Hm. I went and checked and I saw the following .o's under .lib/:
>
>    dct_block_mmx_x86_64.o
[...]
>  so it would seem that x86_64 support gets used.

Yes, on CVS now that does happen, but I was referring to the current
_release_. 64bit users will be at least somewhat content because they will
not have to suffer with no accelleration!
>  Interesting. Of course ffmpeg's stable release is long overdue, but
>  CVS should be quite stable as far as DV is concerned. Are you sure


>  that it failed in DV decoding, not when user tried to export stuff
>  into mpeg4 or something.

avcodec_decode_video (or similar) is at the top of the callstack just
before the calls into the segv handler. Of course, I can't reproduce it.
Also, unfortunately, there are no args on the backtrace. If you can test
and not reproduce it, then I will close the bug as not reproducible and to
try with the latest ffmpeg CVS.