Skip to main content
10 events
when toggle format what by license comment
Apr 11, 2017 at 13:20 history edited slhck CC BY-SA 3.0
deleted 445 characters in body
Apr 11, 2017 at 13:01 history edited slhck CC BY-SA 3.0
added 8 characters in body
Nov 24, 2014 at 6:33 vote accept Srini
Nov 21, 2014 at 19:57 comment added slhck 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.
Nov 21, 2014 at 19:01 comment added dstob 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.
Nov 21, 2014 at 7:25 comment added slhck 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.
Nov 21, 2014 at 4:13 comment added dstob 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?
Nov 20, 2014 at 19:25 history edited slhck CC BY-SA 3.0
added 8 characters in body
Nov 19, 2014 at 20:24 history edited slhck CC BY-SA 3.0
added 602 characters in body
Nov 19, 2014 at 20:14 history answered slhck CC BY-SA 3.0