> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command-connector/ja/she-ding/change-a-non-verkada-channel-orientation.md).

# 非Verkadaチャンネルの向きを変更する

非Verkadaチャンネルカメラのビューを回転する

場合によっては、Verkada以外のカメラフィードが誤った向きで表示されることがあります。Command Connectorを使えば、これらのフィードをCommand内で直接簡単に回転でき、適切に整列させることで、より見やすくできます。

***

## 構成

{% stepper %}
{% step %}
**Verkada Commandで、\[すべての製品] > \[カメラ] に移動します。**
{% endstep %}

{% step %}
**設定するVerkada以外のチャネルを選択します。**
{% endstep %}

{% step %}
**右下の\[設定]をクリックします。**
{% endstep %}

{% step %}
**\[デバイス] > \[向き] で、\[変更]をクリックします。**

a. 向きモードを選択します。\
b. クリック **保存** して変更を確定します。

<div align="left" data-with-frame="true"><img src="https://2993246688-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNje42M0OzzbT2nhzkB3K%2Fuploads%2Fgit-blob-b2d990dab20fe6188d65e50ae8bb34c1c853abe8%2F88cacdfd55ddccaea797014e2b1ea2c357d8d713.png?alt=media" alt="" width="356"></div>
{% endstep %}
{% endstepper %}

{% hint style="danger" %}
Command Connector 1台で、最大4つのVerkada以外のカメラフィードを回転できます。カメラの回転に対応しているのは、H.264のメインプロファイルとハイプロファイルのみです。
{% endhint %}


---

# 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://help.verkada.com/command-connector/ja/she-ding/change-a-non-verkada-channel-orientation.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.
