I have following script (named vid2gif.sh) to convert a video file to gif:
#! /bin/bash
ffmpeg -i $1 /tmp/gif/out%04d.gif
gifsicle --delay=10 --loop /tmp/gif/*.gif > $2
I can convert a file using command:
vid2gif.sh myvid.mp4 myvid.gif
How can I make it to convert all mp4 files in a folder? That is, how can I make following command work:
vid2gif.sh *.mp4
The script should output files as *.gif. Thanks for your help.
#!/bin/sh
for f; do
tempdir=$(mktemp -t -d gifdir.XXXXXX)
ffmpeg -i "$f" "$tempdir/out%04d.gif"
gifsicle --delay=10 --loop "$tempdir"/*.gif >"${f%.*}.gif"
rm -rf "$tempdir"
done
Let's go over how this works:
Iteration
for f; do
is equivalent to for f in "$@"; that is to say, it loops over all command-line arguments. If instead you wanted to loop over all MP4s in the current directory, this would be for f in *.mp4; do, or to loop over all MP4s named in the directory passed as the first command line argument, it would be for f in "$1"/*.mp4; do. To support either usage -- but go with the first one if no directory is passed -- it would be for f in "${1:-.}"/*.mp4; do.
Temporary directory use
Because the original script would reuse /tmp/gif for everything, you'd get files from one input source being used in others. This is best avoided by creating a new temporary directory for each input file, which mktemp will automate.
Creating the .gif name
"${f%.*}" is a parameter expansion which removes everything after the last . in a file; see BashFAQ #100 for documentation on string manipulation in bash in general, including this particular form.
Thus, "${f%.*}.gif" strips the existing extension, and adds a .gif extension.
TEMPDIR, or /tmp if unset. See man mktemp on your system for precise docs.
.shextensions for executable scripts (as opposed to shell libraries intended to be invoked withsource) is bad form -- executable scripts define commands, and UNIX commands don't have extensions -- they're inherently language-agnostic, as the shebang line at the top defines how they're interpreted. See talisman.org/~erlkonig/documents/… for a longer discussion.#!/bin/bashare bash scripts, not POSIX sh scripts, so using.shextensions for them is misleading; many such scripts will break in surprising ways if run withsh somescript, which the extension implies is supported).chmod +xto mark it executable, yes. If you didn't want to install it for all users, but only for yourself, you might consider making a$HOME/bindirectory and adding that to yourPATH.