[FFmpeg-trac] #593(undetermined:new): ffmpeg + libx264: Input picture width is greater than stride
FFmpeg
trac at avcodec.org
Wed Oct 26 14:05:43 CEST 2011
#593: ffmpeg + libx264: Input picture width is greater than stride
-------------------------------------+-------------------------------------
Reporter: whitemagic | Type: defect
Status: new | Priority: normal
Component: | Version:
undetermined | unspecified
Keywords: libx264 | Blocked By:
multiple output resolution stride | Reproduced by developer: 0
Blocking: |
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
I receive raw video from a Blackmagic Decklink card through a pipe and
would like to encode it to two or more different resolution/quality H.264
streams with AAC audio (e.g. encode a full HD and a 640x360 version) using
a single command line.
Everything fine if only a single output 1920x1080 stream is defined. If I
add an other one (say 640x360), then I get this error from libx264:
[libx264 @ 0x146ff80] Input picture width (1920) is greater than stride
(640)
Although, if the second stream has the same resolution (ie. 1920x1080)
then it is ok. But this is not my intention to encode two of the same
quality. I cannot find anything useful on this problem.
I am using this version of ffmpeg:
FFmpeg version SVN-r25838, Copyright (c) 2000-2010 the FFmpeg developers
built on Sep 20 2011 17:00:01 with gcc 4.4.5
Video encoding failed
My command line is:
ffmpeg -v 9 -loglevel 99 -pix_fmt yuv422p -s ${video_res} -r ${video_fps}
-i - \
-ar 48000 -f s16le -ac 2 -i - -vol 2048 -acodec libfaac -ac 2 -ab 128k
-ar 48000 -async 1 \
-vcodec libx264 -vpre fast -vpre baseline -threads 0 -s ${video_res} -b
2000k -bt 100k -y -f mp4 test.mp4 \
-ar 48000 -f s16le -ac 2 -i - -vol 2048 -acodec libfaac -ac 2 -ab 128k
-ar 48000 -async 1 \
-vcodec libx264 -vpre fast -vpre baseline -threads 0 -s 640x360 -b 500k
-bt 50k -f mp4 test_lq.mp4
(input is a pipe, so cannot provide the input itself)
I am attaching the full output of my ffmpeg. Please help me to localize
the problem whether ffmpeg or libx264 is causing it. Thanks.
--
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/593>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list