> For the complete documentation index, see [llms.txt](https://docs.openbrush.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openbrush.app/user-guide/make-moving-creations-using-audio-reactive-brushes.md).

# Make moving creations using audio reactive brushes

Some brushes are labelled audio reactive. Their colour, shape or motion responds to audio captured by Open Brush.

![](https://3738774261-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mikdwm98p33AibfiSqN%2Fuploads%2Fgit-blob-e391f8a60d1e7fd492761514e06f263b6931059a%2Fimage-060.png?alt=media)

## Desktop workflow

1. Begin playing audio from your computer desktop.
2. On the Brushes panel, select the wavy audio-reactive button.
3. You will see a message that Open Brush is listening for audio.
4. Once audio is detected, draw with an audio-reactive brush.

Desktop builds listen to the computer's current audio output. If no source is detected, start playback before enabling audio-reactive mode and check that the intended Windows output device is active.

## Quest and other standalone headsets

Standalone builds react to audio playing inside Open Brush rather than audio from another app:

1. Copy an MP4 or another supported video containing an audio track to `Documents/Open Brush/Media Library/Videos` on the headset.
2. Add the video from **Extras > Local Media Library > Local Videos**.
3. Make sure the video's volume is above zero and start playback.
4. Enable the audio-reactive button on the Brushes panel and draw with an audio-reactive brush.

Different brushes react in different ways, including pulsing, changing brightness and moving their geometry. The audio affects the live rendering; it does not alter the underlying stroke control points.


---

# 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://docs.openbrush.app/user-guide/make-moving-creations-using-audio-reactive-brushes.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.