ln -s /usr/local/bin/ffmpeg/ffmpeg /usr/bin/ffmpeg Next, go ahead and create a symlink so that ffmpeg can be run from any location. Step 6: Create a symlink to use ffmpeg from any location It should output something like: ffmpeg version 4.2.1-static Go inside this folder to check if ffmpeg has been installed successfully or not./ffmpeg -version
This will create a folder named ffmpeg-4.2.1-amd64-static . Use the following command to unzip the binaries. Inside the /usr/local/bin/ffmpeg folder run this command to download the static binaries. Note: That last i386 indicates that it’s 32-bit x86_64 indicates 64-bit.Īlso, by hit and trial, I found out that the processor is AMD and not ARM. To check if your system is 32-bit or 64-bit you can execute the following command: uname -a Replace the ffmpeg-amd64-static with the current build version. txt file, you will see the current version of the build. Click on the “build info” link at the releases page and at the top of the. Note: To find the current build version from John’s site. Go to the following link and download a static build relevant for your system. Step 4: Download a static build of ffmpeg Step 3: Inside the /usr/local/bin directory, create an ffmpeg directory and go inside it. Step 2: Go to the /usr/local/bin directory cd /usr/local/bin
Step 1: SSH into your instance and become root sudo su. To be fair ffmpeg has provided aĬompilation guide for CentOS but for lazy people, it is too much of an effort. :)įinally, I found a solution that worked perfectly so I thought of sharing it here. For Debian and Ubuntu distributions, ffmpeg is available as a apt-get package but for other distributions you have to manually compile it. The issue was that my EC2 instance is running Amazon Linux based AMI which is probably based on some version of CentOS. Recently, I needed to install ffmpeg on my EC2 instance and I struggled quite a bit to set it up.
0 kommentar(er)
