Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Is this the timestamp in relation to a constant framerate placed on the output or the correspondence of the outputted jpegs to the original mp4 timestamps that could be any framerate and have any timestamp values?
    – dstob
    Commented Nov 21, 2014 at 4:13
  • This timestamp is based on the requested output framerate. It relates to both the output pictures as well as the original input video frames those pictures came from—there is only one time base. This works because when changing the framerate, ffmpeg will (of course) not play the video faster, but "stretch" the presentation time of each frame, and drop unneeded frames.
    – slhck
    Commented Nov 21, 2014 at 7:25
  • Why does there have to be only one time base when you are manually creating the output time base? This won't always be the case of course but on the first 60 fps video I threw at it, ffmpeg just created its own time base ignoring the time stamps of the input.
    – dstob
    Commented Nov 21, 2014 at 19:01
  • 1
    Not sure I understand what exactly you're getting at. ffmpeg selects as input timebase whatever it parses as the first input file's timebase. You can of course also tell ffmpeg to throw away the input timestamps with -vsync drop, but that happens after filtering, IIRC.
    – slhck
    Commented Nov 21, 2014 at 19:57