[FFmpeg-trac] #3399(undetermined:closed): Bad output framerate decision for mp4 from camera

FFmpeg trac at avcodec.org
Wed Feb 19 17:12:37 CET 2014


#3399: Bad output framerate decision for mp4 from camera
-------------------------------------+-------------------------------------
             Reporter:  mressler     |                    Owner:
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:
              Version:  git-master   |  undetermined
             Keywords:  fps mov      |               Resolution:  duplicate
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  1
-------------------------------------+-------------------------------------

Comment (by mressler):

 So -r will force the framerate, but how did you know to use those values?
 What about the source video caused the bad decision to be made by ffmpeg?
 I ask so that I can detect this automatically for my users in the future.

 Is it a good idea to always manually force the framerate?

 The sample command you ran didn't include the -r option?

--
Ticket URL: <https://trac.ffmpeg.org/ticket/3399#comment:6>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list