Hello friends. The following program WORKED to read image files, but it stopped working and gave the following error: global loadsave.cpp:268 cv::findDecoder imread_ (''): can't open/read file: check file path/integrity …
Hello guys. I’m during 3 days trying to make opencv to work with CUDA. I already have CUDA installed, cudnn etc. What happens: After making all process described in some youtube videos, many and many times, with lots of versions of opencv, with visual studio 2019 and 2022, the last command which I should do is cmake --build “path” --target INSTALL --config Release. In the example video ...
I think there was an update to the input sent to opencv in version 4.11 and it especially affects Linux-based systems. The question is, how should we adjust the array inputs created with numpy in Linux-based systems in the current version?
The Python Category is for discussion of Python coding issues, optimizations, or questions associated with OpenCV. Please keep discussion limited to OpenCV related topics. General discussion of Python events, topics and style should happen at the Python website. Thanks!
most likely an installation problem. please recap, if you built the libs locally, in which case stuff went to : /usr/local/include/opencv4/ and the libs to: /usr/local/lib/ or if you got them from some ppm (noone knows, then …) but it’s likely /usr/include/opencv4/ for the headers & /usr/lib/ for the resp. libs.
I am building an OpenCV library by Cmake with Cuda. My GPU and Cuda Toolkit are GTX1650 and v12.8, respectively. The command is following: cmake -G "Visual Studio 17 2022" -DCMAKE_BUILD_TYPE=Release ^ -D …
I tried to run opencv using Visual Studio on Windows 11. But it is missing many include files. I think I was missing some steps during the installation process. For instance if I go look for opencv2/include there is only one include file located in the directory. that file has the name, opencv.hpp the location of that file is placed under the C ...
the opencv.js project was a GSoC project, a kind of feasibility study. there is hardly any code using it for LLMs to learn from. approxPolyDP was never useful for things with rounded corners. there’s a new approxPolyN function that you should take a look at. for things with rounded corners, it makes sense.
Hello everyone, I have been working on a project in which I need to compute a depth map. In order to do so, I have used both Stereo BM and Stereo SGBM algorithms after computing a stereo calibration. Both gave me not good results at all, even when playing with the different parameters. After having done some post filtering work with the wls_filter.filter () function, the result with the SGBM ...
