> 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/sound-engine/fm-panel.md).
# FM Panel
***
### Overview
Current features a flexible FM system, allowing any sound source to frequency modulate (FM) or amplitude modulate (AM) another module, including itself. This capability can be used for FM synthesis or to introduce extra harmonics and instability into your patches. A noise source is also available for adding extra grit.
On the left side of each row, you’ll find the name of the carrier, which is the module that will be modulated based on the other settings.
***
### FM/AM
**1. Source.** Select what modulates the carrier: **Feedback** (the carrier modulates itself), any other sound source, **Noise**, or the output of **Filter 1** or **Filter 2**.
**2. Amount.** Adjust the depth of the modulation being applied.
**3. Mode.** Choose between through-zero frequency modulation and a unique form of amplitude modulation. Note that the sampler does not support AM/FM when in **Flex** mode.
---
# 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/sound-engine/fm-panel.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.
