enable-vaapi switch should be enough, though.

It means that when you're encoding content for use with your blogs or some fancy youtube download, you can do it much, much faster on hardware with lower processor utilization (so you can multi-task), lesser heat output and, as a plus, is significantly faster (As tested on my end, ~8.7x for 1080p and ~4.2x for 4k encodes with reference media) compared to a pure, software-based approach as offered by libx264 and similar implementations, albeit at an acceptable quality compromise.įirst, you will need to build ffmpeg (and libav,as per your preferences) with appropriate arguments. Basic competence on the shell, such as reading man files, using a text editor of choice, manipulating file operations on the same, etc is assumed.Īnd as an indemnity clause, I, the author, will not be liable for any damage, implied or otherwise, to your files, hardware or the stability of your machine as a consequence to using these instructions to achieve a similar feat as described in this gist.That the user is comfortable with the Linux terminal, and can navigate through it.The end user can install, upgrade, downgrade and resolve both conflicts and dependency resolution of packages on his/her distribution's package manager.The end-user can comfortably install and configure their Linux distribution of choice.Supported hardware that works reliably well to be termedīefore taking on this manual, the author assumes that: Using VAAPI's hardware accelerated video encoding on Linux with Intel's hardware on FFmpeg and libavĪs it turns out, the current version of FFmpeg (version 3.1 releasedĮarlier today) and libav (master branch) supports full H.264 and HEVC encode in VAAPI on

Hvec sdk ffmpeg download