JavaCV VS来自OpenCV的运行点查看 [英] JavaCV Vs OpenCV from Runtime point of View

查看:250
本文介绍了JavaCV VS来自OpenCV的运行点查看的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我建立一个Android应用程序,其中包括图像处理技术。从运行的角度来看,这是更好的JavaCV或OpenCV的?

I am building an Android App that includes image processing techniques. From the Runtime point of view, which is better JavaCV or OpenCV ?

推荐答案

其运行时开销似乎是差不多的,但是Android的OpenCV的包装不给获得通过直接NIO缓冲区的原始数据,在Java中绘制自定义处理很多低效率的。 JavaCV为这些任务更有效。作为JavaCV的作者,我也很喜欢它的API更好:)这是更接近原始的C / C ++ API比Android的OpenCV的。

Their runtime overhead seems to be about the same, but the android-opencv wrappers do not give access to raw data via direct NIO buffers, rendering custom processing in Java a lot less efficient. JavaCV is more efficient for those tasks. Being the author of JavaCV, I also like its API better :) It's closer to the original C/C++ API than android-opencv.

编辑:另一个区别是,Android的OpenCV的强制用户使用NDK和JNI来编写函数。由于JavaCV是基于 JavaCPP ,我们可以更容易地编写本地功能,而无需处理既无NDK也不JNI。

Another difference is that android-opencv forces users to use the NDK and JNI to write functions. Since JavaCV is based on JavaCPP, we can write native functions more easily without having to deal with neither the NDK nor JNI.

这篇关于JavaCV VS来自OpenCV的运行点查看的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆