Comments on: OpenCV – Open Source Computer Vision Library http://blog.trossenrobotics.com/2007/02/15/opencv-open-source-computer-vision-library/ The Trossen Robotics Blog is the place to keep up to date on all the latest product releases and news in robotics. Tue, 23 Feb 2010 19:18:21 -0600 http://wordpress.org/?v=2.8.4 hourly 1 By: Yasunari Tosa http://blog.trossenrobotics.com/2007/02/15/opencv-open-source-computer-vision-library/comment-page-1/#comment-62590 Yasunari Tosa Sun, 08 Jun 2008 20:49:52 +0000 http://blog.trossenrobotics.com/index.php/2007/02/15/opencv-open-source-computer-vision-library/#comment-62590 You can use C++/CLI under Windows with VS2005 or later to create wrapper classes to use OpenCV or whatever C++ libraries you want to use. It is very easy. This is the major differece from Java where only native C functions can be imported. One issue with OpenCV in that quality of codes varies from one subject to the other. Even worse: the one I downloaded had memory leak in the basic level under Windows environment but the developers are casual about it when asked ("eventually fix them later"). I fixed the leak myself due to the source availability. The problem is due to the lack of a single person or persons looking over the development of the entire OpenCV libraries to have high quality codes. OpenCV is OK when you use it to write papers but not for commercial use (unless you are willing to fix problems yourself). You can use C++/CLI under Windows with VS2005 or later to create wrapper classes to use OpenCV or whatever C++ libraries you want to use. It is very easy. This is the major differece from Java where only native C functions can be imported.

One issue with OpenCV in that quality of codes varies from one subject to the other. Even worse: the one I downloaded had memory leak in the basic level under Windows environment but the developers are casual about it when asked (”eventually fix them later”). I fixed the leak myself due to the source availability. The problem is due to the lack of a single person or persons looking over the development of the entire OpenCV libraries to have high quality codes. OpenCV is OK when you use it to write papers but not for commercial use (unless you are willing to fix problems yourself).

]]> By: inflatable http://blog.trossenrobotics.com/2007/02/15/opencv-open-source-computer-vision-library/comment-page-1/#comment-4053 inflatable Tue, 08 May 2007 02:12:35 +0000 http://blog.trossenrobotics.com/index.php/2007/02/15/opencv-open-source-computer-vision-library/#comment-4053 Nice post, :) ,thank you! inflatable.... Nice post, :) ,thank you!
inflatable….

]]> By: Alex http://blog.trossenrobotics.com/2007/02/15/opencv-open-source-computer-vision-library/comment-page-1/#comment-1070 Alex Tue, 20 Feb 2007 22:15:46 +0000 http://blog.trossenrobotics.com/index.php/2007/02/15/opencv-open-source-computer-vision-library/#comment-1070 Thanks for the input Bob! It's always great to hear about other's experiences. So, working with OpenCV is not so good on .NET, but good if you are working in unmanaged environments? Thanks for the input Bob! It’s always great to hear about other’s experiences. So, working with OpenCV is not so good on .NET, but good if you are working in unmanaged environments?

]]> By: Bob Mottram http://blog.trossenrobotics.com/2007/02/15/opencv-open-source-computer-vision-library/comment-page-1/#comment-1067 Bob Mottram Tue, 20 Feb 2007 12:27:16 +0000 http://blog.trossenrobotics.com/index.php/2007/02/15/opencv-open-source-computer-vision-library/#comment-1067 OpenCV is ok on face recognition, but I stopped using it a while back when I began using .NET. Because it's written in C++ I was getting managed code issues. You can work around these by compiling to a DLL and then referencing that, but it all starts to get very hacky. In most cases I thought my own image processing algorithms were better anyway. The OpenCV stereo algorithm was pretty horrible. OpenCV is ok on face recognition, but I stopped using it a while back when I began using .NET. Because it’s written in C++ I was getting managed code issues. You can work around these by compiling to a DLL and then referencing that, but it all starts to get very hacky. In most cases I thought my own image processing algorithms were better anyway. The OpenCV stereo algorithm was pretty horrible.

]]>