com / ffmpeg / Copyright ( c ) 2000 - 2021 the FFmpeg developersįFMPEG : built with gcc 8 ( Debian 8.3. SERVER : rtmp destination set to : rtmp : // broadcast. SERVER : Please set rtmp destination before start streaming. Take this as a work in progress.SERVER : Hello from mediarecorder - to - rtmp server! There's a possibility that the AMD AMF-based encoders will eventually land on Linux, using a Vulkan-based interop.

You may also find helpers, such as this, useful. See the compilation guide on the FFmpeg Wiki, and adapt as needed.

However, you can also build a copy from source, if so needed. It's most likely that FFmpeg with VAAPI enabled is the default on the likes of Ubuntu. On your system and confirming what encoders are supported. You can confirm this by running: vainfo | grep Slice To the best of my knowledge (correct me if I'm wrong), VP8 and VP9 encoding isn't exposed on AMD's side via VAAPI. On Linux, using the opensource mesa amdgpu driver (not the proprietary package installed from AMD), you can access VAAPI-based encoders, aptly named h264_vaapi and hevc_vaapi, whose usage can be viewed via: ffmpeg -h encoder=h264_vaapi Note that the resulting build above is non-redistributable, and is only for personal use. cross_compile_ffmpeg.sh -gcc-cpu-count=12 -build-libmxf=n -disable-nonfree=n -prefer-stable=y -compiler-flavors=multi If you use the cross-compile option, pass the arguments below for a build with the features you'll need. This project is a great start on that subject. You'd need to build an FFmpeg binary for Windows, either natively, or as recommended, cross-compiling. If you're on Windows, you can access the related encoders via AMF, aptly named h264_amf and hevc_amf, whose usage can be viewed via: ffmpeg -h encoder=h264_amf Use these instructions that are applicable to your case.

I'll provide instructions for both Windows and Linux, as you've not indicated what platform you're on.

Ffmpeg mac using cpu