> 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/sound-systems/configuration/configure-a-line-input-on-a-network-audio-player.md).

# Configure a Line Input on a Network Audio Player

Learn how to configure Line Inputs for your Verkada network audio player

Verkada network audio players have multiple line inputs that allow you to connect any audio stream and play it to your Verkada Sound Systems devices.

{% hint style="danger" %}
You must be an Audio Site Admin to manage line inputs on network audio players.
{% endhint %}

***

### Add a line input

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

{% step %}
**On the left navigation, select Sites.**

1. Select your site.
2. On the right, click **Go to Site.**
   {% endstep %}

{% step %}
**At the top, click Devices.**
{% endstep %}

{% step %}
**Select your device, then on the right, click** <i class="fa-arrow-right">:arrow-right:</i>.
{% endstep %}

{% step %}
**On the device page, click on one or two of the line input ports highlighted in blue.**

1. (Optional) Under **Selected ports**, click the dropdown next to the port and select **Stereo** to pair it with its adjacent port.
2. Enter a name for the input.
3. Set the site you want to scope your line input to.
4. (Optional) Enable **Live Mode**.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>Live Mode streams audio at a much lower latency. Devices playing the line input may fall out of sync. Use Live Mode only when low latency is essential. Wi-Fi devices are not supported as outputs in this mode.</p></div>
5. Under **Play To**, click **Edit**, then select the spaces or zones that you want to stream the audio to.
   {% endstep %}

{% step %}
**Click Add to create the input.**
{% endstep %}
{% endstepper %}

***

### Delete a line input

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

{% step %}
**On the left navigation, select Sites.**

1. Select your site.
2. On the right, click **Go to Site.**
   {% endstep %}

{% step %}
**At the top, click Devices.**
{% endstep %}

{% step %}
**Select your device, then on the right, click** <i class="fa-arrow-right">:arrow-right:</i>.
{% endstep %}

{% step %}
**Under Line In, select the input you want to delete.**

1. Next to **Delete Line In,** click **Delete.**
2. Click **Confirm.**
   {% 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/sound-systems/configuration/configure-a-line-input-on-a-network-audio-player.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.
