> For the complete documentation index, see [llms.txt](https://guide.strikepack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.strikepack.com/horizon/strikepack-horizon-app-guide/shooter-studio-guide/9-audio-settings.md).

# 9 - Audio Settings

<figure><img src="https://1841283601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYraHizgjOptWmwCAGKE%2Fuploads%2FTfmAGiSjZda1qLX7RCfA%2Fline_horizon_flipped.png?alt=media&amp;token=89672410-9e30-495d-9551-51526f156405" alt=""><figcaption></figcaption></figure>

<h2 align="center"><strong>Audio Settings</strong></h2>

<p align="center"><strong>STRIKEPACK HORIZON™ Gaming Adapters</strong></p>

<figure><img src="https://1841283601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYraHizgjOptWmwCAGKE%2Fuploads%2F5Jx5Tu6u1wor8lUxYxMw%2Fline_horizon.png?alt=media&amp;token=7db97041-9d92-468c-9c18-a0fcbb400984" alt=""><figcaption></figcaption></figure>

{% embed url="<https://youtube.com/watch?v=4r7jnApqg3g>" %}

<a href="https://www.youtube.com/shorts/4r7jnApqg3g" class="button secondary" data-icon="youtube">Watch Video on YouTube</a>

<mark style="color:blue;">**In the video above,**</mark> you'll learn how to adjust a profile's **Audio Settings** in the **STRIKEPACK HORIZON** app, should you want it to be more discreet.

<mark style="color:blue;">**Written Steps:**</mark>

{% stepper %}
{% step %}
To open **Audio Settings**, <img src="https://1841283601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYraHizgjOptWmwCAGKE%2Fuploads%2FsUgzRD8aE22qsSxZ4cmI%2FTap_Icon.svg?alt=media&amp;token=70edd8e3-3389-4437-ae55-60bc2b67ec86" alt="" data-size="line"> **tap** the <i class="fa-volume">:volume:</i> **Audio** button on the bottom-bar.

***

{% endstep %}

{% step %}
**Master Volume** controls overall audio level. This is per profile, as are the other Audio Settings.

***

{% endstep %}

{% step %}
**Status Updates** controls volume for app notifications or changes that happen without user input.

***

{% endstep %}

{% step %}
**Controller Feedback** controls volume for audio cues triggered by controller button presses, such as swapping slots or cycling weapons.

***

{% endstep %}

{% step %}
**Voice Feedback** controls volume for app responses after processing a voice command.

***

{% endstep %}

{% step %}
**Dash Feedback** controls volume and haptics for interactions while touch navigating the dashboard menus.

***

{% endstep %}

{% step %}
When you are done adjusting volumes, <img src="https://1841283601-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFYraHizgjOptWmwCAGKE%2Fuploads%2FsUgzRD8aE22qsSxZ4cmI%2FTap_Icon.svg?alt=media&amp;token=70edd8e3-3389-4437-ae55-60bc2b67ec86" alt="" data-size="line"> **tap** the <i class="fa-volume">:volume:</i> **Audio** button again to close Audio Settings.
{% 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://guide.strikepack.com/horizon/strikepack-horizon-app-guide/shooter-studio-guide/9-audio-settings.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.