On macOS you want to use "h264_videotoolbox": ffmpeg -i mysource -c:v h264_qsv -c:a copy output.mp4 Here on my Windows machine I will choose the "h264_qsv" (Intel Quick Sync Video acceleration) encoder. if you have no NVIDIA graphics card the h264_nvenc will not work. Note: not all encoders might actually work. h264_qsv H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (Intel Quick Sync Video acceleration) (codec h264) V.D h264_nvenc NVIDIA NVENC H.264 encoder (codec h264) V.D h264_mf H264 via MediaFoundation (codec h264)
V.D h264_amf AMD AMF H.264 Encoder (codec h264) V.D libx264rgb libx264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 RGB (codec h264) To get a short description of each encoder you can execute: ffmpeg -encoders This list is dependent to your OS and the enabled encoders during FFmpeg compilation. Some are software-, some are hardware-encoders. In this this you should find your target codec (h264): ĭEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_qsv h264_cuvid ) (encoders: libx264 libx264rgb h264_amf h264_mf h264_nvenc h264_qsv )
To check this you can simply execute ffmpeg -codecs Encodingįirst of all you need to know, what encoders have been enabled in your FFmpeg version. But the load depends also on other things like bitrate, resolution and CPU/hardware. And after enabling the hardware accelerated decoding it reduced the CPU load from 20% to 4%. If your CPU support for example Intel Quick Sync than you can significantly reduce the CPU load using hardware acceleration (in my test case below it was from 90% using libx264 to 20% using h264_qsv).
0 kommentar(er)
