Am Mo., 13. Mai 2019 um 15:29 Uhr schrieb Carl Eugen Hoyos < [email protected]>:
> Am Mo., 13. Mai 2019 um 15:05 Uhr schrieb Jon bae <[email protected]>: > > > > Am Mo., 13. Mai 2019 um 14:34 Uhr schrieb Carl Eugen Hoyos < > > [email protected]>: > > > > > Am Mo., 13. Mai 2019 um 14:31 Uhr schrieb Michael Koch > > > <[email protected]>: > > > > > > > > Or the fps filter. > > > > > This filter and the r option have different algorithms that have > > > > > advantages (and disadvantages) in different situations. > > > > > > > > Are the differences explained somewhere in the documentation? > > > > > > Not to my knowledge, them main difference is that the filter is > > > more greedy. > > > > > > Carl Eugen > > > > > > > > Sorry Carl Eugen - you are right. I did a test, and when I apply the fps > > filter after setpts it not duplicate any frames. > > Sure? > > I mean: It may or may not duplicate frames but contrary to "-r" > the console output will not tell you. > > As Moritz wrote: If your input is cfr, you only need setpts, > fps is needed just in case an initial or final frame is missing. > If your input is not cfr, setpts may or may not work > correctly but you need fps (or -r) to create cfr video > which the mp4 muxer expects. > > At least by my test file the fps filter has not duplicate frames, when I add it after setpts. In my tests I have to use fps filter or the -r option, when I don't use them I get no 25 fps in my output file. I think we mostly deal with crf files. _______________________________________________ ffmpeg-user mailing list [email protected] https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email [email protected] with subject "unsubscribe".
