More Insights Read more →
More Insights Read more →
Check out all the cool stuff we are doing in the video below.
Bellevue, Wa – OpenCV 3.0 is finally here, and we couldn’t be more proud of our team that helped make this new update the best it has ever been. OpenCV 3.0 is claimed to be the most functional and fastest OpenCV ever.
Open Source Computer Vision (OpenCV) is a permissive free software designed to build efficiency with real-time applications. With more than 9 million downloads, OpenCV is typically used for interactive art, stitching maps on the web, mines inspections and advanced robotics.
Here at Akvelon, we help our clients throughout the world through innovative applications of software. We ideate, define and implement better ways of doing things, which create better processes to achieve better results.
Our very own team – Max Kostin and Evgeny Agafonchikov – worked to bring OpenCV into Windows Runtime realm. Most of OpenCV modules are now available to be used from WinRT CX/C++ code and components. Over 75,000++ lines of code through 15++ pull requests have been contributed and merged in since 2.4 – Remember, this is the most functional and fastest OpenCV to date! Through thousands of tests, OpenCV 3.0 is stable, and behaves successfully on every operating system.
What’s more are the multiple changes in 3.0, one in particular that called out our very own Max Kostin:
There are multiple improvements and bug-fixes for WinRT port (as well as Windows 8.x port) of OpenCV by Microsoft guys (big thanks to Max Kostin)!In particular, parallel_for is enabled on WinRT, so the code should run much faster on multi-core devices.Also, the WMF video capturing backend has been greatly improved.
In particular, parallel_for is enabled on WinRT, so the code should run much faster on multi-core devices.
Also, the WMF video capturing backend has been greatly improved.
What is WinRT?
What are the benefits of the WinRT improvements to OpenCV?
Developers can now mix Win8 code – based on WinRT and Windows Runtime for Modern apps – with OpenCV code. If they choose to use their existing codes, they can do that as well. Developers can also use XAML to define the screen layout (using the familiar XAML controls, binding, etc) and combine it with OpenCV code, or directly use the main screen as a drawing surface for OpenCV code. OpenCV can now also run within XAML Phone applications, so developers can use OpenCV in their apps and publish it to the Windows Phone store. As with WinRT, developers can use XAML, OpenCV or a combination of the two.
Thus, our work not only targets Windows 8/8.1, but also provides early access for developers to use OpenCV on Windows 10. This is very important when considering the transformation to Windows 10 and Windows 10 support for many of their internal and external products and technologies.
Furthermore, our latest contribution of open source code to the OpenCV project, completes the relevant OpenCV libraries to enable video modules to run on any modern Windows OS -Windows 8.1, Windows Phone 8.1, as well as Windows 10 preview.
Read more on Running Video with OpenCV and WinRT
It means that all the parallel processing should be available out-of-the-box on any POSIX-compatible OS, including QNX and such. Try it out!
smart pointers (Ptr<>) can now be created in both 2.4 and 3.0 style (new ClassName(params) vs makePtr<ClassName>(params))
trained and stored stat models from opencv_ml 2.4 can now be loaded and used by opencv_ml 3.0 as-is.
OPENCV WIKI CHANGE LOG
You have gone a long way to come to the point that we can confidently assign some bugs to you. Besides, you are also doing very good job finding bugs in your area. Thanks a lot for your work!
Sorry, the comment form is closed at this time.