4 ms·

Thanks for the frame ranges. So... ffmpeg -i zelda.mp4 -vf "perspective=60:90:589:147:50:415:582:418:enable='not(between(n,0,149)+between(n,1488,2063))'" -c:a

• Daiz 12y ago
  >-vf "perspective=60:90:589:147:50:415:582:418:enable='not(between(n,0,149)+between(n,1488,2063))'" Incidentally, this is a pretty big reason why I'd pick Avisynth over ffmpeg for video filtering any day of the week.
  • ux 12y ago
    Haters gonna hate. You can put that filtergraph in a file with line returns or whatever clarity you fancy. Note that FFmpeg doesn't require wine to work on Linux (or any other system), and it also handles here the audio, the encode, and the remuxing. (Ah, and it doesn't need to download dll on random dubious sites or lost forum threads to make it usable)
  • pkroll 12y ago
    As a fan of AviSynth, the scripts that I build often make that line look so, so simple. :) And you can use ffmpeg (and a couple of other tools) in VirtualDub 1.10+ to directly render to MP4 with no interstitial file (it'll handle all the pipelining for you). They're all useful tools.
    • Daiz 12y ago
      >As a fan of AviSynth, the scripts that I build often make that line look so, so simple. :) And now imagine what those scripts would look like as an ffmpeg -vf command! That was basically the point - the -vf line is already pretty messy with just one range-applied command, and would become even more so if you started doing something more complicated. Avisynth on the other hand has actual scripts for the video processing, which scales to much more complex processing while still remaining accessible. ffmpeg -vf might be good for doing one or two simple things to the whole video, but for anything more complex than that you really should use an actual video processing solution instead.
      • ux 12y ago
        That's why you have -filter_script and -filter_complex_script options.