从Kinect v1更新到Kinect v2 [英] Updating from Kinect v1 to Kinect v2

查看:128
本文介绍了从Kinect v1更新到Kinect v2的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

大家好,

由于我们尚未收到kinect v2状态的答案,我们正计划使用V1制作应用程序。但是出现了一个问题:V2和V1的sdk之间的主要区别是什么?我们可以轻松升级我们的代码吗?他们是否暴露了相同的功能?
我们有很多工作要从一种技术迁移到另一种技术吗?

As we have not received a answer of the kinect v2 status, we are planning on make a app with the V1. But a question arises: What's the main difference between the sdk of the V2 and V1? Can we upgrade our code with ease? Do they expose the same functions? Would we have much work migrating from one technology to another?

谢谢!

推荐答案

没有为SDK的最终实施提供公开信息。通常,同样的方法适用于两者之间;您可以访问颜色,深度,红外数据帧,并对这些数据帧进行一些处理。函数
调用有点不同,但是很容易移植。您可以在线找到一些视频,其中人们使用v2演示了以前的应用。

There has been no public information provided to the final implementation of the SDK. As a rule, the same methodology applies between to both; you get access to color, depth, ir frames of data and will do some processing on those frames of data. The function calls are a bit different, but are simple enough to port. You may find some videos online where people have demonstrated their previous apps using v2.

如果您按照将处理与帧的获取分离的模型,它应该是直接的。在某些情况下,使用v2会更好,因为在您的应用中需要处理的传感器管理较少。
的主要区别在于颜色/深度的分辨率是不同的,但很少有人会对它进行硬编码依赖。

If you follow the model where you decouple processing from acquisition of the frame, it should be straight forward. In some instances using v2 is better since there is less management of the sensor required to be handled in your app. The main difference is the resolutions are different for color/depth, but rarely is someone going to hard code a dependency on that.


这篇关于从Kinect v1更新到Kinect v2的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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