2017-07-21 13:02:49 -0600 | commented answer | cv::gpu::solvePnPRansac |
2017-07-18 17:02:53 -0600 | commented question | OpenCV InputArray to std::vector<type> @LBerger Obviously, I would like to use an existing one. |
2017-07-18 12:49:43 -0600 | asked a question | OpenCV InputArray to std::vector<type> I have a function which takes in an What is the correct way to go about doing this? |
2017-07-17 17:56:17 -0600 | commented question | Can not resolve JNI function in Android stdio There is really no way to diagnose this problem without further information. |
2017-07-17 13:19:11 -0600 | answered a question | cv::gpu::solvePnPRansac You can find them in the legacy support module: http://docs.opencv.org/3.1.0/d5/dc3/g.... My hope is that the cv::gpu::SolvePnPRansac modules will be moved to use cv::UMat, as that is more compatible and not CUDA specific. That is speculation, however. |
2017-07-17 13:13:22 -0600 | received badge | ● Scholar (source) |
2017-07-14 20:21:55 -0600 | answered a question | VideoCapture not working in opencv android Asaik, without re-writing some of the wrappers for the VideoCapture class, it does not work inside OpenCV4Android. I have tried several things without changing the source code. I think that it is because of the discrepancies and maintenance required to support various APIs/Devices. Also, maybe the underlying image buffers used by Android cause problems. As the other answer indicates, you can use it to read from AVI, and some specified file formats. Apologies, I forgot to add that. |
2017-07-14 14:35:46 -0600 | commented answer | How to run "build_sdk.py" for Android SDK ^ link is now broken, again. |
2017-07-14 14:33:05 -0600 | commented question | How can i build opencv 3.2.0 on Android with build_sdk.py I totally agree. The amount of help centered around building OpenCV4Android is really not good. But,it looks like it is trying to do some form of installation. But, in case you were wondering about usage, here is another question about the same thing, that was answered: http://answers.opencv.org/question/73... Hope it helps! |
2017-06-14 18:53:38 -0600 | commented question | OpenCV OCL with Intel CPU OpenCL on Ubuntu Hey, have you ever solved this problem? I am having a similar issue with this. I am running a bootcamped Mac Book Pro, with Windows 10, and the run time performance of my application is significantly different than when run on my desktop version. Actually seems like there is a fundamental problem with race conditioning. Like, I get consistent errors with vector iterators being out of bounds.... I feel as if there is maybe some bug with the OpenCL driver in boot-camped mac world. |
2017-04-18 13:55:16 -0600 | answered a question | Building OpenCV4Android With OpenGL and OpenCL Support As a temporary answer: I have looked through the source code, and in |
2017-03-30 12:38:46 -0600 | received badge | ● Enthusiast |
2017-03-29 12:56:45 -0600 | received badge | ● Editor (source) |
2017-03-29 12:51:55 -0600 | asked a question | Building OpenCV4Android With OpenGL and OpenCL Support
I am using the Android NDK, and was using the pre-compiled OpenCV4Android binaries. Everything was going well, until I needed to do some texture handling, and had to use the
So, to get around this, I thought that I should re-build OpenCV4Android, trying to include the OpenGL flag, and (for posterity) explicitly turn on the OpenCL flag-- I have done custom builds on the desktop, no problem. Building OpenCV4Android with OpenCL is actually pretty straight forward: after following this tutorial, you pass the However, building with OpenGL, seems really difficult. I know that there could be issues with the native OpenGL ES support that Android provides in their NDK, resulting in there being absolutely no-way to support OpenCV implementations of OpenGL. However, I find it weird that the header content for OpenGL would then still be referenced in the source code for Android builds. Also, after looking at the header file for the What I have tried so far is modifying the OpenGL flags within the parent Any definitive answer on this would really be appreciated! Also, including this information within the development page, would save lots of people trouble! Knowing what they can, and cannot build with is important! (Also, sorry for not hyperlinking keywords; apparently I have insufficient karma to do so. But, every link I followed was from the openCV website, under the Android Platform list. ) |