The Intel® Integrated Native Developer Experience (Intel® INDE) suite has been discontinued. For more information, see https://software.intel.com/en-us/inde-eol.
The Intel® Integrated Native Developer Experience (Intel® INDE) is a cross-architecture productivity suite that provides developers with tools, support, and IDE integration to create high-performance C++/Java* applications for Windows* on Intel® architecture and Android* on ARM* and Intel® architecture.
The new OpenCV beta, a feature of Intel INDE, is compatible with the new open source OpenCV 3.0 beta (Open Source Computer Vision Library: http://opencv.org). OpenCV beta provides free binaries for computer vision applications development and production for usages like enhanced photography, augmented reality, video summarization, and more.
Key features of the Intel® INDE OpenCV are:
- Compatibly with OpenCV 3.0
- Pre-build and validated binaries, cleared of IP protected building blocks.
- Easy-to-use and maintain, with IDE integration for both Windows and Android development.
- Optimized for Intel® platforms with heterogeneous computing.
The official “Beta” status of the current Intel INDE OpenCV release implies that there might be API changes in the final OpenCV 3.0 (“Gold”) release. Therefore, whenever you start development with the Intel INDE OpenCV 3.0 Beta, you might need to change your code to make sure it works with “Gold” versions of the component.
Refer to the known issues section below for information on possible incompatibility.
The Intel INDE OpenCV Beta release focuses on simplifying the development process and shortening development time. You do not need to configure, build, or integrate the OpenCV libraries into your environment yourself. This enables you to start development immediately.
To learn more about this product, refer to the Getting started with Intel INDE OpenCV component guide.
This document provides system requirements, installation instructions, issues and limitations, and legal information.
For technical support, including answers to questions not addressed in the installed product, please visit the technical support forum.
There are no additional requirements to install and use this product on top of the existing Intel INDE System and Software requirements listed at https://software.intel.com/en-us/intel-inde-support.
Installation on Microsoft Windows* OS
You can obtain and install the Intel INDE OpenCV library on Windows* host as part of the Intel INDE installation. For detailed instructions refer to the Quick Installation Guide for OpenCV with Intel® INDE.
Uninstalling Intel INDE OpenCV
To remove the Intel INDE OpenCV, uninstall it via the Intel INDE installer. For instructions, refer to the Intel INDE Release Notes and Installation Guide.
Getting Started with Android* Targets
The currently available community version of OpenCV today (3.0 Beta) does not offer Android support. Intel INDE OpenCV comprises preview Android (32-bit only) binaries. The preview binaries enable you to explore the limited set of features and capabilities of OpenCV 3.0 on Android* targets. Today’s beta feature set for Android is limited, but will grow with future releases. For more information, including IDE integration process, refer to Getting Started with Intel INDE OpenCV for Android* Targets.
Getting Started for Windows* Targets
Intel INDE OpenCV provides ready-to-use binaries for Windows application development via Microsoft Visual Studio* IDE. The product also provides integration into Microsoft Visual Studio*. Also, during the Intel INDE installation you can mark for installation Microsoft’s ImageWatch pre-release software plugin for Visual Studio. This plug-in is shown under the OpenCV component within the Intel INDE installer. For more information, refer to Getting Started with Intel INDE-OpenCV for Windows* Targets.
On Android* platforms, the default acceleration vehicle in the community OpenCV 3.0 Beta is set to GPU OpenCL and Intel INDE OpenCV inherits this logic. However, this has been changed in a later revision of community OpenCV (by disabling the OpenCL code path for Android*). If such modification becomes part of the community OpenCV 3.0 (“Gold”) release, your application might start behaving differently when switching between the community OpenCV and the Intel INDE OpenCV implementation.
- If installation of the Microsoft* ImageWatch plug-in for Visual Studio* via the Intel INDE installer fails, install the plug-in separately using the instructions at https://visualstudiogallery.msdn.microsoft.com/e682d542-7ef3-402c-b857-bbfba714f78d
- For Android* application development, if your application uses the Android OpenCV Manager (http://docs.opencv.org/platforms/android/service/doc/index.html) you need to make your code use specific tag/versioning to load the Intel INDE OpenCV binaries instead. For details refer to Getting Started with Intel INDE-OpenCV for Android* Targets. Not doing this will result in usage of Community OpenCV libraries by default.
- Using the Intel INDE OpenCV product assumes your application does rely on OpenCV 3.0 API. Even though you may get the existing OpenCV 2.4.x-based application to work fine with this product, such compatibility is not claimed and behavior is not guaranteed. Therefore consider porting your application to 3.0 OpenCV API first. For more details on 3.0 OpenCV API please refer to OpenCV 3.0 Architecture Guide for Intel INDE OpenCV.
- The additional features added in this product are not part of the community version of OpenCV. In particular, usage of the new functions may result in incompatibility with other OpenCV 3.0 implementations.
- On the date of this product’ release, the Community OpenCV 3.0 Beta does not offer binaries for ARM-based platforms and this product does not offer them either.
- Visual Studio* is not supported for Android* development with Intel INDE OpenCV.
- On Android*, the UMat support is limited to JNI only. JNI stands for Java Native Interface- an application development approach with the C/C++ code communicating with the rest of Java via JNI.
- The fix implemented in this product removes a data race between oclCleanupCallback and Mat::GetUMat presented in the community OpenCV. However, this might have a negative performance impact depending on the application and system used.
- On Windows*, Timeout Detection and Recovery (TDR) events may be observed when OpenCL™ execution is involved, especially on workloads with complex, time-consuming kernels. Increase the TDR delay to avoid the TDRs. For details, refer to the article at http://msdn.microsoft.com/en-us/library/windows/hardware/gg487368.aspx
- For details on known issues with the OpenCL™ standard on the Intel Processor Graphics, refer to the relevant driver release notes.
- The product supports Intel® Threading Building Blocks (Intel® TBB) 4.3.4 (4.3 update 4). Any standalone Intel TBB package loaded by the application should be of either the same or higher version.