> 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/configuration/configure-streaming-profile-selection-for-non-verkada-channels.md).

# Configure Streaming Profile Selection for Non-Verkada Channels

Streaming Profile Selection controls how a Verkada Command Connector chooses video profiles on a non-Verkada camera.

* **Optimal** uses the streaming profile that works best with Command. Use Optimal in production. Optimal mode clears any profiles you selected manually.
* **Manufacturer** uses the streaming profiles already configured on the camera. Use Manufacturer when the camera also streams to another system, such as a network video recorder, and you do not want the Command Connector to change those profiles. This includes a trial or proof of concept. When you retire the other system, switch the channel back to Optimal.

{% hint style="warning" %}
Channel retention is not guaranteed while *Streaming Profile Selection* is set to Manufacturer.
{% endhint %}

***

### Before you begin

* The channel is an ONVIF camera connected through a Command Connector. Streaming Profile Selection is not available on an RTSP-only channel.
* The Command Connector firmware supports streaming profile selection. When it does not, the setting is hidden.

***

### Set the streaming profile selection

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Cameras.**
{% endstep %}

{% step %}
**Select the non-Verkada channel.**
{% endstep %}

{% step %}
**In the bottom right, click Settings.**
{% endstep %}

{% step %}
**Select Video Streaming.**
{% endstep %}

{% step %}
**Next to** **Streaming Profile Selection, select either:**

* **Optimal:** Use the best streaming profile for feature performance
* **Manufacturer:** Use the streaming profile from the camera manufacturer

{% hint style="warning" %}
Optimal mode clears any manually selected profiles.
{% endhint %}
{% endstep %}
{% endstepper %}

***

### Select HQ and SQ profiles manually

Manual selection is available when *Streaming Profile Selection* is set to **Manufacturer**.

The camera needs at least two profiles that the Command Connector did not create. Profiles named `vkda-high` and `vkda-low` are not listed.

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Cameras.**
{% endstep %}

{% step %}
**Select the non-Verkada channel.**
{% endstep %}

{% step %}
**In the bottom right, click Settings.**
{% endstep %}

{% step %}
**On Video Streaming, next to Current Profile, click Change.**
{% endstep %}

{% step %}
**On Select SQ Profile, select the SQ profile, then click Next.**

Use Search profiles to filter the list:

* Name
* Resolution
* FPS
* Bitrate
* GOV Length
* Codec
  {% endstep %}

{% step %}
**On Select HQ Profile, select the HQ profile, then click Apply.**

After you apply a selection, Command shows `New profile selection changes are being applied.`

Command warns you when the pair may affect streaming:

* HQ and SQ have different aspect ratios
* HQ and SQ use different codecs
* SQ resolution is larger than HQ
* HQ and SQ have the same resolution
* SQ bitrate is higher than HQ
  {% endstep %}
  {% endstepper %}


---

# 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/configuration/configure-streaming-profile-selection-for-non-verkada-channels.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.