[Ffmpeg-devel] Two ASF related bugs and fixes

Kohn Emil Dan emild
Tue Apr 18 16:19:08 CEST 2006

Yep, I saw that. I have resent the post.



On Tue, 18 Apr 2006, Steve Lhomme wrote:

> emild at cs.technion.ac.il wrote:
>> Hello,
>> I have found two bugs related to ffmpeg's ASF file format.
>> 1) The first bug has to do with the ASF writer. The problem is caused by 
>> the
>> fact that the size of the padding is not adjusted to include the size of
>> the padding length field. This causes the last byte of the payload to be
>> overwritten with zeroes before it is written to disk, thus yielding an 
>> invalid
>> bitstream.
>> mplayer and even ffmpeg complain when such streams are passed to them.
>> I have put an input file which illustrates the problem at:
>> ftp://ftp.mplayerhq.hu/MPlayer/incoming/ASF_PROBLEM/WRITER/IN/Philips_qcif.mp4
>> and the resulting output at:
>> ftp://ftp.mplayerhq.hu/MPlayer/incoming/ASF_PROBLEM/WRITER/OUT/buggy_Philips_qcif.mp4.asf
>> The command line used was:
>> ffmpeg -i Philips_qcif.mp4 -r 15 -b 64 -an -s 176x144 -vcodec wmv1
>> buggy_Philips_qcif.mp4.asf
>> For example this is what mplayer has to say about the resulting output 
>> file:
> I think you ended up your email prematurely. The output of Mplayer is not 
> there, and there is no mention of the second bug.
> Steve
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel at mplayerhq.hu
> http://mplayerhq.hu/mailman/listinfo/ffmpeg-devel

More information about the ffmpeg-devel mailing list