[FFmpeg-trac] #2347(avcodec:closed): Recent builds regression bug - KO from 12th Feb 2013 - OK before
FFmpeg
trac at avcodec.org
Tue Mar 12 10:01:45 CET 2013
#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 cehoyos):
Replying to [comment:12 feelart]:
> If you're quote "If you know in advance that quality does not matter or
if you know in advance that you must play your output file with software
that does not support anything else but yuv420p, then please add -pix_fmt
yuv420p to your command line." would be valid then MD5 signature for
FFmpeg ante 9th Feb would all be the same and would be the same as results
with ffmpeg-20130209 with -pix_fmt yuv420p, but they are not.
The reason is a change in cf8d9b7
Please test the following command lines with your "20130209-git-969039e"
version to see that this commit did not introduce a bug but actually fixed
one by changing an erratic and difficult to describe behaviour:
$ ffmpeg -i Masque16_9.png -pix_fmt rgb24 out.png
$ ffmpeg -loop 1 -i out.png -vcodec libx264 -t 4 -r 25 out.mp4
(The command "works" with your rgba sample, but produces yuv444p output
for rgb24 input: This was imo inconsistent behaviour that was fixed in
cf8d9b7.)
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2347#comment:13>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list