I've been using ffmpeg for decades, and while it's not the easiest tool to understand the logic of the command line arguments of when you first dive into it, once you "get it", it's quite fucking brilliant.
Case in point: only 3 days ago, I made a shell script to take a bunch of 360° photographs shot at regular intervals and concatenate them into a timelapse video file. The single ffmpeg command:
Rescales the input images to a more manageable resolution for 360° video players
Denoises the images by blending each image with its two "neighbors" before and after it
Reprojects the scene by yawing the POV some 40° to the right to face the subject of the video
Color-corrects the images to lift the shadows and the midtones a bit because the images were shot at dusk and were underexposed
Superimpose the time of the day at which the individual frames were shot from the image files' timestamps in the 360° view at a particular spot in the sphere
Speeds up the video 90x
All that in ONE SINGLE COMMAND.
ffmpeg is the most powerful tool ever! I fucken love it.
And the entire supporting shell script around it is 76 lines. That's really not a lot of shell script to do that much ultra-specialized video editing... This would never be possible without ffmpeg.
1 reply
I've been using ffmpeg for decades, and while it's not the easiest tool to understand the logic of the command line arguments of when you first dive into it, once you "get it", it's quite fucking brilliant.
Case in point: only 3 days ago, I made a shell script to take a bunch of 360° photographs shot at regular intervals and concatenate them into a timelapse video file. The single ffmpeg command:
All that in ONE SINGLE COMMAND.
ffmpeg is the most powerful tool ever! I fucken love it.
And the entire supporting shell script around it is 76 lines. That's really not a lot of shell script to do that much ultra-specialized video editing... This would never be possible without ffmpeg.
(And here's the script If you're curious:)