# non-free リポジトリの追加 sudo apt install software-properties-common It is not included in the LD-PATH and is not recognized by the MediaSDK build.Īdd it to the LD-PATH with the following command: Libva that is built and installed is deployed to the /usr/local/lib. (If it is a large-scale build, it will take quite a while.) ) If you are not doing other work in parallel, it is recommended to add an option.

If not specified, there will be at most one, i.e. (It would be nice to specify the number of CPU threads +1.) My environment is 5 because it is 4 threads.

(A directory called build has existed since the beginning, so instead of b.) )Īn option -j5 for make is the maximum number of jobs to run in parallel. I created a directory called b and am doing the build work in it, but there is no problem even if this procedure is not required. # 依存パッケージ & 必要なツールインストール sudo apt install meson libdrm-dev automake libtool (It is not good to publish something that has not been confirmed.) ) Preparing the Build Toolsįrom module preparation to building ffmpeg, install the essential tools for building first. NVIDIA, AMD has only checked for help because I don't have a machine for GPU encoding. The procedures and commands displayed here have been confirmed to be executed in the following environments. (I don't usually use them all.) If you're in a weird environment using three hard PCs, that's a different story. This article summarizes how to deploy and build QSV, AMF, NVENC to FFMPEG.īy following all of the steps listed here, you can build a ffmpeg that you can hardware-encode on any Intel GPGPU, AMD GPU, or NVIDIA GPU.

To do hardware encoding, you must prepare the module and build ffmpeg yourself. (On Linux Mint, installing ffmpeg as a package from apt made NVENC available.) ) The default ffmpeg is software encoding only. Ffmpeg allows hardware encoding using Intel's QSV, AMD's AMF, and NVIDIA's NVENC.

Ffmpeg h264 hardware encoding