[FFmpeg-trac] #2347(avcodec:closed): Recent builds regression bug - KO from 12th Feb 2013 - OK before

[FFmpeg]

#2347: Recent builds regression bug  - KO from 12th Feb 2013 - OK before
------------------------------------+-----------------------------------
             Reporter:  feelart     |                    Owner:
                 Type:  defect      |                   Status:  closed
             Priority:  normal      |                Component:  avcodec
              Version:  git-master  |               Resolution:  invalid
             Keywords:  libx264     |               Blocked By:
             Blocking:              |  Reproduced by developer:  0
Analyzed by developer:  0           |
------------------------------------+-----------------------------------

Comment (by feelart):

 I think there is a miss-understanding.

 It reveals bugs that I and other experienced.
 Indeed

 If all that changed is compiler (gcc 4.7.2) options then it reveals is a
 deaper problem, and that's good.

 Proof
 {{{
 C:\PortableApps\MM\FFmpeg_regression\ffmpeg-20130209-git-969039e-
 win64-static\ffmpeg.exe -y -loop 1 -f image2 -i Masque16_9.png -vcodec
 libx264 -t 4 -r 25 outNoPix20130209.mp4
 C:\PortableApps\MM\FFmpeg_regression\ffmpeg-20130209-git-969039e-
 win64-static\ffmpeg.exe -y -loop 1 -f image2 -i Masque16_9.png -vcodec
 libx264 -t 4 -r 25 -pix_fmt yuv420p outWithPix20130209.mp4

 ffmpeg.exe -y -loop 1 -f image2 -i Masque16_9.png -vcodec libx264 -t 4 -r
 25 -pix_fmt yuv420p outWithPix.mp4
 ffmpeg.exe -y -loop 1 -f image2 -i Masque16_9.png -vcodec libx264 -t 4 -r
 25 outNoPix.mp4
 }}}
 With build 2013-02-09 with or without -pix_fmt yuv420p are MD5 equivalent,
 but not with recent builds!

 {{{
 Then it is like recently closed ticket 2284
 Remember that this was not a FFmpeg-related ticket.
 }}}
 I couldn't know that in advance....
 Nor can users know, that a there is a change of compiler options...

 {{{
 The playback applications you were testing (except vlc) only implement a
 very small part of the h264 specification.
 }}}
 It works like a charm with all players when encoded with builds <
 12-02-2013


 {{{
 but please remember that this is not a support forum,
 }}}
 I do know, I didn't report an usage issue, I just ask within a bug report
 a complementary information.

 {{{
 Please report all bugs that you experience with FFmpeg,
 }}}
 Unfortunately, the way you respond makes it very dissuasive, that I do
 start to understand the libav fork...
 One thing is to observe a bug, another is to make reproducable by a 3rd
 party, then try to extract its simplest form.
 It would already be a progress to say when there is a bug, but not FFmpeg
 but, to say this bug is passed to the relevant owner.

 I believe you'll get a bunch bugs(possibly many redundant) report with
 other people regarding libx264. See for instance,
 http://ffmpeg.zeranoe.com/forum/viewtopic.php?f=7&t=1054

 Me reporting others (at least 3) malformed streams bugs I do observe, in
 the present state, you totally dissuated me, I'll give a try at libav.
 Have a nice day.

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2347#comment:8>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker