I put the second filter on top of the first, otherwise this would not work.

Because of the first filter I had to define values somewhat like z=75%, x=xxx & y=yyy, instead of z=100%, x=0 & y=0. Then, I instatiated another Rotate & Scale filter because I wanted to zoom out and pan to the “full” picture. For that I used a Rotate & Scale filter with z=175%, x=xxx and y=yyy, but did not define keyframes for that filter. I wanted to zoom in and pan to a starting point at t=00:00:00. I used two instances of the Rotate & Scale filter because I didn’t use keyframes properly. However, I think I solved the problem partly: What is your operating system? $ uname -a It’s the same resolution as my input frames: $ ffprobe timelapse_profiled_huffyuv.mkvįfprobe version 3.4.6-0ubuntu0.18.04.1 Copyright (c) 2007-2019 the FFmpeg developersīuilt with gcc 7 (Ubuntu 7.3.0-16ubuntu3)Ĭonfiguration: -prefix=/usr -extra-version=0ubuntu0.18.04.1 -toolchain=hardened -libdir=/usr/lib/x86_64-linux-gnu -incdir=/usr/include/x86_64-linux-gnu -enable-gpl -disable-stripping -enable-avresample -enable-avisynth -enable-gnutls -enable-ladspa -enable-libass -enable-libbluray -enable-libbs2b -enable-libcaca -enable-libcdio -enable-libflite -enable-libfontconfig -enable-libfreetype -enable-libfribidi -enable-libgme -enable-libgsm -enable-libmp3lame -enable-libmysofa -enable-libopenjpeg -enable-libopenmpt -enable-libopus -enable-libpulse -enable-librubberband -enable-librsvg -enable-libshine -enable-libsnappy -enable-libsoxr -enable-libspeex -enable-libssh -enable-libtheora -enable-libtwolame -enable-libvorbis -enable-libvpx -enable-libwavpack -enable-libwebp -enable-libx265 -enable-libxml2 -enable-libxvid -enable-libzmq -enable-libzvbi -enable-omx -enable-openal -enable-opengl -enable-sdl2 -enable-libdc1394 -enable-libdrm -enable-libiec61883 -enable-chromaprint -enable-frei0r -enable-libopencv -enable-libx264 -enable-shared I don’t know how many other ffmpeg switches this also applies to, but I thought I’d share it as I personally couldn’t find anything about it elsewhere.You said you created a huffyuv video from the images. I have never encountered a command-line app where the order of the switches actually mattered, until now. The second one before, and its the second one I wanted, cropping the video first, then resizing it. Output2.avi: RIFF (little-endian) data, AVI, 320 x 240, 25.00 fps, video: FFMpeg MPEG-4, audio: MPEG-1 Layer 1 or 2 (stereo, 44100 Hz)Īs you can see, the first output file has its dimensions cropped after resizing. Output1.avi: RIFF (little-endian) data, AVI, 298 x 232, 25.00 fps, video: FFMpeg MPEG-4, audio: MPEG-1 Layer 1 or 2 (stereo, 44100 Hz) Input.avi: RIFF (little-endian) data, AVI, 640 x 480, 25.00 fps, video: XviD, audio: MPEG-1 Layer 3 (stereo, 44100 Hz) Now let’s look at the output with: file *.avi. In the second case we set the cropping first. Notice that in the first case, we’ve set the size first (qvga means 320×240). Our input file, input.avi is a 640×480 video.įfmpeg -i input.avi -s qvga -croptop 8 -cropright 22 output1.aviįfmpeg -i input.avi -croptop 8 -cropright 22 -s qvga output2.avi I wanted to remove these, but have a fixed output size. The video I was re-encoding had some fuzziness at the top, and an ugly black border down the right-hand side. I discovered something whilst trying to crop and re-size a video with FFMPEG: the order of switches actually matters! I couldn’t find any mention of this in the documentation, and nowhere could I find an explanation of why my video was being cropped after it was resized.

Ffmpeg resize scale