Hardware-accelerated Video I/O

• Status: WIP
• Platforms: Linux, Windows

The patch #19460 (thanks to @mikhail-nikolskiy) added properties to control hardware-acceleration of video decoding/encoding tasks. This patch is going to be released with OpenCV 4.5.2.

Support matrix for these properties:

Hardware-acceleration is available in preview mode (disabled by default), so feel free to try it with your HW configurations:

VideoCapture capture(filename, CAP_FFMPEG,
    {
        CAP_PROP_HW_ACCELERATION, VIDEO_ACCELERATION_ANY,
    }
);

or run OpenCV Video I/O tests (opencv_test_videoio).

In case of observed problems, please create new issue with adding reference to this issue.

API documentation page is here
Wiki page: https://github.com/opencv/opencv/wiki/Video-IO-hardware-acceleration

This is commutative issue for patches and bug reports about hardware-accelerated video decoding/encoding.

🚀 Noticeable PRs:

• videoio: HW decode/encode in FFMPEG backend; new properties with support in FFMPEG/GST/MSMF #19460 (feature) - added properties support + enabled generic APIs like D3D11/VAAPI + enabled Intel Integrated Graphics
• cv::UMat output/input in VideoCapture/VideoWriter (data stays in GPU memory) #19755 (feature) - cv::UMat output/input in VideoCapture/VideoWriter
• 🚧

🚨 Issues:

• Several test cases in videoio/videocapture_acceleration.read fail on Windows (VP9) #19694: failed VP9 test cases on Windows + Quadro P2000 (CUDA 11.2)
• 4.5.2 Videoio breaking change for GPU acceleration #19867: 4.5.2 Videoio breaking change for GPU acceleration
• VideoCapture with FFmpeg and CUDA Hardware Acceleration Returns Empty Frames in OpenCV 4.7.0 #25185