[FFmpeg-trac] #2379(undetermined:new): FFmpeg produces broken h264 output.

FFmpeg trac at avcodec.org
Tue Mar 19 18:47:02 CET 2013

#2379: FFmpeg produces broken h264 output.
             Reporter:  dodgexander  |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  git-master   |  undetermined
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0

Comment (by cehoyos):

 Replying to [comment:5 dodgexander]:
 > I '''can't''' paste the console output because it exceeds the allowed
 text in the description and I cannot upload the log of the job because it
 exceeds the attachment limit.

 I have worked on quite a lot of tickets, I do not remember one where the
 console output did not easily fit into a text file that was not several MB

 > You develop ffmpeg, but do not know what a zip file is???

 I do know what a zip file is, unfortunately the text file in the zip is
 unreadable (as is "skippingoutput.log" which you uploaded to mediafire).

 > Here is part of the broken output:

 This folder now contains ten files: How am I supposed to know which one I
 should test?

 > And Here is a chunk larger of original further in (if you can't repeat
 with first chunk):

 "No files in this folder"

 > Like I said I don't know how to reproduce the bug with ffmpeg directly
 (not everyone has skills in how to compile and use ffmpeg, in fact I think
 the majority don't) ,

 Apart from the fact that it is easy to compile FFmpeg, it is not
 necessary, please find current builds at http://ffmpeg.zeranoe.com/builds/

 > but if you take the time to read the log, you should know better than me
 what is wrong.

 As said, the "log" is unfortunately unreadable, so far I don't even know
 what you are trying to / what you want FFmpeg to do.

 > Its clearly related to ffmpeg and not MCEBuddy.

 In this case it should be simple to provide the failing command line.

 > And the reason i upload multiple files is to help you repeat the bug.
 Here ill split the links to make it easier:
 > 100mb sample of source file: [http://www.mediafire.com/?hbhha69x4kxubyt]

 I downloaded skippingoutput.wtv (104857600 bytes, md5sum
 The file plays fine here with ffplay, I was able to convert it to avi and
 mov, I remuxed it to mpegts and all three output files play fine with

 > 400mb sample of source file

 "No files in this folder"

 > Sample of broken outut: [http://www.mediafire.com/?pvg6c4x88ejq6lf]

 > Log of conversion process (or you can use 7zip to open attached zip
 file): http://www.mediafire.com/?vs4n45q184dqm45

 As said, this is not a readable format.

Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2379#comment:6>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list