> 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/eprom-memory-rites-manual/macros.md).
# Macros
***
### Overview
The Macro Controls provide the primary performance and sound-shaping controls for the currently loaded preset.
Each Macro is assigned to multiple controls inside of the synth engine based on the selected preset, allowing you to transform, animate, and customize sounds in ways that are meaningful to that specific patch. Exploring these controls is often the quickest way to uncover a preset's full creative potential.
***
### 1. Macro Randomization Button
The **Dice** icon generates random variations of the current Macro settings.
Unlike loading a completely different preset, Macro Randomization creates new combinations of the four Macro controls while preserving the core character of the loaded sound. This makes it easy to discover fresh variations, unexpected textures, and new sonic directions with a single click.
### 2. Macro Knobs
**Macro 1**, **Macro 2**, **Macro 3**, and **Macro 4** are assigned to preset-specific sets of parameters that shape and transform the sound in unique ways depending on the selected preset.
Each Macro can be adjusted by dragging its control or by entering numerical values directly, providing both expressive real-time control and precise parameter adjustment.
---
# 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/eprom-memory-rites-manual/macros.md?ask=&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.
