> For the complete documentation index, see [llms.txt](https://docs.velogicfit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.velogicfit.com/zh/di-02-jie-shi-yong-velogic-studio/multiple-kinect-cameras.md).

# 使用多个 Kinect 摄像头

如何在 Velogic Studio 中设置并使用多个 Microsoft Kinect 摄像头进行双侧采集

微软 Kinect 摄像头一直都有一个内置限制：在 Windows 上一次只能连接一台 Kinect 摄像头。

在我们开发 Velogic Studio 4（于 2024 年初发布）时，一项主要改进就是能够同时使用多台 Femto Mega 摄像头，实现完整的双侧采集。

虽然 Microsoft Kinect 摄像头无法同时进行双侧采集（由于 Windows 的限制），但现在可以使用多台 Kinect 摄像头来采集骑手的两侧，而无需旋转骑手。

这不是同时进行的，但仍然比在平台上实际旋转骑手的工作流程更好。具体如下：

## 设置流程

1. **启用多摄像头模式** 在 Velogic Studio 的第 1 步中，请在 Kinect 配置部分的底部寻找此选项：\
   ![Multiple camera mode toggle option at bottom of Kinect configuration section](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-de345c9cd8dec8f015d3f1afee82bd10fdb22acd%2Fmultiple-kinect-cameras-1.png?alt=media)
2. **配置第一台摄像头** 默认情况下，该选项是关闭的，但当你将其打开时，会在配置面板中看到一些不同：\
   ![Kinect configuration panel showing camera naming and remove button with multiple camera mode enabled](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-480aec9dc680caca0fdb7a7d2c8e4af9b150aa4b%2Fmultiple-kinect-cameras-2.png?alt=media)
   * Kinect 摄像头现在有了一个唯一的“名称”。这个名称最初设置为摄像头内部唯一的序列号，但你可以点击“重命名”将其改为更合适的名称，例如“右”或“左”。
   * 有一个“移除”按钮，你可以用它来删除这台摄像头。
3. **添加第二台摄像头** 如果你现在拔掉那台 Kinect 摄像头，再插入另一台摄像头，你会看到两个配置面板，每台摄像头一个：\
   ![Two Kinect camera configuration panels displayed after second camera is connected](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-5d9e6862dfb4c69d8c1f5a72bcd4e12cc00d4ca7%2Fmultiple-kinect-cameras-3.png?alt=media)
4. **重命名第二台摄像头** 你也应该重命名第二台摄像头，以便更容易识别。

## 采集流程

现在 Velogic Studio 已识别这两台摄像头，你可以用每台摄像头完成一次采集，而 Velogic Studio 会根据摄像头的名称为采集到的视频赋予不同的名称。

## 合并采集

当你完成两次采集后，例如一次使用左侧摄像头、一次使用右侧摄像头，你可以将鼠标悬停在第二次采集的缩略图上，然后点击“操作”按钮：\
![Capture thumbnail with Actions button visible when hovering over second capture](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-ecf7ff53ba0c3647e1e12344dac33c22812e5d29%2Fmultiple-kinect-cameras-4.png?alt=media)

……然后从下拉选项中选择“与前一个合并”：\
![Actions dropdown menu showing Merge with previous option for combining captures](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-f248eb8c12c7e200773f2130f208a1a9590353c5%2Fmultiple-kinect-cameras-5.png?alt=media)

Velogic Studio 会将这两次采集合并在一起，然后你就会得到一个同时包含右侧和左侧视频及指标的单一采集结果。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.velogicfit.com/zh/di-02-jie-shi-yong-velogic-studio/multiple-kinect-cameras.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.