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

FFmpeg trac at avcodec.org
Fri Mar 22 21:19:12 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:31 dodgexander]:
 > >I may of course be wrong, but I would be very surprised if this
 "detection" works, I find it much more likely that your whole stream gets
 > This is what I would have thought too, but there is an aggressive option
 and a force option. With the converted file, only force works, so I
 suspect they are different, somehow.

 Of course: The original file is sent with the interlaced flag (for the
 whole file); since you (I) did not specify the interlaced option for the
 transcoding (-flags +ildct+ilme), the output file does not contain the
 interlaced flag (that has absolutely nothing to do with interlaced
 *content* but only interlaced encoding which is always used where I live,
 no matter if the content is interlaced and a deinterlacer is needed or if
 the content is progressive - the reason is that from a broadcaster's
 point-of-view, encoding progressive material as interlaced only has a
 minor overhead while encoding interlaced material as progressive costs a
 lot of quality).

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

More information about the FFmpeg-trac mailing list