> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/watch-and-find-video/manage-cameras/audio-playback.md).

# Audio Playback

Adjust the volume on audio-compatible cameras.

Some cameras have the ability to record audio along with video. An **audio button** appears in the bottom-right corner of the video player if your camera(s) has audio playback functionality (hover over the camera view to reveal the audio button):

<img src="https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-db56e57ae85d2d3821e1d3b2c8adddbd512010ad%2F8864d5af2c2d2fe7.gif?alt=media" alt="" width="560">

Select the **audio button** to unmute/mute audio playback for the camera. You can playback audio from recorded and live video.

**Note:** Solink may not be compatible with all audio-capable cameras. If you do not see the audio button in the video player, it is likely that the camera does not have audio recording functionality or is not compatible with our software for audio playback. You can also reach out to our [Support team](/docs/get-started/introductory-guides/how-to-contact-our-team.md) to troubleshoot the camera.


---

# 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.solink.com/docs/watch-and-find-video/manage-cameras/audio-playback.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.
