Hey everyone, I am wondering about the decision to have cv::ocl::convertFromImage copy the image data into a new OpenCL buffer owned by a cv::UMat whereas cv::ocl::convertFromBuffer simply attaches the cl_mem buffer to a cv::UMat. Is there some reason that OpenCV cannot do the same for an OpenCL image2d? Unfortunately you can’t use convertFromBuffer on an image2d because it fails type and size assertions when attempted. Is this merely a case of not being needed yet, or is there some deeper issue that would render this impossible without a copy? Thanks.
Related Topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Why does _InputArray::convertTo(OutputArray dst, int rtype, ..) or cv::convertTo(..) not exist? | 2 | 650 | November 29, 2021 | |
| convertFromD3D11Texture2D throws OpenCL: Context initilized without DirectX interoperability | 0 | 325 | December 1, 2023 | |
| Qt+OpenCV use cv::ogl::texture2D::copyFrom( cv::cuda::GpuMat) to get texture directly | 8 | 1540 | July 7, 2022 | |
| Switch cv::ocl context | 0 | 424 | January 18, 2022 | |
| Copy cv::cuda::GpuMat in Cuda Kernel | 4 | 1418 | October 5, 2022 |