![]() ![]() I think we should consider updating the docs since I suspect that users of that configuration are not actually getting hardware acceleration - if I didn’t specify -c:v h264_qsv then I got no errors… but it wasn’t actually using hardware acceleration. I also tried -vf hwdownload,format=nv12,format=yuv420p and it worked, but it it used slightly more CPU than the vpp_qsv configuration, plus I suspect it’s less portable since it’s not really documented which formats are supported for direct hwdownload with which drivers and hardware. With this set up, each 640x480 7fps reolink detect steam uses 3% of one E-core on my 12700. ![]() I think for Alder Lake on linux, qsv doesn’t support yuv420p as a hwdownload format (it does support nv12!), so we need a second pass to convert it to yuv420p in hardware, then use -gpu_copy for accelerated copy from the hardware memory to software. This does result in CPU improvement and I do see activity in intel_gpu_top. Ok, I got qsv hwaccel “working” on beta7 with this config: hwaccel_args:ĭetect: -vf vpp_qsv=format=yuv420p -f rawvideo -pix_fmt yuv420p Any other information that may be helpful Relevant log output Error initializing an internal MFX session: unsupported (-3) Record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v h264_qsv -c:a copy -an VersionĠ.10.1-83481AF Frigate config file ffmpeg: The stock Docker image will fail to initialize the hardware encoder/decoders using qsv if this package is not installed (see general Ubuntu bug)Īfter adding the(deb focal main) and installing libmfxgen1 via apt-get results in the ffmpeg instance being able to correctly utilize qsv. In order to use the qsv device, the Docker image needs to have libmfxgen1 installed as per the Intel compatibility matrix ![]() I have an Alder Lake gen12 CPU that I’m utilizing QuickSync for hardware transcoding. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |