> 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/core-effects-manual/effects/preset-bar-and-settings.md).
# Preset Bar and Settings
***
### Overview
The Core Effects share a common preset bar and Settings menu, and each effect shows the settings that apply to it. This page describes the preset bar, the Settings menu and Global Tune.
***
### Preset Bar and Settings Menu
The bar at the top of every effect holds the tooltip toggle, your account, notifications, the preset browser (previous, name, next), Save, Random Preset and the Settings menu. Open Settings for **Initialize preset**, **Show user presets**, **View manual**, and a **Support** submenu with **Get help**, **Collect support info**, **View logs** and **Log settings**. **Window size** scales the interface, **Frame rate** sets how often the graphics update, and **Enable OpenGL** switches the renderer.
Some effects add items that only apply to them. **Internal BPM** scales the tempo used by synced controls. **Playback behavior** sets whether the effect resets when the transport starts or stops.
***
### Global Tune
**Global Tune.** Choose **Global Tune…** in the Settings menu to set the reference frequency for A4. The default is 440 Hz. Global Tune applies to controls that are set as notes, such as Scale Mode in Poly Flanger. Frequencies set in Hz are not affected. The menu item appears only in effects that have note-based controls.
---
# 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/core-effects-manual/effects/preset-bar-and-settings.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.
