> For the complete documentation index, see [llms.txt](https://manual.minimal.audio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.minimal.audio/current-manual/overview-and-navigation/play-view.md).

# Play View

***

### Overview

The Play View provides a fresh and expressive approach to sound design.

This view includes an interactive XY pad connected to four macro controls, providing ways to interact with presets. You can also see an overview of the current preset and sound engines, with options to bypass, solo, or quickly access each sound source for detailed editing.

Whether you're using presets from the Stream or creating your own from scratch, the Play View is designed to help you stay in the flow.

<figure><img src="https://427345021-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvbat4pds7C4cELReQ739%2Fuploads%2FudlrIJsOeiwfcTMfQr86%2Fplayview_final.png?alt=media&amp;token=cf3935e1-695d-4da3-8faf-2656b681411d" alt=""><figcaption></figcaption></figure>

***

### 1. Macro XY pad

The XY pad displays the current preset pack art and includes two draggable handles, each linked to two macros that control key parameters within the preset.

When hovering over an XY pad handle, the corresponding macros are highlighted, and vice versa. A circular icon next to each macro name indicates whether it will be adjusted by horizontal or vertical movements on the XY pad.

You can also rename each macro by clicking on its text label.

Note that the circular pack art can be customized for user packs. See [Creating Preset Packs](/current-manual/presets-and-sounds/creating-preset-packs.md) for more info.

***

### 2. Preset info

The preset info area displays the name of the currently loaded preset along with its associated pack. Here, you can favorite the current preset or load the previous, next, or a random preset.

Note that preset loading matches the preset popup in the [Top Bar](/current-manual/overview-and-navigation/top-bar.md), including the selected pack and search filters.

***

### 3. Engine Overview

The engine area offers an overview of each engine module. Clicking on a module's name takes you directly to it in the Engine View for further editing. You can also bypass and solo each sound source directly from the Play view.

***

### 4. Keyboard & Scales

The bottom section of the Play View includes a keyboard along with controls for setting Current's scale and root note.

Many presets utilize Current's arpeggiator and chord generator, which require a specific key and scale, so it's recommended to set these to match your project. You can also lock the currently selected scale to ensure it remains consistent across presets.

The on-screen keyboard marks generated notes with a ring. See [Keyboard & Scales](/current-manual/keyboard-and-midi-effects/keyboard-and-scales.md) for more info.

For more info, please see the full [Keyboard and MIDI Effects](/current-manual/keyboard-and-midi-effects.md) article.


---

# 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://manual.minimal.audio/current-manual/overview-and-navigation/play-view.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.
