[FFmpeg-trac] #926(undetermined:new): -r ignored, resulting in error "Option framerate not found"

[FFmpeg]

#926: -r ignored, resulting in error "Option framerate not found"
-------------------------------------+-------------------------------------
             Reporter:  charlesc     |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:               |                  Version:
  undetermined                       |  unspecified
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 This is essentially the same as #403, though that was closed as invalid.
 This appears to be valid.

 I've been using ffmpeg to generate video (various video codecs) from
 individual frames generated by another program, which is fed to ffmpeg by
 pipe to stdin in yuv4mpegpipe format, along with a separate audio file.
 This worked for a long time, with a commandline like this:
 {{{
 ffmpeg -i /path/to/audio.m4a -acodec copy \
   -r 25 -f yuv4mpegpipe -i - \
   -vcodec flv -vb 250k -qmin 5 -qmax 50 -g 150 \
   -y /path/to/output.flv
 }}}

 The yuv4mpeg header that's being generated by the program is this:
 {{{
 YUV4MPEG2 W854 H480 F25:1 Ip A0:0 C420mpeg2 XYSCSS=420MPEG2
 }}}

 With recent versions of ffmpeg built from the git repo (my current version
 is `ffmpeg version N-32933-g9b3df9b [...] built on Sep 25 2011 14:17:40
 with gcc 4.4.3`), ffmpeg refuses to start with this same command, exiting
 with returncode 1 and giving this error:
 {{{
 Option framerate not found.
 }}}

 If I leave off the `-r 25` option it appears to work, using the input
 framerate from the yuv4mpeg header.  But shouldn't it let me override that
 with `-r`, say if I wanted the output video to run at 30fps instead of 25?

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/926>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker