> 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/extra-tips.md).

# 额外提示

使用 Velogic Studio 的实用技巧和窍门，包括校准指导和网络摄像头配置

## 一般提示

* 如果你在调试过程中选择切换左右侧，每次切换侧别时都需要点击实时预览界面下方的校准按钮
* 如果你想进行快速调试，可以在不校准的情况下使用此系统。它只会提供角度指标，因此本质上与我们的 2D Motion 系统具有相同的功能
* 线框中有一点不一致不会影响你的数据，除非闪烁每次都发生在踏板行程的顶部或底部。
* 线框在任何时候与骑行者的动作不同步都不要紧，因为测量功能与绘制线框的过程是分开的。线框只是一个辅助可视化的附加功能
* 如果你在任何时候遇到系统问题，请采集一个样本文件（在故障排除中有详细说明）并截取屏幕截图；没有充分的信息，我们很难解决你的问题。

## 关闭摄像头

该系统支持使用网络摄像头来捕捉骑行者的额外视角。目前还无法将第二个 Kinect 作为辅助摄像头使用。

你可以在“设置”菜单中从可用摄像头中进行选择。这对于关闭集成的前置摄像头很有用，尤其是在它们并非你的骑行者采集设备的一部分时。\
![Camera settings menu showing available webcam selection options for configuration](https://2529810062-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FjxwtZYYk0lvusnMTywNR%2Fuploads%2Fgit-blob-479c74bd17394a6efddcf0adc7f619967ac0b532%2Fcamera-settings-menu.png?alt=media)

进入采集界面后，你可以通过点击实时预览下方的画面块来选择哪个视图为主视图

我们已使用 Logitech 和 Microsoft 的网络摄像头进行了测试，并建议使用 1080P、30fps 的型号，以匹配 Kinect 的图像清晰度。我们尚未测试无线网络摄像头或使用移动设备的视频流功能。

采集过程中保存的视频将是主视图中显示的画面。因此，你可以通过在采集时选择正面视图来保存正面视频。


---

# 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/extra-tips.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.