"B. Bogart" writes:
> Disabling mmx does solve the segfault.
>
> The cause of the problem is jpgs of different classes in my sequence. I
> ended up with some pseduoclass images in the sequence of largely
> directclass jpgs, which kill ffmpeg. With mmx enabled this results in a
> segfault, with mm
Disabling mmx does solve the segfault.
The cause of the problem is jpgs of different classes in my sequence. I
ended up with some pseduoclass images in the sequence of largely
directclass jpgs, which kill ffmpeg. With mmx enabled this results in a
segfault, with mmx disabled ffmpeg just quits
"B. Bogart" writes:
> Reinhard Tartler wrote:
>> this is a good indication that this bug is also present in current
>> trunk, i.e., this bug needs to be confirmed and upstreamed.
>
> Compiling ffmpeg fresh for current svn also has the same problem.
okay, then this bug definitly upstreaming.
see
Reinhard Tartler wrote:
this is a good indication that this bug is also present in current
trunk, i.e., this bug needs to be confirmed and upstreamed.
Compiling ffmpeg fresh for current svn also has the same problem.
Just a try: please disable your /usr/lib/i686/cmov/ directory (e.g.,
by rena
tags 561553 upstream
stop
"B. Bogart" writes:
> When trying to run the same ffmpeg command I get an identical segfault,
> always happening around frame 214xx. Remeber all frames are simply
> links that point to the attached jpeg.
>
> This happens both in the lenny ffmpeg, and the ffmpeg includ
5 matches
Mail list logo
