> 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/rift-manual/welcome-to-rift/signal-flow.md).
# Signal Flow
Rift’s signal flow allows for some exciting and unconventional processing. This section is a short overview, and you will find more detail in each module’s respective section.
1. **Drive.** Rift’s processing begins with input gain controls. These are useful for driving the signal to produce more intense distortion or creating rhythmic effects when modulated.
2. **Distortion.** The distortion engine blends two parallel algorithms in Rift’s unique waveform processor. Here you can create custom effect combinations with precise control over how they are mixed. Easily choose the number of stages to take Rift from subtle to extreme.
3. **Feedback.** After the distortion, the signal is sent through a flexible feedback processor. The feedback’s frequency range can be set to notes, comb filtering, or longer delay times.
4. **Filter.** Rift’s filter can be routed pre distortion or post feedback. Choose from 24 custom filter types ranging from morphing, formant, notch, harmonic, and more.
5. **Output.** Here you can adjust the output gain, select an output limiter, and control the global dry/wet.
6. **Modulation.** In the center of Rift’s **Engine View,** you will find an envelope follower, a morphing LFO, two powerful Curve modulators, and two macro knobs. These can modulate any parameter, but they do not produce sound on their own.
---
# 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/rift-manual/welcome-to-rift/signal-flow.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.
