blindbunny ffmpegbugs.10.noonee...@spamgourmet.com added the comment:
Ok, the problem is not restricted to libx264, but also applies to mpeg4.
However, disabling avfilter fixes the problem. So the issue occurs when
compiling ffmpeg with, e.g.,
--enable-shared --enable-nonfree --enable-gpl
Michael Niedermayer michae...@gmx.at added the comment:
On Sat, May 29, 2010 at 07:20:35PM +, bobbele wrote:
bobbele fab...@lesniak-it.de added the comment:
I decided this bug to be important, since it's not yet fixed in todays
svn-r23371. I think that the problem is the -s switch,
blindbunny ffmpegbugs.10.noonee...@spamgourmet.com added the comment:
I'm seeing the very same problem. The command
ffmpeg -i src.mkv -s 400x320 -vcodec libx264 -vpre hq -crf 20 -an -sn scaled.mkv
-vframes 10
scales the input down to 400x320 as expected. But the command
ffmpeg -i src.mkv
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Please confirm that this only happens with x264 and test --disable-
libavfilter and provide complete, uncut output of your command line.
FFmpeg issue tracker
bobbele fab...@lesniak-it.de added the comment:
I decided this bug to be important, since it's not yet fixed in todays
svn-r23371. I think that the problem is the -s switch, which just selects the
frame size (the video won't be scaled, it's cut out) - but that only appears
when using the -crop*
Carl Eugen Hoyos ceho...@rainbow.studorg.tuwien.ac.at added the comment:
Please provide a minimal command line (if possible with -an), preferably without
using an external library (x264). If this is a regression (which would make this
issue important), please provide the version introducing the
